Description of problem: According with bz#1349218 vdsm 3.5 will be rebuild only in case of critical updates so there is no space for adding new VDSM requirements. In that case, it's required to workaround via ovirt-node.
To test this bug the rhev-h image must have: sanlock-2.8-3.el6.x86_64 or higher sanlock-lib-2.8-3.el6.x86_64 or higher sanlock-python-2.8-3.el6.x86_64 or higher and vdsm must be part of sanlock and qemu groups. # cat /etc/redhat-release Red Hat Enterprise Virtualization Hypervisor release 6.8 (20160630.2.el6ev) # rpm -qa | grep -i sanlock sanlock-lib-2.8-3.el6.x86_64 sanlock-2.8-3.el6.x86_64 sanlock-python-2.8-3.el6.x86_64 libvirt-lock-sanlock-0.10.2-60.el6.x86_64 # grep vdsm /etc/group sanlock:x:179:vdsm qemu:x:107:vdsm,sanlock
Verified using package rhev-hypervisor6-6.8-20160707.3 [root@hp-dl585g7-03 data]# cat /etc/redhat-release Red Hat Enterprise Virtualization Hypervisor release 6.8 (20160707.3.el6ev) [root@hp-dl585g7-03 data]# rpm -qa | grep -i sanlock sanlock-2.8-3.el6.x86_64 sanlock-lib-2.8-3.el6.x86_64 sanlock-python-2.8-3.el6.x86_64 libvirt-lock-sanlock-0.10.2-60.el6.x86_64 [root@hp-dl585g7-03 data]# grep vdsm /etc/group sanlock:x:179:vdsm qemu:x:107:vdsm,sanlock
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. https://rhn.redhat.com/errata/RHEA-2016-1557.html