Bonding interface does not come up on networking.service stop/start/restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Fabiano Correa Mercer |
Bug Description
Brief Description
-----------------
Reported to the stx mailing list: https:/
It was seen that after 24 hours of operation, a worker node lost connectivity over the management network. The management network was assigned to a bonded interface.
systemctl status networking.service showed a failure to bring up the bonded interface:
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Fri 2023-03-10 15:28:30 UTC; 12s ago
Docs: man:interfaces(5)
Process: 395870 ExecStart=
Main PID: 395870 (code=exited, status=1/FAILURE)
CPU: 311ms
This appears to be a known bug in the ifenslave 2.12 Debian package
Severity
--------
Major: System/Feature is usable but degraded
Steps to Reproduce
------------------
Created a bonded platform interface:
system host-if-add controller-0 -c platform -a balanced -x layer2 ae0 ae enp0s9 enp0s10
systemctl stop networking.service
systemctl start networking.service
systemctl status networking.service
Expected Behavior
------------------
The bonded interface should come up
Actual Behavior
----------------
The bonded interface does not come up
Reproducibility
---------------
100%
System Configuration
-------
N/A
Branch/Pull Time/Commit
-------
stx 8.0
Last Pass
---------
Unknown but probably worked in stx 7.0
Timestamp/Logs
--------------
N/A
Test Activity
-------------
Unknown
Workaround
----------
This appears to have been fixed in ifenslave 2.13:
https:/
https:/
https:/
Not tested but the issue would probably also be solved with a host lock/unlock
Changed in starlingx: | |
assignee: | nobody → Fabiano Correa Mercer (fcorream) |
Changed in starlingx: | |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. opendev. org/c/starlingx /tools/ +/881769
Review: https:/