[Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
Got it on mantic -> noble upgrade too, the solution proposed in the Description helped: $ systemctl disable --now systemd-networkd.service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
Got it on mantic -> noble upgrade too, the solution proposed in the Description helped: $ systemctl disable --now systemd-networkd.service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
Hi, I got hit by this bug after a mantic -> noble upgrade on a desktop system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
I have a number of RPi installed with Ubuntu Server 23.10 (64 bit) installations in Nov. 2023. They do no have this problem. Installing the same OS about a week ago on the same RPi, causes the problem. So the problem was likely caused by something Ubuntu released between Nov. to March. @Steve Langasek [workaround](https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/comments/74) works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
> If you have a bunch of unmanaged interfaces, then you should use a > drop-in configuration to pass the --any flag to > systemd-networkd-wait-online: > > cat > /etc/systemd/system/systemd-networkd-wait-online.service.d/any.conf << > EOF > [Service] > ExecStart= > ExecStart=/lib/systemd/systemd-networkd-wait-online --any > EOF > > This makes it so that systemd-networkd-wait-online will return success once > at least one interface becomes configured. Unfortunately this doesn't appear to work. I've tried this on the current noble dailies (which also suffer the 2 minute boot delay on the server images due to this issue). The default netplan config is simply: network: version: 2 ethernets: eth0: dhcp4: true optional: true This displays the issue, even with --any presumably because wlan0 is unmanaged so networkctl reports the online state is "unknown" (even when eth0 is happily configured and routable). I attempting making wlan0 "managed" but optional. This requires a mandatory access point to be defined to conform to the YAML schema, so I added a fake one (I should open a separate issue for this because I shouldn't have to make up access points just to mark an interface optional): network: version: 2 ethernets: eth0: dhcp4: true optional: true wifis: wlan0: dhcp4: true optional: true access-points: foo: password: foobarbaz Unfortunately this also displays the issue. This time wlan0 is managed, but "configuring" and the online state is still "unknown". So far as I can tell, the --any option doesn't match the behaviour claimed in the man-page (i.e. "exits with success when at least one interface becomes online"). > There is no workaround for this with the stock netplan config on > raspberry pi, which trips this bug. But you can customize > /etc/netplan/ on your system to mark your expected/required network > interfaces as "optional: false" (which is the default if > unspecified); AIUI that would avoid this issue with > systemd-networkd. This *does* work ... assuming the Pi actually has a network interface. If the Pi is networkless, it's unfortunately doomed to the 2 minute delay still. And obviously I don't want to make eth0 mandatory by default in the images (which would break the 3A+ and Zero 2W, which lack eth0 entirely). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
