Description of problem: I have network vm_mtu_9000 attach to bond0 and VM1 is running with this network attached to it. When I try to break bond0 and attach vm_mtu_9000 to interface I got error: MainProcess|Thread-205192::ERROR::2012-11-11 13:45:57,309::configNetwork::1373::setupNetworks::(setupNetworks) (23, "delNetwork: ['eth2', 'eth3', 'vnet1'] are not all nics enslaved to bond0") Traceback (most recent call last): File "/usr/share/vdsm/configNetwork.py", line 1315, in setupNetworks implicitBonding=False) File "/usr/share/vdsm/configNetwork.py", line 1068, in delNetwork (nics, bonding)) ConfigNetworkError: (23, "delNetwork: ['eth2', 'eth3', 'vnet1'] are not all nics enslaved to bond0") MainProcess|Thread-205192::ERROR::2012-11-11 13:45:57,318::supervdsmServer::68::SuperVdsm.ServerCallback::(wrapper) Error in setupNetworks Traceback (most recent call last): File "/usr/share/vdsm/supervdsmServer.py", line 66, in wrapper return func(*args, **kwargs) File "/usr/share/vdsm/supervdsmServer.py", line 118, in setupNetworks return configNetwork.setupNetworks(networks, bondings, **options) File "/usr/share/vdsm/configNetwork.py", line 1315, in setupNetworks implicitBonding=False) File "/usr/share/vdsm/configNetwork.py", line 1068, in delNetwork (nics, bonding)) ConfigNetworkError: (23, "delNetwork: ['eth2', 'eth3', 'vnet1'] are not all nics enslaved to bond0") Thread-205192::ERROR::2012-11-11 13:45:57,319::API::1138::vds::(setupNetworks) delNetwork: ['eth2', 'eth3', 'vnet1'] are not all nics enslaved to bond0 Traceback (most recent call last): File "/usr/share/vdsm/API.py", line 1136, in setupNetworks supervdsm.getProxy().setupNetworks(networks, bondings, options) File "/usr/share/vdsm/supervdsm.py", line 69, in __call__ return callMethod() File "/usr/share/vdsm/supervdsm.py", line 60, in <lambda> **kwargs) File "<string>", line 2, in setupNetworks File "/usr/lib64/python2.6/multiprocessing/managers.py", line 740, in _callmethod raise convert_to_error(kind, result) ConfigNetworkError: (23, "delNetwork: ['eth2', 'eth3', 'vnet1'] are not all nics enslaved to bond0") Version-Release number of selected component (if applicable): vdsm-4.9.6-41.0.el6_3.x86_64 How reproducible: 100% Steps to Reproduce: 1.Create BOND and attach network with costum MTU.(vm_mtu_9000) 2.Create VM with network vm_mtu_9000 3.Open setupnetworks and try to break the bond. Actual results: Faild with the above exaction
Created attachment 642902 [details] vdsm.log
Steps to Reproduce: 1.Create BOND and attach network with costum MTU.(vm_mtu_9000) 2.Create VM with network vm_mtu_9000 and start the VM 3.Open setupnetworks and try to break the bond while the VM is running.
http://gerrit.ovirt.org/#/c/9384
the current solution still doesn't allow to break the bond, but raise proper error and leave the state as is. In the future we might consider to allow to break the bond and disconnect VM from the external world
Verified on: vdsm-4.10.2-3.0.el6ev.x86_64 rhevm-3.2.0-4.el6ev.noarch Error: navy-vds3: Cannot setup Networks. The following VMs are actively using the Logical Network: vm32. Please stop the VMs and try again. Get proper error.
This bug is currently attached to errata RHBA-2012:14332. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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-2013-0886.html