Bug 832758
| Summary: | SetupNetwrks | Can't create BOND without attached network | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Meni Yakove <myakove> | ||||||||
| Component: | vdsm | Assignee: | Dan Kenigsberg <dkenigsb> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Meni Yakove <myakove> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 6.4 | CC: | abaron, acathrow, bazulay, danken, dyasny, iheim, ilvovsky, lpeer, mkolesni, mpavlik, Rhev-m-bugs, yeylon, ykaul | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | 6.4 | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | network | ||||||||||
| Fixed In Version: | vdsm-4.9.6-25.0 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-07-30 17:17:25 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 840699 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Meni Yakove
2012-06-17 08:06:09 UTC
Created attachment 592389 [details]
vdsm.log
Created attachment 592390 [details]
engine.log
logical networks or physical networks. assuming the latter, i'd say correct behavior is to not allow creating the bond without specifying at least two physical networks it bonds. (In reply to comment #3) > logical networks or physical networks. > assuming the latter, i'd say correct behavior is to not allow creating the > bond without specifying at least two physical networks it bonds. Create BOND using physical networks and do not attached logical networks to it. If we must attached logical network to the BOND the 'OK' button should be grayed out if we didn't attached any logical network to the BOND. (In reply to comment #5) > Create BOND using physical networks and do not attached logical networks to > it. > If we must attached logical network to the BOND the 'OK' button should be > grayed out if we didn't attached any logical network to the BOND. No need to gray out, this is a VDSM side bug so please update product/component. Additionally, it might've been fixed already. Igor can you comment please? (In reply to comment #6) > No need to gray out, this is a VDSM side bug so please update > product/component. Mike, I fully trust your ability to do it I believe this has been fixed by http://gerrit.ovirt.org/5487 of vdsm-4.9.6-17.0. Please verify. all important files is attached in attached logs.tar.gz
With vdsm-4.9.6-17.0.el6.x86_64 it is possible to create empty bond. However the bond is started in wrong mode. I selected bond mode1 (active-backup), but bond starts with mode0 (round-robin).
in vdsm.log it is visible that bondmode=1 is sent
Thread-62::DEBUG::2012-07-11 11:27:32,047::BindingXMLRPC::864::vds::(wrapper) client [10.34.63.65]::call setupNetworks with ({}, {'bond1': {'nics': ['p1p1', 'p1p2'], 'options': 'mode=1 miimon=100'}}, {'connectivityCheck': 'true', 'connectivityTimeout': 60000}) {} flowID [1472104]
ifcfg file is created correctly
[root@dell-r210ii-05 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond1
DEVICE=bond1
ONBOOT=yes
BOOTPROTO=none
BONDING_OPTS='mode=1 miimon=100'
NM_CONTROLLED=no
but bond is running in mode 0 (roun-robin)
[root@dell-r210ii-05 ~]# cat /proc/net/bonding/bond1
Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Bonding Mode: load balancing (round-robin)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: p1p1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: 90:e2:ba:04:2d:74
Slave queue ID: 0
Slave Interface: p1p2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: 90:e2:ba:04:2d:75
Slave queue ID: 0
Maybe this is related to following WARNING from vdsm.log
MainProcess|Thread-62::WARNING::2012-07-11 11:27:32,508::configNetwork::83::root::(ifup) /etc/sysconfig/network-scripts/ifup-eth: line 136: echo: write error: Operation not permitted
Created attachment 597519 [details]
logs
*** This bug has been marked as a duplicate of bug 842338 *** |