** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
--
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/1833671
Title:
bond interfaces stop working after restart of systemd-networkd
Status in systemd:
Unknown
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
In Progress
Bug description:
Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu
18.04.2 I have one machine where, every time systemd-networkd restarts
(ie every time there is an update to systemd) the bond0 interface
stops working.
I see both physical interfaces go soft down and then come back again:
Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in
system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC
Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture
x86-64.
Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for
backup interface eno2, disabling it in 200 ms
Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for
active interface eno1, disabling it in 200 ms
Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW
filter on device eno2
Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW
filter on device eno1
Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again
after 200 ms for interface eno2
Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again
after 100 ms for interface eno1
and after that nothing until I stop systemd-networkd, delete the bond
interface, and then start systemd-networkd again.
On most machines the cycle seems to take a bit longer and the
interfaces reach a hard down start before coming back and in that case
there seems to be no problem.
I think this is likely an instance of this upstream bug:
https://github.com/systemd/systemd/issues/10118
which has a fix here:
https://github.com/systemd/systemd/pull/10465
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1833671/+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
