Bug 1230371
Summary: | [SELinux]: [Snapshot]: SELinux policy updates required in RHEL-6.7 for gluster-snapshot | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Prasanth <pprakash> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.7 | CC: | ashah, dwalsh, lvrabec, mgrepl, mmalik, plautrba, pprakash, pvrabec, rjoseph, senaik, ssekidde, storage-qa-internal, tlavigne |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-3.7.19-276.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1230202 | Environment: | |
Last Closed: | 2015-07-22 07:14:46 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: | |||
Bug Depends On: | 1230202 | ||
Bug Blocks: | 1212796, 1223636 |
Description
Prasanth
2015-06-10 17:54:46 UTC
The gluster daemon wants to run xfs_db tool. Unfortunately, xfs_db is labeled bin_t instead of fsadm_exec_t, therefore xfs_db process does not run in correct doman. If you run following commands before your tests: # semanage fcontext -a -t fsadm_exec_t /usr/sbin/xfs_db # restorecon -Rv /usr/sbin does it help? Created snapshot with latest policy and could not see avc logs. [root@darkknightrises audit]# rpm -qa | grep selinux selinux-policy-targeted-3.7.19-276.el6.noarch libselinux-2.0.94-5.8.el6.x86_64 libselinux-utils-2.0.94-5.8.el6.x86_64 selinux-policy-3.7.19-276.el6.noarch libselinux-python-2.0.94-5.8.el6.x86_64 [root@darkknightrises audit]# rpm -q policycoreutils policycoreutils-2.0.83-24.el6.x86_64 *** Bug 1234298 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1375.html |