commit I0f88ebcab07dea20a0288f6b75c5888a74d9e440 (feature "automatically unpause vms in EIO when SD becomes active") broke vdsm on VM shutdown error looks like: libvirtEventLoop::INFO::2013-08-01 01:09:30,866::vm::4214::vm.Vm::(releaseVm) vmId=`3b98c785-b090-4b09-aca9-32f779ca4034`::Release VM resources libvirtEventLoop::DEBUG::2013-08-01 01:09:30,867::sampling::292::vm.Vm::(stop) vmId=`3b98c785-b090-4b09-aca9-32f779ca4034`::Stop statistics collection Thread-408::ERROR::2013-08-01 01:09:30,865::BindingXMLRPC::998::vds::(wrapper) unexpected error 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 211, in vmDestroy return vm.destroy() File "/usr/share/vdsm/API.py", line 322, in destroy res = v.destroy() File "/usr/share/vdsm/vm.py", line 4278, in destroy response = self.releaseVm() File "/usr/share/vdsm/vm.py", line 4246, in releaseVm self.cif.removeVmFromMonitoredDomains(self.id) File "/usr/share/vdsm/clientIF.py", line 125, in removeVmFromMonitoredDomains for dom in self.domainVmIds: RuntimeError: dictionary changed size during iteration
Setting Target Milestone Beta1.
*** Bug 994551 has been marked as a duplicate of this bug. ***
verified using is10 Now we can poweroff VM without any problems.
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.
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