[Bug 2003250] Re: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss

[Bartosz Woronicz]

This bug fix for Jammy is critical for our ongoing deployment at the customer side.
The unique combination of hardware (Intel NICs and AMD platform) causes unusual long time for the bond to come up after running netplan (7-11s). That is long enough to cause:
- three way database partition
- timeout on ha based services (corosync) 

As running netplan apply is used among our automation and charms it may
disrupt all HA db service like PostgresSQL , MysSQL, MongoDB, OVNdb

As this seems critical to our deployment I am marking that field-
critical

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

Title:
  networkctl reload with bond devices causes slaves to go DOWN and UP,
  causing couple of seconds of network loss

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Won't Fix

Bug description:
  We currently use Ubuntu 22.04.1 LTS including updates for our production cloud (switched from legacy Centos 7).
  Although we like the distribution we recently hit serious systemd buggy behavior described in [1] bugreport using packages [2].

  Unfortunatelly the clouds we are running consist of openstack on top
  of kubernetes and we need to have complex network configuration
  including linux bond devices.

  Our observation is that every time we apply our configuration via
  CI/CD infrastructure using ansible and netplan (regardless whether
  there is actual network configuration change) we see approximatelly
  8-16 seconds network interruptions and see bond interfaces going DOWN
  and then UP.

  We expect bond interfaces stay UP when there is no network
  configuration change.

  We went though couple of options how to solve the issue and the first
  one is to add such existing patch [3] into current
  systemd-249.11-0ubuntu3.6.

  Could you comment whether this kind of non-security patch is likely to land in 22.04.1 LTS soon.
  We are able to help to bring patch into systemd package community way if you suggest the steps.

  
  [1] https://github.com/systemd/systemd/issues/25067
  [2] Packages
  root at controlplane-001:/etc/apt0# apt list | grep -E '^(systemd/|netplan.io)'
  netplan.io/jammy-updates,now 0.105-0ubuntu2~22.04.1 amd64 [installed,automatic]
  systemd/jammy-updates,now 249.11-0ubuntu3.6 amd64 [installed,automatic]
  [3] https://github.com/systemd/systemd/pull/25162
  [4] # lsb_release -rd
  Description:    Ubuntu 22.04.1 LTS
  Release:        22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003250/+subscriptions