update tumbleweed 202408222/23 to 20240825 kills network
As david ranklin wrote on this list in the morning with his whireless network, also here after a update a couple of minutes ago, one on of my machines (others i have not updated) from 240822 or 240823 (sorry, could not check, because netzwork is gone) my wicked network is gone. have not investigated up to now, i am not in front of that machine, so please take care ! simoN -- www.becherer.de
I just updated a VM from Tumbleweed 20240808-0 -> 20240826-0 and I'm seeing similar and/or worse behavior. After the dist-upgrade, during initial boot after grub boots the system I get a blank screen, I do not see any of the boot messages and I never see the console sign-in prompt. I then need to reset power, and on the grub screen I select advanced options and select the previous kernel (6.10.3-1-default) and the system boots successfully, but the network (wicked) fails to start during boot with various message as I've listed below. I can manually start networking (systemctl start network), but that is clearly a workaround. I'm going to post this to the opensuse-factory list, but wanted to follow-up on this thread since the issue is continuing with Tumblewewed 20240826-0. wicked[1227]: /org/opensuse/Network/Interface.getManagedObjects failed. Server responds: wicked[1227]: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable wicked[1227]: Couldn't refresh list of active network interfaces systemd[1]: wicked.service: Failed with result 'exit-code'. systemd[1]: Failed to start wicked managed network interfaces.
On 8/28/24 6:32 AM, Darin Perusich via openSUSE Users wrote:
I just updated a VM from Tumbleweed 20240808-0 -> 20240826-0 and I'm seeing similar and/or worse behavior. After the dist-upgrade, during initial boot after grub boots the system I get a blank screen, I do not see any of the boot messages and I never see the console sign-in prompt. I then need to reset power, and on the grub screen I select advanced options and select the previous kernel (6.10.3-1-default) and the system boots successfully, but the network (wicked) fails to start during boot with various message as I've listed below. I can manually start networking (systemctl start network), but that is clearly a workaround.
I'm going to post this to the opensuse-factory list, but wanted to follow-up on this thread since the issue is continuing with Tumblewewed 20240826-0.
wicked[1227]: /org/opensuse/Network/Interface.getManagedObjects failed. Server responds: wicked[1227]: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable wicked[1227]: Couldn't refresh list of active network interfaces systemd[1]: wicked.service: Failed with result 'exit-code'. systemd[1]: Failed to start wicked managed network interfaces.
Already reported as bug and they are working on a solution, see: On 8/27/24 8:39 AM, Simon Becherer wrote:
.... snip ...... That for example has been reported already as https://bugzilla.opensuse.org/show_bug.cgi?id=1229745
wicked is wrongly starting before dbus-broker and results in not having a network configured.
After the boot, you can "systemctl restart network" or apply the patch which is proposed in https://github.com/openSUSE/wicked/pull/1032 locally to get it faster,
The bug report contains another work-around as well. You can also read through the thread from yesterday: "Tumbleweed - dracut update on dup tonight failed to start WiFi on reboot?" -- David C. Rankin, J.D.,P.E.
Am 28.08.24 um 13:32 schrieb Darin Perusich via openSUSE Users:
I just updated a VM from Tumbleweed 20240808-0 -> 20240826-0 and I'm seeing similar and/or worse behavior. After the dist-upgrade, during initial boot after grub boots the system I get a blank screen, I do not see any of the boot messages and I never see the console sign-in prompt. I then need to reset power, and on the grub screen I select advanced options and select the previous kernel (6.10.3-1-default) and the system boots successfully, but the network (wicked) fails to start during boot with various message as I've listed below. I can manually start networking (systemctl start network), but that is clearly a workaround.
I'm going to post this to the opensuse-factory list, but wanted to follow-up on this thread since the issue is continuing with Tumblewewed 20240826-0.
wicked[1227]: /org/opensuse/Network/Interface.getManagedObjects failed. Server responds: wicked[1227]: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable wicked[1227]: Couldn't refresh list of active network interfaces systemd[1]: wicked.service: Failed with result 'exit-code'. systemd[1]: Failed to start wicked managed network interfaces.
I updated at the momment a system also to 20240826 and wicked worked fine, not checked if its luck or if the problem is already solved. simoN -- www.becherer.de
On 8/28/24 3:11 PM, Simon Becherer wrote:
I updated at the momment a system also to 20240826 and wicked worked fine, not checked if its luck or if the problem is already solved.
simoN
Yes, wicked was updated to ver. 0.6.76-1.1 in the update today. Yay! Now I can delete my replacement files! -- David C. Rankin, J.D.,P.E.
On Wed, Aug 28, 2024 at 5:28 PM David C. Rankin <drankinatty@gmail.com> wrote:
On 8/28/24 3:11 PM, Simon Becherer wrote:
I updated at the momment a system also to 20240826 and wicked worked fine, not checked if its luck or if the problem is already solved.
simoN
Yes, wicked was updated to ver. 0.6.76-1.1 in the update today. Yay! Now I can delete my replacement files!
The update to 20240827 has resolved the network not starting issue, but I still lose access to the VMWare console unless I boot the previous kernel 6.10.3-1-default. I don't think this is a plymouth issue because if I remove "splash=silent" and change "quite" to "verbose" in grub at boot it still occurs. Unfortunately I'm not able to sign into bugzilla due to an account/username issue, which I'm waiting for the bugzilla-admins to resolve.
-- David C. Rankin, J.D.,P.E.
On 8/29/24 6:46 AM, Darin Perusich wrote:
The update to 20240827 has resolved the network not starting issue, but I still lose access to the VMWare console unless I boot the previous kernel 6.10.3-1-default. I don't think this is a plymouth issue because if I remove "splash=silent" and change "quite" to "verbose" in grub at boot it still occurs. Unfortunately I'm not able to sign into bugzilla due to an account/username issue, which I'm waiting for the bugzilla-admins to resolve.
Yes, It may be the case the wickedd.service break was one of many symptoms in whatever change freedesktop.org blessed us with. The BindsTo= works for wicked, but has added 0.3 sec to boot time and feels more like a Bandaid than a full fix. I too have writted to bugzilla admins twice over the past month to fix an e-mail attached to bugzilla that no longer exists. I've not had a single communication from them despite my efforts. Perhaps if we had an actual person to contact instead of some admin account, we may be able to resolve both our issues. Devs? Anybody know (and will share) who that is? -- David C. Rankin, J.D.,P.E.
participants (3)
-
Darin Perusich -
David C. Rankin -
Simon Becherer