Bug 805229
Summary: | rgmanager & selinux & vm services with path parameter | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Przemyslaw Sztoch <psztoch> |
Component: | resource-agents | Assignee: | Fabio Massimo Di Nitto <fdinitto> |
Status: | CLOSED WORKSFORME | QA Contact: | cluster-qe <cluster-qe> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | CC: | agk, cluster-maint, dwalsh, fdinitto, mgrepl |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-09-10 05:44:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Przemyslaw Sztoch
2012-03-20 17:08:36 UTC
Is auditd running? $ service auditd status Does it work in permissive mode? $ setenforce 0 If yes, then please execute $ semodule -DB re-test it and run $ ausearch -m avc -ts recent audit.log is empty. It was very strange for me. If SeLINUX is off, vm is created without any problem! I had modified vm.sh and created extra log file for "virsh create". Then I captured "error: Failed to open file '/srv/shared/vm/app1.xml': Permission denied" This problem was at production cluster and I can't easly turn on selinux, now. Of course if you do not use path argument, then vm.sh will use "virsh start". "virsh start" is working correctly. Only "virsh create" generates error. What is your version of policy? Cluster folks, could we test it? selinux-policy-targeted.noarch-3.7.19-126.el6_2.10 (and full upgrade) IMHO I am providing the requested information for you... Please, escalate this bug. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. Is this still a problem? I am doubtful there is anything to be done to fix this in the resource-agents package. I canĀ“t reproduce this problem in RHEL6.7. Please feel free to reopen the bug in case it is still an issue. |