Hi, i upgraded oVirt node to 4.2.3.1 version. After upgrade I can not migrate 
VM or run VM  on the node. After viewing logs file i find several errors. One 
of them:

2018-06-07 15:52:20,536+07 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(ForkJoinPool-1-worker-3) [] EVENT_ID: VM_DOWN_ERROR(119), VM 
ansible.example.com is down with error. Exit message: internal error: Process 
exited prior to exec: libvirt: Lock Driver error : Failed to ope
n socket to sanlock daemon: Permission denied.

I run setenforce 0 and VM can running on the node.


audit2allow -a


#============= setfiles_t ==============

#!!!! WARNING: 'bin_t' is a base type.
allow setfiles_t bin_t:file entrypoint;
allow setfiles_t self:capability sys_chroot;

#============= svirt_t ==============

#!!!! The file 
'/rhev/data-center/mnt/10.10.10.100:_var_nfs-ovirt-iso-share_files/dbf9ff5d-2cd4-408e-8a9d-08d39fa9a58a/images/11111111-1111-1111-1111-111111111111/CentOS-7-x86_64-Minimal-1708.iso'
 is mislabeled on your system.
#!!!! Fix with $ restorecon -R -v 
/rhev/data-center/mnt/10.10.10.100:_var_nfs-ovirt-iso-share_files/dbf9ff5d-2cd4-408e-8a9d-08d39fa9a58a/images/11111111-1111-1111-1111-111111111111/CentOS-7-x86_64-Minimal-1708.iso
#!!!! This avc can be allowed using the boolean 'virt_use_nfs'
allow svirt_t nfs_t:file open;

#!!!! The file '/run/sanlock/sanlock.sock' is mislabeled on your system.
#!!!! Fix with $ restorecon -R -v /run/sanlock/sanlock.sock
#!!!! This avc can be allowed using the boolean 'virt_use_sanlock'
allow svirt_t sanlock_t:unix_stream_socket connectto;

I run restorecon -R -v /run/sanlock/sanlock.sock, but it did not help
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VJCIWULSAP5EHFZPIFQHRECDYS3YZQM5/

Reply via email to