group.of.nepali.translators team mailing list archive

[Dimitri John Ledkov <launchpad@xxxxxxxxxxxx>]

** Description changed:

+ [Impact]
+ 
+  * Incomplete cherrypick of ARP functionality in networkd resulted in an
+ undesired side-effect, specifically NOARP flag started to be applied
+ unconditionally, specifically when it should not have, resulting in loss
+ of network connectivity.
+ 
+ * This is a regression in -updates.
+ 
+ [Test Case]
+ 
+  * Configure a bond using networkd
+  * Upgrade
+  * Make sure NOARP flag is not set on the interfaces / bond
+ 
+ [Regression Potential]
+ 
+  * This is an upstream fix for this issue.
+ 
+ [Other Info]
+  
+  * Upstream fix
+ https://github.com/systemd/systemd/commit/1ed1f50f8277df07918e13cba3331a114eaa6fe3.patch
+  
+  * Original bug report
+ 
  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

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Critical

** Also affects: systemd (Ubuntu Artful)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu Bionic)
   Importance: Critical
       Status: Confirmed

** Also affects: systemd (Ubuntu Zesty)
   Importance: Undecided
       Status: New

** Changed in: systemd (Ubuntu Xenial)
       Status: New => In Progress

** Changed in: systemd (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: systemd (Ubuntu Zesty)
       Status: New => Fix Released

** Changed in: systemd (Ubuntu Artful)
       Status: New => Fix Released

** Changed in: systemd (Ubuntu Bionic)
       Status: Confirmed => Fix Released

** Changed in: systemd (Ubuntu Xenial)
     Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu Xenial)
    Milestone: None => xenial-updates

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1727301

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

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Zesty:
  Fix Released
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Incomplete cherrypick of ARP functionality in networkd resulted in
  an undesired side-effect, specifically NOARP flag started to be
  applied unconditionally, specifically when it should not have,
  resulting in loss of network connectivity.

  * This is a regression in -updates.

  [Test Case]

   * Configure a bond using networkd
   * Upgrade
   * Make sure NOARP flag is not set on the interfaces / bond

  [Regression Potential]

   * This is an upstream fix for this issue.

  [Other Info]
   
   * Upstream fix
  https://github.com/systemd/systemd/commit/1ed1f50f8277df07918e13cba3331a114eaa6fe3.patch
   
   * Original bug report

  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/systemd/+bug/1727301/+subscriptions