Bonding interface does not come up after host-unlock
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Steven Webster |
Bug Description
Brief Description
-----------------
Adding a bond interface on a management or cluster-host network without a VLAN ontop can cause the bond interface to fail to come up after host-unlock.
Severity
--------
Major: System/Feature is usable but degraded
Steps to Reproduce
------------------
After bootstrap:
for i in $(system interface-
system host-if-modify controller-0 lo -c none
system host-if-add controller-0 -a active_standby -c platform bond0 ae ens2f0 ens2f1
system host-if-add controller-0 -a active_standby -c platform bond1 ae ens3f0 ens3f1
system host-if-add -V 755 -c platform controller-0 mgmt0 vlan bond1
system host-if-add -V 754 -c platform controller-0 oam0 vlan bond1
system interface-
system interface-
system interface-
system interface-
system host-unlock controller-0
Expected Behavior
------------------
The bond0 interface should be up.
Actual Behavior
----------------
The bond0 interface is not up.
Reproducibility
---------------
100%
System Configuration
-------
N/A
Branch/Pull Time/Commit
-------
master
Last Pass
---------
N/A
This code has been in place for a couple years, but most configs have cluster-host and mgmt on a VLAN which is why this hasn't been seen previously.
Test Activity
-------------
Evaluation
Workaround
----------
Remove the following from the /etc/sysconfig/
/sbin/modprobe bonding; echo +bond0 > /sys/class/
then ifup <bond-interface>
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.8.0 |
Fix proposed to branch: master /review. opendev. org/c/starlingx /config/ +/849905
Review: https:/