Hide Forgot
Created attachment 504983 [details] vdsm log Description of problem: in case libvirtd is non-responsive restarting libvirtd will triger vdsm prepareForShutdown which will hang forever on: Thread-264::ERROR::2011-06-16 09:37:43,020::clientIF::63::vds::(wrapper) Traceback (most recent call last): File "/usr/share/vdsm/clientIF.py", line 59, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/clientIF.py", line 892, in getVdsCapabilities self.machineCapabilities = self._getCapabilities() File "/usr/share/vdsm/clientIF.py", line 862, in _getCapabilities ',' + ','.join(getCompatibleCpuModels()) File "/usr/share/vdsm/clientIF.py", line 823, in getCompatibleCpuModels in allModels if compatible(model) ] File "/usr/share/vdsm/clientIF.py", line 819, in compatible return c.compareCPU(xml, 0) in ( File "/usr/share/vdsm/libvirtconnection.py", line 59, in wrapper ret = f(*args, **kwargs) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1446, in compareCPU if ret == -1: raise libvirtError ('virConnectCompareCPU() failed', conn=self) libvirtError: cannot recv data: : Connection reset by peer (END) Version-Release number of selected component (if applicable): libvirt-0.9.1-1.el6.x86_64 vdsm-4.9-75.el6.x86_64 How reproducible: 100% Steps to Reproduce: on a host connected to storage pool and have no vms running do: 1 kill -19 `pgrep libvirt` 2 vdsClient -s 0 getVdsCaps & 3 /etc/init.d/libvirtd restart Additional info: *vdsm log attached
In a private communication Erez told me that the issue no longer reproduces now that Eduardo pool cleanup patchset is in. David, please reopen if you find refuting evindence.
unable to reproduce vdsm-4.9-79.el6.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/RHEA-2011-1782.html