Description of problem: VDSM fails to create bridgeless (non vm) network. After it fails if vdsmd service is restart it stack on: Thread-13::DEBUG::2013-07-13 17:40:36,608::BindingXMLRPC::979::vds::(wrapper) client [10.35.161.86]::call getCapabilities with () {} Thread-13::DEBUG::2013-07-13 17:40:36,608::BindingXMLRPC::986::vds::(wrapper) return getCapabilities with {'status': {'message': 'Recovering from crash or Initializing', 'code': 99}} and the host is in Initializing on rhevm. Version-Release number of selected component (if applicable): vdsm-4.12.0-rc1.12.git8ee6885.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.create net1(non vm) on dc and attach it to cluster 2.open setupnetwork and attach net1 to interface Actual results: net1 bridgeless network wasn't created Expected results: net1 bridgeless network created Additional info: from vdsm log: Traceback (most recent call last): File "/usr/share/vdsm/BindingXMLRPC.py", line 984, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/BindingXMLRPC.py", line 413, in setupNetworks return api.setupNetworks(networks, bondings, options) File "/usr/share/vdsm/API.py", line 1259, in setupNetworks supervdsm.getProxy().setupNetworks(networks, bondings, options) File "/usr/share/vdsm/supervdsm.py", line 57, in __call__ raise ex IndexError: list index out of range from virsh net-dumpxml: <network> <name>vdsm-sw1</name> <uuid>28829a4f-babc-3193-a94e-6c055874cdb9</uuid> <forward mode='passthrough'/> </network>
Created attachment 775300 [details] engine and vdsm logs
removeing net1 (non vm) network from libvirt using virsh solve the vdsm service problem ({'message': 'Recovering from crash or Initializing', 'code': 99}})
vdsm-4.12.0-rc3.12.git139ec2f.el6ev.x86_64
This bug is currently attached to errata RHBA-2013:15291. 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.
This issue was introduced and solved during the rhev-3.3 development cycle. No reason to report it to customers.
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/RHBA-2014-0040.html