Public bug reported:
On new install of 17.10 systemd-networkd loops with:
Oct 23 16:45:24 san-jose systemd[1]: Starting Network Service...
Oct 23 16:45:24 san-jose systemd-networkd[1217]: enp129s0f0: Gained IPv6LL
Oct 23 16:45:24 san-jose systemd-networkd[1217]: Enumeration completed
Oct 23 16:45:24 san-jose systemd[1]: Started Network Service.
Oct 23 16:45:25 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address
10.30.3.94/24 via 12
Oct 23 16:45:27 san-jose systemd-networkd[1217]: Could not set hostname: The
name org.freedesktop
Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost
Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address
10.30.3.94/24 via 12
Oct 23 16:45:29 san-jose systemd-networkd[1217]: Could not set hostname: The
name org.freedesktop
Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Configured
Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost
that is the correct interface and address.
If I manually run 'dhclient nep129s0f0' the lease sticks and 'journalctl
-fu systemd-networkd' shows:
Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address
10.30.3.94/24 via 12
Oct 23 16:45:34 san-jose systemd-networkd[1217]: Could not set hostname: The
name org.freedesktop
Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Configured
I have verified this is reproducible on other systems with ixgbe based
add in cards.
igb (1G) cards seem to behave properly as do a random assortment of
onboard devices and virtio devices inside VMs.
Based on a pseudo random selection of my available gear it does seem
hardware specific but this is our only flavor of 10G nic (and we have
kindof a lot of them). Since isc-dhcp-client can bring up the
interface on the commandline I don't *think* it's a driver issue.
root@host:~# lsb_release -rd;uname -r ; dpkg -l nplan systemd
Description: Ubuntu 17.10
Release: 17.10
4.13.0-16-generic
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==================-==============-==============-=========================================
ii nplan 0.30 amd64 YAML network configuration abstraction fo
ii systemd 234-2ubuntu12 amd64 system and service manager
my current workaround:
root@host:~# cat /etc/rc.local
#!/bin/sh
dhclient enp129s0f0
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727825
Title:
networkd DHCP immediately drops lease ( on igbx cards )
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727825/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
