Red Hat Bugzilla – Bug 1262496
bonding option "primary" is considered invalid by vdsm
Last modified: 2016-02-10 14:16:20 EST
Description of problem:
hosted-engine --deploy fails with an error message saying that "primary" is not a valid option for a bond.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Networking setup
em1 & em2 are part of bond0
bond0.1000 (vlan) is built on bond0
2. ifcfg-bond0 has line
BONDING_OPTS="mode=active-backup primary=em1 primary-reselect=always"
3. Run hosted-engine --deploy and select the bond0.1000 interface for the engine.
(I am doing an FC install to a SAS LUN, if it matters)
4. Install will fail
Failure to build the hosted-engine. Error message says "primary" is not a valid bond option.
Continued install of the hosted-engine.
When I change the line in bond0 to
BONDING_OPTS="mode=active-backup" then hosted-engine --deploy succeeds.
Can you please check/attach relevant logs? At least hosted-engine setup - in /var/log/ovirt-hosted-engine-setup , perhaps also vdsm (/var/log/vdsm/*).
Also please 'rpm -qa | grep -i vdsm'.
I assume that the bond works well as-is, right?
Created attachment 1073345 [details]
ovirt-hosted-engine-setup log file
The network setup you will see in the log file is
em1 + em2 -> bond0
bond0.1000 VLAN has bridge virbr1000 with an IP
bond0.129 VLAN does not have a bridge or an IP and was the one specified in the hosted engine setup. Again, if I had 'BONDING_OPTS="mode=active-backup primary=em1 primary-reselect=always"' in the ifcfg.bond0 file the install would fail. If I changed that to 'BONDING_OPTS=mode=active-backup' the install would succeed.
The bond seems to work fine either way, I just prefer to have more control so the network traffic stats stay on one port.
It fails when calling vdscli setupNetworks . Dan - can you please have a look? Thanks.
"primary" is a valid bond option; Vdsm should have recognised it.
can you include vdsm version, supervdsm.log and the /var/lib/vdsm/bonding-defaults.json from the host?
Created attachment 1090786 [details]
Created attachment 1090787 [details]
Still seeing this error in the released version of oVirt 3.6.
vdsm version: vdsm-22.214.171.124-0.el7.centos.noarch
The supervdsm.log and bonding-defaults.json files are attached.
'primary' option will be recognized in the next 3.6 release (and of course in 4.0). Please just note that 'primary-reselect=always' should be spelled with an underscore otherwise it is also unknown :-)
To reporduce, set custom bond option
mode=active-backup primary=em1 primary-reselect=always
Please set target release or I can't move the bug to ON_QA automatically.
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Verified on - vdsm-4.17.13-1.el7ev.noarch
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.