I'm seeing the same behavior with Ubuntu 18.04.2 running in a VMware
virtual machine. When networking for the VM is set to "Host-only", it
takes two extra minutes to boot while waiting for systemd-networkd-wait-
online.service to fail.
$ lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04
$ apt-cache policy systemd
systemd:
Installed: 237-3ubuntu10.13
Candidate: 237-3ubuntu10.13
Version table:
*** 237-3ubuntu10.13 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
237-3ubuntu10 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
--
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/1804611
Title:
systemd-networkd is stuck in 'configuring' with DHCP and no default
route
Status in systemd package in Ubuntu:
Confirmed
Bug description:
In our network setup systemd-networkd fails to configure everything
correctly. Our systems have two NIC which are configured via DHCP. One
NIC is in a service network without a default route. With this setup
we get systemd-networkd-wait-online.service failing after timeout and
the service NIC stuck in 'configuring'. Besides that, everything is
working as expected.
Our config:
# lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
# apt-cache policy systemd
systemd:
Installiert: 237-3ubuntu10.9
Installationskandidat: 237-3ubuntu10.9
Versionstabelle:
*** 237-3ubuntu10.9 500
500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
237-3ubuntu10 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Package
# cat /etc/systemd/network/ens160.network
[Match]
Name=ens160
[Network]
DHCP=ipv4
[DHCP]
UseMTU=true
RouteMetric=100
ClientIdentifier=mac
# cat /etc/systemd/network/ens192.network
[Match]
Name=ens192
[Network]
DHCP=ipv4
[DHCP]
UseMTU=true
RouteMetric=100
ClientIdentifier=mac
UseRoutes=false
UseDNS=false
networkctl status -a
● 1: lo
Link File: n/a
Network File: n/a
Type: loopback
State: carrier (unmanaged)
Address: 127.0.0.1
::1
● 2: ens160
Link File: n/a
Network File: /etc/systemd/network/ens160.network
Type: ether
State: routable (configured)
Path: pci-0000:03:00.0
Vendor: VMware
Model: VMXNET3 Ethernet Controller
HW Address: 00:50:56:a4:98:4c (VMware, Inc.)
Address: 10.22.0.30
fe80::250:56ff:fea4:984c
Gateway: 10.22.200.254 (Hewlett Packard Enterprise)
DNS: 10.22.0.2
Search Domains: xxxxxxxxxxx
● 3: ens192
Link File: n/a
Network File: /etc/systemd/network/ens192.network
Type: ether
State: routable (configuring)
Path: pci-0000:0b:00.0
Vendor: VMware
Model: VMXNET3 Ethernet Controller
HW Address: 00:50:56:a4:c0:42 (VMware, Inc.)
Address: 10.23.0.30
fe80::250:56ff:fea4:c042
Search Domains: xxxxxxxxxxxx
This also happens in other configurations, which are more complex as soon as
I add the service NIC which has no default route. systemd 239 from ubuntu 16.10
works fine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804611/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
