Bug 881745

Summary: vdsm: vdsm does not restart on hsm when connectivity to the NFS storage is blocked
Product: Red Hat Enterprise Virtualization Manager Reporter: Dafna Ron <dron>
Component: vdsmAssignee: Yaniv Bronhaim <ybronhei>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 3.1.3CC: abaron, acathrow, bazulay, dron, hateya, iheim, jkt, lpeer, smizrahi, ybronhei
Target Milestone: ---Keywords: Reopened
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: 2013-09-01 08:11:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
logs none

Description Dafna Ron 2012-11-29 14:03:26 UTC
Created attachment 654296 [details]
logs

Description of problem:

I blocked connectivity to the NFS storage domain from 2 out of 3 of my hosts. 
the vdsm service in the second host (not the spm) did not restart (no prepareForShutdown is called). 

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

vdsm-4.9.6-44.0.el6_3.x86_64
libvirt-0.9.10-21.el6_3.6.x86_64
qemu-img-rhev-0.12.1.2-2.295.el6_3.5.x86_64
qemu-kvm-rhev-0.12.1.2-2.295.el6_3.5.x86_64

How reproducible:

100%

Steps to Reproduce:
1. in 3 hosts cluster with 1 NFS storage domain, block connectivity to the storage domain from 2 out of the 3 hosts (spm + other) using iptables
2.
3.
  
Actual results:

vdsm does not restart in the hsm blocked host

Expected results:

vdsm should restart 

Additional info: logs

Comment 1 RHEL Program Management 2012-12-14 07:50:17 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 Yaniv Bronhaim 2013-04-02 10:48:43 UTC
Storage block handling should restart vdsm only on SPM. This is handled by sanlock when the connectivity to the storage is lost, sanlock sends SIGTERM for 40sec and SIGKILL if vdsm still up.

prepareForShutdown is called when SIGTERM is received, but over HSM host it's never meant to happened.