Public bug reported:
this breaks existing configurations with bonding on upgrading from
229-4ubuntu19 to 229-4ubuntu20 on xenial
as bond interfaces are now by default configured without ARP. Hence you
suddenly lose network connectivity on upgrade. Very bad for a SRU.
Plus adding "ARP=yes" to the Link section of a .network file does not
work.
Before this update, bond interfaces (specifically 802.3ad) were
defaulting to ARP enabled. After the upgrade, they are created with
NOARP set on the link.
pre-upgrade:
eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP>
eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP>
bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP>
post-upgrade:
eth0: <BROADCAST,MULTICAST,NOARP,SLAVE,UP,LOWER_UP>
eth1: <BROADCAST,MULTICAST,NOARP,SLAVE,UP,LOWER_UP>
bond0: <BROADCAST,MULTICAST,NOARP,MASTER,UP,LOWER_UP>
Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: regression-updates
** Description changed:
+ this breaks existing configurations with bonding on upgrading from
+ 229-4ubuntu19 to 229-4ubuntu20 on xenial
- this breaks existing configurations with bonding on upgrading from
229-4ubuntu19 to 229-4ubuntu20
- as bond interfaces are now by default configured without ARP. Hence you
suddenly lose network connectivity on upgrade. Very bad for a SRU.
+ as bond interfaces are now by default configured without ARP. Hence you
+ suddenly lose network connectivity on upgrade. Very bad for a SRU.
Plus adding "ARP=yes" to the Link section of a .network file does not
work.
Before this update, bond interfaces (specifically 802.3ad) were
defaulting to ARP enabled. After the upgrade, they are created with
NOARP set on the link.
pre-upgrade:
eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP>
eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP>
bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP>
post-upgrade:
eth0: <BROADCAST,MULTICAST,NOARP,SLAVE,UP,LOWER_UP>
eth1: <BROADCAST,MULTICAST,NOARP,SLAVE,UP,LOWER_UP>
bond0: <BROADCAST,MULTICAST,NOARP,MASTER,UP,LOWER_UP>
Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
--
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/1727301
Title:
229-4ubuntu20 added ARP option breaks existing bonding interfaces
Status in systemd package in Ubuntu:
New
Bug description:
this breaks existing configurations with bonding on upgrading from
229-4ubuntu19 to 229-4ubuntu20 on xenial
as bond interfaces are now by default configured without ARP. Hence
you suddenly lose network connectivity on upgrade. Very bad for a SRU.
Plus adding "ARP=yes" to the Link section of a .network file does not
work.
Before this update, bond interfaces (specifically 802.3ad) were
defaulting to ARP enabled. After the upgrade, they are created with
NOARP set on the link.
pre-upgrade:
eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP>
eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP>
bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP>
post-upgrade:
eth0: <BROADCAST,MULTICAST,NOARP,SLAVE,UP,LOWER_UP>
eth1: <BROADCAST,MULTICAST,NOARP,SLAVE,UP,LOWER_UP>
bond0: <BROADCAST,MULTICAST,NOARP,MASTER,UP,LOWER_UP>
Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727301/+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
