Bug 858832
| Summary: | Sanlock service cannot start due to SELinux | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Rodrigo Trujillo <rotru> | ||||
| Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | bkabrda, cfeist, dominick.grift, dwalsh, fsimonce, gustavold, mgrepl, rotru, teigland, ybronhei | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | ppc64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-09-24 13:22:39 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
i also get an error while trying to start sanlock service: service sanlock status shows: sanlock daemon started 2.4 aio 1 10 renew 20 80 host 885008f5-17dc...348127889 set scheduler RR|RESET_ON_FORK priority 99 failed: Operation not permitted wdmd connect failed for watchdog handling I'd check if there is a newer selinux build you could try out. You can refer to bug 831908 where we're getting the selinux policy fixed in RHEL. Similar changes will probably be needed here. I just tested these selinux-policy packages new version and my problem is fixed: http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=712848 |
Created attachment 614528 [details] Logs from messages and audit.log Description of problem: Sanlock tries to start but then fails. The problem seems to be caused by selinux, because if it is in permissive state, the service starts properly. Version-Release number of selected component (if applicable): sanlock-2.4-2.fc17.ppc64 sanlock-python-2.4-2.fc17.ppc64 sanlock-lib-2.4-2.fc17.ppc64 selinux-policy-3.10.0-130.fc17.noarch libselinux-2.1.10-3.fc17.ppc64 libselinux-utils-2.1.10-3.fc17.ppc64 selinux-policy-targeted-3.10.0-130.fc17.noarch selinux-policy-devel-3.10.0-130.fc17.noarch libselinux-python-2.1.10-3.fc17.ppc64 How reproducible: Any time, if SELinux is in enforcing mode Steps to Reproduce: 1. Set SELinux to enforcing mode 2. Start sanlock service 3. Actual results: Service does not start Expected results: Sanlock service up and running Additional info: See logs attached.