Description of problem:
After an update or fresh install, the bond mode defaults to round-robin which causes configured port channel in switches to go down.
Would it be possible to add a bonding configuration within the undercloud.conf file in order to prevent this from happening?
Each time the following command are executed:
openstack undercloud install
openstack undercloud upgrade
The following line disappear:
BONDING_OPTS="mode=802.3ad ad_select=bandwidth lacp_rate=fast xmit_hash_policy=layer2+3 miimon=100"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure bond
2. Run openstack undercloud install
Bond shouldn't break
Any update on this and when and if we might see fixed?
(In reply to David Hill from comment #0)
> Description of problem:
> After an update or fresh install, the bond mode defaults to round-robin
> which causes configured port channel in switches to go down.
> Would it be possible to add a bonding configuration within the
> undercloud.conf file in order to prevent this from happening?
> Each time the following command are executed:
> openstack undercloud install
> openstack undercloud upgrade
> The following line disappear:
> BONDING_OPTS="mode=802.3ad ad_select=bandwidth lacp_rate=fast
> xmit_hash_policy=layer2+3 miimon=100"
From what file does this line disappear? Is it an interface config file under /etc/sysconfig/network-scripts? If so, is os-net-config managing that interface?
If it is, then it's expected behavior that os-net-config regenerates those files when the undercloud commands are run.
How is the line getting there in the first place? I'm not sure it's even possible to represent these bonding options for an undercloud install.
This is as expected as the undercloud does not support bonding - see the future feature request here: https://bugzilla.redhat.com/show_bug.cgi?id=1385041.
The undercloud is expecting that there exists a single interface used for provisioning.
Marking this as a duplicate to the bug tracking bonding in the undercloud so that updates and status can be kept on one place.
*** This bug has been marked as a duplicate of bug 1385041 ***