Bug 825151 - [RHEVM] [backend] [Setup Host Networks] bonding options are not handed over correctly
Summary: [RHEVM] [backend] [Setup Host Networks] bonding options are not handed over c...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.0
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: ---
: ---
Assignee: Mike Kolesnik
QA Contact: Martin Pavlik
URL:
Whiteboard: network
: 828171 (view as bug list)
Depends On:
Blocks: 709060 830832
TreeView+ depends on / blocked
 
Reported: 2012-05-25 08:59 UTC by Martin Pavlik
Modified: 2019-04-28 09:27 UTC (History)
9 users (show)

Fixed In Version: SI6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 19:58:39 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot 1 (136.78 KB, image/png)
2012-05-25 09:01 UTC, Martin Pavlik
no flags Details
screenshot 2 (138.90 KB, image/png)
2012-05-25 09:08 UTC, Martin Pavlik
no flags Details
vdsm.log + engine.log (5.76 KB, application/x-gzip)
2012-05-25 09:08 UTC, Martin Pavlik
no flags Details

Description Martin Pavlik 2012-05-25 08:59:12 UTC
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

Comment 1 Martin Pavlik 2012-05-25 09:01:49 UTC
Created attachment 586804 [details]
screenshot 1

Comment 2 Martin Pavlik 2012-05-25 09:08:28 UTC
Created attachment 586805 [details]
screenshot 2

Comment 3 Martin Pavlik 2012-05-25 09:08:54 UTC
Created attachment 586806 [details]
vdsm.log + engine.log

Comment 4 Avi Tal 2012-05-26 21:09:29 UTC
What does /proc/net/bonding/bondX contain when bondingOptions=None?

Comment 5 Martin Pavlik 2012-05-28 06:10:12 UTC
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.

Comment 6 Avi Tal 2012-06-07 06:38:34 UTC
This is a backend bug and Automation test blocker. it blocks us from testing different bonding modes

Comment 7 Avi Tal 2012-06-07 06:50:14 UTC
*** Bug 828171 has been marked as a duplicate of this bug. ***

Comment 9 Mike Kolesnik 2012-06-07 08:25:42 UTC
http://gerrit.ovirt.org/#/c/5088/

Comment 11 Martin Pavlik 2012-06-15 10:40:32 UTC
Verified, now bond in mode can be created


Note You need to log in before you can comment on or make changes to this bug.