I’m struggling after an update from Cobia to Dragonfish (went straight to 24.04.1) today. I had zero issues when I migrated from Bluefin to Cobia so I didn’t expect to have this problem.
The upgrade went through, but my Apps are not loading and I’m getting an error that says Error in Apps Service: Application(s) have failed to start: list index outside of range.
When I tried to check or change the Application settings, everything seems to fail with this networking errors as follows:
Error: route_v4_interface
Timed out waiting 60 seconds for bond1: eno1=eno2 to come up
More info…
Error: Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/middlewared/job.py”, line 469, in run
await self.future
File “/usr/lib/python3/dist-packages/middlewared/job.py”, line 511, in __run_body
rv = await self.method(*args)
^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/schema/processor.py”, line 47, in nf
res = await f(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/schema/processor.py”, line 187, in nf
return await func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/plugins/kubernetes_linux/update.py”, line 506, in do_update
await self.validate_data(config, ‘kubernetes_update’, old_config)
File “/usr/lib/python3/dist-packages/middlewared/plugins/kubernetes_linux/update.py”, line 377, in validate_data
verrors.check()
File “/usr/lib/python3/dist-packages/middlewared/service_exception.py”, line 70, in check
raise self
middlewared.service_exception.ValidationErrors: [EINVAL] kubernetes_update.route_v4_interface: Timed out waiting 60 seconds for bond1: eno1=eno2 to come up
I have the eno1 and eno2 setup for LACP (bond1) with what I thought was pretty much default setup. I have no issues connecting to my SMB shares or the truenas.local gui.
There were not any problems under Cobia and I’m not sure how to resolve this.
There seems to be some conflict issue in the 24.04.1 version with Kubernetes and my bonded LACP interface. Kubernetes wouldn’t connect, but it also wouldn’t release my interface, therefore, I couldn’t find a way to delete it and re-create it. I couldn’t get any apps to load from previous settings, and I couldn’t install any new Apps.
I didn’t try that. For now, I’m just happy that nothing was wrecked with my Cobia configuration. Everything is up and running for now. I’ll hold off on the Dragonfish for a few more maintenance updates and then try when I have more time on a weekend.
Just created an account for that. Thank you! Not only link aggregation devices seem to have this issue, even my “normal” lan device stopped kubernetes from working, after deleting the description on the network settings everything seems to be back to normal again.
Bingo!! Worked for me immediately. Had the same issue on upgrading to 24.04.1 and removing the description in the network interface dialog solved it right away.
NB - mine was not an aggregated LAN setup, just my one nic LAN interface. I had given it a name in the description field which, when removed, solved the post-upgrade kubernetes problem.
I rolled back also, went back to networking, edit my bond - remove the description and uncheck autoconfigure IPv6 , save, then updated to dragonfish with no issues. Btw I’m interested in setting up sandboxes with jailmaker. I’m done with truecharts apps.
It appears the 24.04.1.1 update fixed this issue. I tried the upgrade again after checking the Bug thread linked above and everything is up and running with no issues (so far).
