Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
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: