Description of problem: I tried to create bond in mode 1 via Setup Hosts Network dialog (screenshot 1), but I ended up with bond in mode 4 (screenshot 2) according to VDSM log at first everything seems to be sent correctly ('BONDING_OPTS': 'mode=1 miimon=100') Thread-15::DEBUG::2012-05-25 10:22:45,515::BindingXMLRPC::864::vds::(wrapper) client [10.34.63.65]::call setupNetworks with ({'rhevm': {'nic': 'em1', 'BOOTPROTO': 'dhcp', 'bridged': 'true'}, 'NET1': {'bonding': 'bond1', 'ipaddr': '10.34.67.56', 'gateway': '0.0.0.0', 'bridged': 'true', 'netmask': '255.255.255.224'}}, {'bond4': {'remove': 'true'}, 'bond0': {'remove': 'true'}, 'bond1': {'nics': ['p1p1', 'p1p2'], 'BONDING_OPTS': 'mode=1 miimon=100'}, 'bond2': {'remove': 'true'}, 'bond3': {'remove': 'true'}}, {'connectivityCheck': 'true', 'connectivityTimeout': '60000'}) {} flowID [4568e5bb] but in further steps bonding options get lost (bondingOptions=None) MainProcess|Thread-15::INFO::2012-05-25 10:22:53,360::configNetwork::595::root::(addNetwork) Adding network NET1 with vlan=None, bonding=bond1, nics=['p1p1', 'p1p2'], bondingOptions=None, mtu=None, bridged=True, options={} this makes rhevm to use default bonding mode 4. Version-Release number of selected component (if applicable): oVirt Enterprise Virtualization Engine Manager Version: 3.1.0_0001-11.el6ev How reproducible: 100% Steps to Reproduce: have one logical network in cluster (other than rhevm) 1. Hosts -> your host -> Network Interfaces -> Setup Host Networks 2. drag one free interface across another free interface -> choose bonding mode 1 -> click OK 3. drag your logical network to new bond 4. click pencil icon on the bond a) make sure bonding mode is set to Mode 1 b) choose boot protocol static c) fill in IP/MASK , put 0.0.0.0 to Default Gateway d) click OK 5. click OK Actual results: bond is always created with bonding mode 4 Expected results: bond should get created with mode which is chosen via GUI Additional info: it does not really matter which bonding mode is chosen, bond is always created with bonding mode 4
Created attachment 586804 [details] screenshot 1
Created attachment 586805 [details] screenshot 2
Created attachment 586806 [details] vdsm.log + engine.log
What does /proc/net/bonding/bondX contain when bondingOptions=None?
Sorry, I should have mentioned that it is in attachment with logs DEVICE=bond1 ONBOOT=yes BOOTPROTO=none BRIDGE=NET1 BONDING_OPTS='mode=802.3ad miimon=150' NM_CONTROLLED=no Seems that it is options which are used, when you try to create custom bond with empty options.
This is a backend bug and Automation test blocker. it blocks us from testing different bonding modes
*** Bug 828171 has been marked as a duplicate of this bug. ***
http://gerrit.ovirt.org/#/c/5088/
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=fefcccdb56b6fffc1fac1daa4a7f9d29dc739a25
Verified, now bond in mode can be created