Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Previously, the SELinux policy prevented the GlusterFS volumes configurated for the Remote Direct Memory Access (RDMA) transport from starting. With this update, a patch has been applied that fixes this bug, and the SELinux denial no longer occurs in the described situation.
Hi Miroslav,
With the local policy provided in Comment #1, I could create, start and fuse mount RDMA transport type GlusterFS volumes and AVCs from bug description are no longer seen.
(In reply to Anoop C S from comment #5)
> Hi Miroslav,
>
> With the local policy provided in Comment #1, I could create, start and fuse
> mount RDMA transport type GlusterFS volumes and AVCs from bug description
> are no longer seen.
Great. Thank you for testing.
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/RHBA-2017:1861
Here is a workaround until an official fix becomes available: # cat glusterfs-rdma.te policy_module(glusterfs-rdma, 1.0) require { type glusterd_t; type infiniband_device_t; class capability { ipc_lock }; class chr_file { getattr open read write }; } allow glusterd_t glusterd_t : capability { ipc_lock }; allow glusterd_t infiniband_device_t : chr_file { getattr open read write }; # make -f /usr/share/selinux/devel/Makefile Compiling targeted glusterfs-rdma module /usr/bin/checkmodule: loading policy configuration from tmp/glusterfs-rdma.tmp /usr/bin/checkmodule: policy configuration loaded /usr/bin/checkmodule: writing binary representation (version 17) to tmp/glusterfs-rdma.mod Creating targeted glusterfs-rdma.pp policy package rm tmp/glusterfs-rdma.mod.fc tmp/glusterfs-rdma.mod # semodule -i glusterfs-rdma.pp # The Makefile comes from selinux-policy-devel package.