networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Jammy |
Triaged
|
Medium
|
Unassigned | ||
Kinetic |
Won't Fix
|
Low
|
Unassigned |
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-
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:/
[2] Packages
root@controlpla
netplan.
systemd/
[3] https:/
[4] # lsb_release -rd
Description: Ubuntu 22.04.1 LTS
Release: 22.04
I have confirmed that this bug affects Jammy and newer. The upstream patch looks straight-forward, so I will test a build with that patch included to see if it fixes the issue.