Bug 1241386
Summary: | [SELinux] [nfs-ganesha]: seeing avc denied error message for showmount, while doing a volume start - Rhel6.7 | |||
---|---|---|---|---|
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: | high | Docs Contact: | Petr Bokoc <pbokoc> | |
Priority: | high | |||
Version: | 6.7 | CC: | akhakhar, ashah, dwalsh, jsvarova, lvrabec, mgrepl, mmalik, nlevinki, pbokoc, plautrba, pprakash, pvrabec, rcyriac, rhs-bugs, sankarshan, sgraf, ssekidde, tlavigne | |
Target Milestone: | rc | Keywords: | ZStream | |
Target Release: | --- | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | selinux-policy-3.7.19-279.el6 | Doc Type: | Bug Fix | |
Doc Text: |
Fixed an AVC denial error when setting up *Gluster* storage on NFS Ganesha clusters
Attempting to set up Gluster storage on an NFS-Ganesha cluster previously failed due to an Access Vector Cache (AVC) denial error. The responsible SELinux policy has been adjusted to allow handling of volumes mounted by NFS-Ganesha, and the described failure no longer occurs.
|
Story Points: | --- | |
Clone Of: | 1239017 | |||
: | 1248520 (view as bug list) | Environment: | ||
Last Closed: | 2016-05-10 19:59:07 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: | ||||
Bug Blocks: | 1202842, 1212796, 1239017, 1248520 |
Description
Prasanth
2015-07-09 07:04:57 UTC
The local policy for testing # cat gluster_showmount.te policy_module(gluster_showmount, 1.0) optional_policy(` mount_domtrans_showmount(glusterd_t) ') # make -f /usr/share/selinux/devel/Makefile gluster_showmount.pp # semodule -i gluster_showmount.pp 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-2016-0763.html |