Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 681792

Summary: [vdsm] When stopping multiple vms and restarting libvirtd vdsm dose not taking it self down and vms reported as UP* (Non-responsive)
Product: Red Hat Enterprise Linux 6 Reporter: David Naori <dnaori>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED CURRENTRELEASE QA Contact: yeylon <yeylon>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1CC: abaron, bazulay, danken, dnaori, hateya, iheim, ilvovsky, mgoldboi, srevivo, ykaul
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: vdsm-4.9-52.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-19 15:05:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
full log none

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