Bug 1321786
| Summary: | [SELinux] volume not getting exported after setting the option ganesha.enable -RHEL7 | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Shashank Raj <sraj> |
| Component: | nfs-ganesha | Assignee: | Bug Updates Notification Mailing List <rhs-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | Shashank Raj <sraj> |
| Severity: | urgent | Docs Contact: | Marie Hornickova <mdolezel> |
| Priority: | unspecified | ||
| Version: | rhgs-3.1 | CC: | akhakhar, asrivast, bugs, jthottan, kkeithle, mdolezel, ndevos, nlevinki, pprakash, rhinduja, sashinde, skoduri, sraj |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.1.3 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
When the nfs-ganesha server was set up on four nodes with 2X2 volume, the volume was not exported after the nfs-ganesha service was enabled. With this update, a workaround has been provided which ensures that the volume is exported as expected in the described scenario.
|
Story Points: | --- |
| Clone Of: | 1311911 | Environment: | |
| Last Closed: | 2016-06-23 05:34:55 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: | 1312809 | ||
| Bug Blocks: | 1311817 | ||
|
Description
Shashank Raj
2016-03-29 07:23:10 UTC
Verified this bug with the selinux-policy-3.13.1-60.el7_2.4.noarch and nfs-ganesha-2.3.1-6.el7rhgs.x86_64, and its working as expected. After upgrading to the above selinux policy, volumes can be exported through ganesha and no denial AVC's are seen in audit.log Based on the above observation, marking this bug as Verified. 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://access.redhat.com/errata/RHEA-2016:1247 |