Red Hat Bugzilla – Bug 1278051
All-In-One: sanlock: Cannot acquire host id
Last modified: 2016-02-22 09:05:20 EST
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.install ovirt 3.6 all-in-one
5.add local data storage domain for local-host
Error while executing action New Local Storage Domain: AcquireHostIdFailure
add local data storage domain success
VDSM 18.104.22.168 command failed: Cannot acquire host id: (u'805bc73e-21d6-490f-9348-62b994e7f388', SanlockException(19, 'Sanlock lockspace add failure', 'No such device'))
*** Bug 1278050 has been marked as a duplicate of this bug. ***
Please attach logs:
Created attachment 1090682 [details]
added all the logs.
Nir, any news on that one? Logs are attached
(In reply to Tal Nisan from comment #4)
I can check this next week.
From the messages log, we can see that SE Linux is preventing Sanlock access:
Nov 4 22:20:49 localhost sanlock: 2015-11-04 22:20:49+0800 884 : open error -13 /rhev/data-center/mnt/_home_data/d65c4762-bd59-4ac7-ab49-4a05fa4d61dc/dom_md/ids
Nov 4 22:20:49 localhost python: SELinux is preventing /usr/sbin/sanlock from 'read, write' accesses on the file ids.
***** Plugin catchall (100. confidence) suggests **************************
If you believe that sanlock should be allowed read write access on the ids file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
allow this access for now by executing:
# grep sanlock /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
Can you retry with SElinux on permissive mode ?
Also, can you please provide AVC log from SElinux ? - best way is with ausearch
(In reply to Fred Rolland from comment #7)
> Bo hi,
> Can you retry with SElinux on permissive mode ?
> Also, can you please provide AVC log from SElinux ? - best way is with
I will retry this week.
I have checked on 7.2 and it works fine also on Enforcing mode.
Ovirt 3.6 should work with 7.2
*** This bug has been marked as a duplicate of bug 1305768 ***
This issue is not present in ovirt 3.6, it was introduced in master later (future 4.0.0)