Bug 833772

Summary: 3.1 - prepareForShutdown is not executed when connection to libvirt is broken
Product: Red Hat Enterprise Linux 6 Reporter: vvyazmin <vvyazmin>
Component: vdsmAssignee: Gal Hammer <ghammer>
Status: CLOSED DUPLICATE QA Contact: Haim <hateya>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3CC: abaron, bazulay, danken, hateya, iheim, yeylon, ykaul
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-16 07:16:09 UTC Type: Bug
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
vdsm and libvirtd logs none

Description vvyazmin@redhat.com 2012-06-20 10:40:53 UTC
Created attachment 593173 [details]
vdsm and libvirtd logs

Description of problem:
prepareForShutdown is not executed when connection to libvirt is broken (libvirtError: Cannot write data: Broken pipe)

Version-Release number of selected component (if applicable):
vdsm-4.9.6-16.0.el6.x86_64

Actual results:
1. In RHEVM --> Hosts tab --> host in “unassigned” status.
2. VDSM not “recreate” a new connection, in case of connection to LIBVIRT is broken.

Expected results:
1. In RHEVM --> Hosts tab --> host in “up” status.
2. VDSM “recreate” a new connection, in case of connection to LIBVIRT is broken.

Workaround:
# /etc/init.d/vdsmd restart

Comment 2 Barak 2012-07-15 15:51:52 UTC
Please provide libvirt logs (reason for being down) & vdsm logs.

How did you use the prepareForShutdown ? through vdsmCli ?

Comment 3 Haim 2012-07-16 07:16:09 UTC
(In reply to comment #2)
> Please provide libvirt logs (reason for being down) & vdsm logs.
> 
> How did you use the prepareForShutdown ? through vdsmCli ?

no, vdsm should take itself down on such case, anyhow, its a duplicate bug,

*** This bug has been marked as a duplicate of bug 834041 ***