Bug 826467
| Summary: | 3.1 - [vdsm][setupNetworks] Failed to remove bond & attach network to NIC | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Mike Kolesnik <mkolesni> |
| Component: | vdsm | Assignee: | Igor Lvovsky <ilvovsky> |
| Status: | CLOSED ERRATA | QA Contact: | Meni Yakove <myakove> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3 | CC: | abaron, bazulay, cpelland, danken, iheim, lpeer, yeylon, ykaul |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | network | ||
| Fixed In Version: | vdsm-4.9.6-17.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-12-04 18:58:42 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: | |||
Verified on vdsm-4.9.6-23.0.el6_3.x86_64. 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 |
Description of problem: Tried to remove a bond over eth1 & eth3, and attach a network to eth3: MainProcess|Thread-108::DEBUG::2012-05-30 09:46:42,245::configNetwork::998::setupNetworks::(setupNetworks) Setting up network according to configuration: networks:{'test': {'nic': 'eth3', 'bridged': 'true'}}, bondings:{'bond4': {'remove': 'true'}}, options:{'connectivityCheck': 'true', 'connectivityTimeout': '60000'} This failed due to: Thread-108::ERROR::2012-05-30 09:46:42,867::API::1158::vds::(setupNetworks) nic eth3 already enslaved to bond4 Traceback (most recent call last): File "/usr/share/vdsm/API.py", line 1156, in setupNetworks supervdsm.getProxy().setupNetworks(networks, bondings, options) File "/usr/share/vdsm/supervdsm.py", line 67, in __call__ return callMethod() File "/usr/share/vdsm/supervdsm.py", line 65, in <lambda> **kwargs) File "<string>", line 2, in setupNetworks File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod raise convert_to_error(kind, result) ConfigNetworkError: (24, 'nic eth3 already enslaved to bond4') Thread-108::DEBUG::2012-05-30 09:46:42,868::BindingXMLRPC::855::vds::(wrapper) return setupNetworks with {'status': {'message': 'nic eth3 already enslaved to bond4', 'code': 24}} Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create bond over 2 nics, with a network attached to the bond. 2. SetpuNetworks - remove the bond and add a network over one of the released NICs. 3. Actual results: Failure, Expected results: Remove the bond, and attach the network to the given nic. Additional info: