Starting VM after update Ovirt node

So I upgraded oVirt node to 4.2.6.1 version. After upgrade I was presented with not being able to migrate VM or run VM on the node.
I did go in engine logs and vdsm logs. I found bunch of errors but one did stand out

2018-10-04 13:55:57,810-0400 ERROR (vm/8917a3f3) [virt.vm] (vmId='xxx-xxx-xxx-xxx-xxx') The vm start process failed (vm:948)
 
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 877, in _startUnderlyingVm
    self._run()
  File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2895, in _run
    dom.createWithFlags(flags)
  File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 130, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92, in wrapper
    return func(inst, *args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1099, in createWithFlags
    if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
libvirtError: internal error: Process exited prior to exec: libvirt: Lock Driver error : Failed to open socket to sanlock daemon: Permission denied

Just like everyone else first thing I blamed was selinux and when I temporarly disabled it. I was able to migrate VMs again. So I did look to

audit2allow -a

showed that sanlock bool was not set by node install properly. So when I checked

getsebool -a | grep sanlock
 
sanlock_use_fusefs --> off
sanlock_use_nfs --> off
sanlock_use_samba --> off
virt_use_sanlock --> off

simply set both sanlock_use_fusefs and sanlock_use_fusefs needed to be set true.

using setsebool -P sanlock_use_fusefs on

I was able to set those and restarted vdsmd. This way I was able to get VMs migrating again.

Starting VM after update Ovirt node

Zenteric