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
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.
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.