Red Hat Bugzilla – Bug 1292214
HE deploy on NFS failed with sanlock error
Last modified: 2015-12-16 13:57:46 EST
Created attachment 1106502 [details] setup, vdsm and sanlock logs Description of problem: HE deploy failed with sanlock error Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/sanlock/lockspace.py", line 229, in _misc offset=offset SanlockException: (19, 'Sanlock lockspace write failure', 'No such device') 2015-12-16 20:16:27 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Misc configuration': (19, 'Sanlock lockspace write failure', 'No such device') Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.2.6.1-1.el7ev.noarch vdsm-4.16.31-1.el7ev.x86_64 How reproducible: Always Steps to Reproduce: 1. Run hosted-engine --deploy 2. Choose deploy on NFS and continue deployment 3. Actual results: Deployment failed [ INFO ] Connecting Storage Pool [ INFO ] Verifying sanlock lockspace initialization [ ERROR ] Failed to execute stage 'Misc configuration': (19, 'Sanlock lockspace write failure', 'No such device') [ INFO ] Stage: Clean up Expected results: Deployment succeed without any errors Additional info:
Looks like problem in selinux, # setenforce 0 solve problem selinux-policy-targeted-3.13.1-23.el7.noarch selinux-policy-3.13.1-23.el7.noarch Dec 16 20:38:37 alma07 kernel: type=1400 audit(1450291117.396:42): avc: denied { read } for pid=667 comm="sanlock" name="8c39aace-dcad-4ca3-a2fe-e0d47351fa5f" dev="tmpfs" ino=102783 scontext=system_u:system_r:sanlock_t:s0-s0:c0.c1023 tcontext=system_u:object_r:virt_var_run_t:s0 tclass=lnk_file
My mistake host had after reprovision old packages, after update all host packages deployment works fine.