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

Wed Jun 14 16:31:26 UTC 2017

Fresh install of an artful-server image in a VM, and I can't reproduce
this problem.  For some reason, on your system networkd never logs that
the network interface has been 'configured'.  So in fact, systemd-
networkd-wait-online is behaving correctly; you're somehow just never
getting the OK from systemd-networkd.

ubuntu at artful-server:~$ time sudo /lib/systemd/systemd-networkd-wait-online
ignoring: lo

real	0m0.018s
user	0m0.012s
sys	0m0.000s
ubuntu at artful-server:~$ echo $?
0
ubuntu at artful-server:~$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 52:54:00:68:21:e2 brd ff:ff:ff:ff:ff:ff
ubuntu at artful-server:~$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:68:21:e2 brd ff:ff:ff:ff:ff:ff
    inet 192.168.15.68/24 brd 192.168.15.255 scope global dynamic ens3
       valid_lft 3269sec preferred_lft 3269sec
    inet6 2001:470:e980:0:5054:ff:fe68:21e2/64 scope global mngtmpaddr noprefixroute dynamic 
       valid_lft 86295sec preferred_lft 14295sec
    inet6 fe80::5054:ff:fe68:21e2/64 scope link 
       valid_lft forever preferred_lft forever
ubuntu at artful-server:~$ cat /etc/netplan/01-netcfg.yaml 
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
    ens3:
      dhcp4: yes
      dhcp6: yes
ubuntu at artful-server:~$ cat /run/systemd/network/10-netplan-ens3.network 
[Match]
Name=ens3

[Network]
DHCP=yes

[DHCP]
RouteMetric=100
ubuntu at artful-server:~$ dpkg -l systemd|grep ^ii
ii  systemd        233-6ubuntu3 amd64        system and service manager
ubuntu at artful-server:~$ 

And, perhaps most crucially:

ubuntu at artful-server:~$ sudo journalctl -u systemd-networkd --no-pager
-- Logs begin at Wed 2017-06-14 09:20:15 PDT, end at Wed 2017-06-14 09:27:38 PDT. --
Jun 14 09:20:17 artful-server systemd[1]: Starting Network Service...
Jun 14 09:20:17 artful-server systemd-networkd[451]: Enumeration completed
Jun 14 09:20:17 artful-server systemd[1]: Started Network Service.
Jun 14 09:20:17 artful-server systemd-networkd[451]: ens3: IPv6 successfully enabled
Jun 14 09:20:17 artful-server systemd-networkd[451]: ens3: Gained carrier
Jun 14 09:20:18 artful-server systemd-networkd[451]: ens3: DHCPv4 address 192.168.15.68/24 via 192.168.15.1
Jun 14 09:20:18 artful-server systemd-networkd[451]: ens3: Gained IPv6LL
Jun 14 09:20:20 artful-server systemd-networkd[451]: ens3: Configured
ubuntu at artful-server:~$

-- 
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