Bug 681792 - [vdsm] When stopping multiple vms and restarting libvirtd vdsm dose not taking it self down and vms reported as UP* (Non-responsive)
Summary: [vdsm] When stopping multiple vms and restarting libvirtd vdsm dose not takin...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Dan Kenigsberg
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-03 09:21 UTC by David Naori
Modified: 2016-04-18 06:38 UTC (History)
10 users (show)

Fixed In Version: vdsm-4.9-52.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-19 15:05:49 UTC
Target Upstream Version:

Attachments (Terms of Use)
full log (2.61 MB, application/x-gzip)
2011-03-03 09:57 UTC, David Naori 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description David Naori 2011-03-03 09:21:55 UTC 
Description of problem:
When stopping vms and restarting libvirtd, vdsm prints the following error:
Thread-30913::ERROR::2011-03-03 10:37:37,968::utils::428::vm.Vm::(run) vmId=`aeacf1e5-28a1-42a4-8870-62f7ecfb2089`::Traceback (most recent call last):
  File "/usr/share/vdsm/utils.py", line 418, in run
    sample = self.sample()
  File "/usr/share/vdsm/vm.py", line 137, in sample
    s = self.VmSampleClass(self._pid, self._ifids, self._vm)
  File "/usr/share/vdsm/libvirtvm.py", line 79, in __init__
    raise e
libvirtError: server closed connection:

and dose not preform restart.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 David Naori 2011-03-03 09:57:18 UTC 
Created attachment 482023 [details]
full log
Comment 3 David Naori 2011-03-03 09:57:30 UTC 
[vdsm] When stopping multiple vms and restarting libvirtd vdsm dose not taking itself down and vms reported as UP* (Non-responsive)

iption of problem:
When stopping vms and restarting libvirtd, vdsm prints the following error:
Thread-30913::ERROR::2011-03-03 10:37:37,968::utils::428::vm.Vm::(run) vmId=`aeacf1e5-28a1-42a4-8870-62f7ecfb2089`::Traceback (most recent call last):
  File "/usr/share/vdsm/utils.py", line 418, in run
    sample = self.sample()
  File "/usr/share/vdsm/vm.py", line 137, in sample
    s = self.VmSampleClass(self._pid, self._ifids, self._vm)
  File "/usr/share/vdsm/libvirtvm.py", line 79, in __init__
    raise e
libvirtError: server closed connection:

and dose not taking itself down, after couple of minutes vdsm reports the vms as UP* (Non responsive) while they are actually Up. 

Version-Release number of selected component (if applicable):

-vdsm-4.9-51
-libvirt-0.8.7-8

How reproducible:
50%

Reproduce steps:
-stop 10 vms and restart libvirtd 

full vdsm log attached.
Comment 4 David Naori 2011-03-08 13:19:34 UTC 
Verified on vdsm-4.9-52



Thread-252::ERROR::2011-03-08 15:13:08,708::utils::429::vm.Vm::(run) vmId=`29174ab3-fd08-4e67-844b-9aa38f6f01e1`::Traceback (most recent call last):
  File "/usr/share/vdsm/utils.py", line 419, in run
    sample = self.sample()
  File "/usr/share/vdsm/vm.py", line 137, in sample
    s = self.VmSampleClass(self._pid, self._ifids, self._vm)
  File "/usr/share/vdsm/libvirtvm.py", line 79, in __init__
    raise e
libvirtError: server closed connection:



....



Thread-333::DEBUG::2011-03-08 15:13:15,197::taskManager::69::TaskManager::(prepareForShutdown) Request to stop all tasks
Note You need to log in before you can comment on or make changes to this bug.