[Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

[Dennis Kuhn]

I could solve this issue by rebuilding the debian packages without two
patches:

- networkd-add-support-to-configure-NOARP-ARP-for-interface.patch
- networkd-bond-support-primary-slave-and-active-slave-4873.patch

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

Title:
  229-4ubuntu20 added ARP option breaks existing bonding interfaces

Status in systemd package in Ubuntu:
  Confirmed

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