On Wed, Jun 14, 2017 at 10:04:28AM -0000, Stefan Bader wrote: > Sorry, forgot above:
> #> cat /run/systemd/network/10-netplan-eth0.network > [Match] > Name=eth0 > [Network] > DHCP=ipv4 > [DHCP] > RouteMetric=100 I know you say this is also reproducible for you when using ensX names, but for completeness, why do you have eth0 here? That's not a name that should be appearing anywhere on an artful system, unless you've set net.ifnames=0, which is strongly discouraged. On Wed, Jun 14, 2017 at 07:37:50AM -0000, Stefan Bader wrote: > @Steve, yes it does. And if the wait is related to the list of NICs from > ifquery, it does make sense (in some way) as that list only contains > "lo", not "eth0". Also "ifquery --state eth0" does not return anything > while it does return "lo=lo" for "lo". networkd doesn't care at all about ifquery. systemd-networkd-wait-online(8) documents that this should return as soon as "all links it is aware of and which are managed by systemd-network [are] fully configured or failed, and [...] at least one link [gains] a carrier." So this is definitely not working as designed, if you have only a single interface configured in systemd-network and its link is up, but -wait-online is not returning success. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
