Can you provide clear steps to reproduce?
Making sure sanlock package on RHEL hosts equals to or bigger than sanlock-3.2.4-3.el7_2 should do
Vdsm requires sanlock >= 3.4.0-1, if you can install vdsm on the system this
bug can be verified.
This was fixed in:
Author: Allon Mureinik <email@example.com>
Date: Thu Jul 21 17:06:17 2016 +0300
spec: Require sanlock version handling EINTR
libsanlock was not handling EINTR, causing failures in sanlock calls
if vdsm received a signal while libsnalock was blocked in a syscall.
A typical case is when a child process terminates and vdsm receives a
When this happens, the vdsm operation fails with this error:
SanlockException: (4, 'Sanlock ...', 'Interrupted system call')
Signed-off-by: Allon Mureinik <firstname.lastname@example.org>
vdsm requires the correct Sanlock version which delivers a fix for this issue via bug 1356667
[root@storage-jenkins-ge4-vdsm1 ~]# yum deplist vdsm
dependency: sanlock >= 3.4.0-1
provider: sanlock.x86_64 3.4.0-1.el7
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.