Bug 844347
| Summary: | 3.1 beta1 - VDSM: addNetwork Failed to attach bridge to bond interface | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Avi Tal <atal> | ||||||||
| Component: | vdsm | Assignee: | Igor Lvovsky <ilvovsky> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Meni Yakove <myakove> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | urgent | ||||||||||
| Version: | 6.3 | CC: | abaron, bazulay, cpelland, iheim, ilvovsky, lpeer, mavital, srevivo, ykaul | ||||||||
| Target Milestone: | beta | Keywords: | Regression | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | network | ||||||||||
| Fixed In Version: | vdsm-4.9.6-26.0 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-12-04 19:04:07 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: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 601223 [details]
engine log
I believe the error is due to premature ifup'ing of the bonding device: ::(ifup) can't add bond0 to bridge test-network: Invalid argument which has been caused by the fix http://gerrit.ovirt.org/6217 for bug 842338 (how come this was not found during pre-integration?). Please try this issue with the rhev-3.0 version of this fix. I found the same issue with different scenario: 1. create bond bridged network (via setupnetworks) # brctl show bridge name bridge id STP enabled interfaces rhevm 8000.001517a76a4c no eth0 sw2 8000.001d0968714e no bond0 2. edit bonding mode (via setupnetworks) # brctl show bridge name bridge id STP enabled interfaces rhevm 8000.001517a76a4c no eth0 sw2 8000.000000000000 no This will lead to the same result of nicless bridge. attaching vdsm log. Created attachment 601482 [details]
vdsm log using setupnetworks
verified on vdsm-4.9.6-26.0. Tested on SetupNetwork, RestAPI and vdsClient. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-1508.html |
Created attachment 601222 [details] vdsm log rhevm-3.1.0-9.el6ev.noarch (on cluster 3.1) vdsm-4.9.6-24.0.el6_3.x86_64 Description of problem: running addNetwork directly on host or using old REST API to attach bond interface to host leads to nicless bridge running: # vdsClient 0 addNetwork bridge=sw2 bond=bond0 nics=eth2,eth3 result: # brctl show bridge name bridge id STP enabled interfaces rhevm 8000.001517a76a4c no eth0 sw2 8000.000000000000 no note: this problem directly affect the creation of bond0 on sw2 via REST old API POST url: /api/hosts/ae11957e-d98d-11e1-b2c5-001a4a169763/nics body: <host_nic> <name>bond0</name> <network> <name>sw2</name> </network> <bonding> <slaves> <host_nic> <name>eth2</name> </host_nic> <host_nic> <name>eth3</name> </host_nic> </slaves> </bonding> </host_nic>