** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2039083
Title:
"optional: true" flag introduces
Lukas - upstream is actually broken in v253 until v253.6, and the reason
it appears "OK" in v253.5 (which we have in Mantic) is that [1]
introduces a bug upstream that makes systemd-networkd-wait-online behave
similarly to Ubuntu's patched systemd-networkd-wait-online prior to
systemd
So if I understand correctly, this does not affect Focal or Bionic.
It also does not affect Mantic or Noble.
We're just hitting this issue on Jammy = systemd v249.11 (and probably
Lunar = systemd v252.5).
Netplan's behavior seems to be correct, here. It writes sensible
configuration for
As far as I can tell we are facing this issue:
https://github.com/systemd/systemd/issues/25813
This was fixed in systemd 253 with the following patch
https://github.com/systemd/systemd/commit/ab3aed4a0349bbaa26f53340770c1b59b463e05d
(and
>From https://www.man7.org/linux/man-pages/man5/systemd.network.5.html
If RequiredForOnline=no is set, systemd-networkd-wait-online should skip
the interface:
The network will be brought up normally (as configured by
ActivationPolicy=), but in the event that there is no address
being
Copying from my comment
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/comments/43
systemd 249.11-0ubuntu3.11 doesn't resolve the issue I'm facing (this
one). The long delay seems to be caused by systemd-networkd-wait-online
not respecting "RequiredForOnline=no".
ubuntu@ubuntu:~$
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
closely related LP: #2036358
Whatever Ubuntu and systemd decide to do, the manual
systemd-networkd-wait-online(8) also needs clarification:
"[..] wait for all links it is aware of and which are
managed by systemd-networkd.service(8) to be fully configured or
failed, and for at least one link
I think this is related to a recent change in behavior in systemd.
It is supposed to be fixed, by implementing the "network-online.target"
specification. Which defines what should be waited for:
https://discourse.ubuntu.com/t/spec-definition-of-an-online-system/27838
But we first need to get
9 matches
Mail list logo
