[Bug 1697730] Re: Long boot time due to systemd-networkd-wait-online.service failure

[Steve Langasek]

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/
slangasek at ubuntu.com                                     vorlon at debian.org

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1697730

Title:
  Long boot time due to systemd-networkd-wait-online.service failure

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Fresh VM installation from the Artful daily server ISO. Installation
  finishes without issues but booting the installed system takes a long
  time (until systemd-networkd-wait-online.service times out). The VM
  can already be pinged at that stage, so network has been configured at
  that stage. It just seems that the waiting command does not notice the
  interface being up.

  From the installed system (after timeout) it looks like the lo device
  is set up via /etc/network/interfaces but the NIC is set in
  /etc/netplan/01-netcfg.yaml.

  systemd-networkd.service:
  Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Network Service...
  Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: Enumeration completed
  Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: IPv6 successfully enabled
  Jun 13 17:07:08 bar-artful6401 systemd[1]: Started Network Service.
  Jun 13 17:07:08 bar-artful6401 systemd-networkd[587]: eth0: Gained carrier
  Jun 13 17:07:09 bar-artful6401 systemd-networkd[587]: eth0: DHCPv4 address 192.168.2.159/24 via 192.168.2.1
  Jun 13 17:07:10 bar-artful6401 systemd-networkd[587]: eth0: Gained IPv6LL

  systemd-networkd-wait-online.service (failed):
  Jun 13 17:07:08 bar-artful6401 systemd[1]: Starting Wait for Network to be Configured...
  Jun 13 17:09:09 bar-artful6401 systemd-networkd-wait-online[593]: Event loop failed: Connection timed out
  Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, sta
  Jun 13 17:09:09 bar-artful6401 systemd[1]: Failed to start Wait for Network to be Configured.
  Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state.
  Jun 13 17:09:09 bar-artful6401 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 233-6ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Tue Jun 13 18:11:47 2017
  InstallationDate: Installed on 2017-06-13 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170611)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic root=/dev/mapper/bar--artful6401--vg-root ro video=640x480
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2017
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: dmi:bvnXen:bvr4.8.0:bd03/15/2017:svnXen:pnHVMdomU:pvr4.8.0:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.8.0
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+subscriptions