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.
When SELinux was enabled, users were unable to mount GFS2 file systems listed in /etc/fstab. With this update, SELinux rules have been added to allow the mount process to communicate with gfs_controld, so that such file systems can now be mount as expected.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
When SELinux was enabled, users were unable to mount GFS2 file systems listed in /etc/fstab. With this update, SELinux rules have been added to allow the mount process to communicate with gfs_controld, so that such file systems can now be mount as expected.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0526.html
Description of problem: [root@taft-01 ~]# service gfs2 start Mounting GFS2 filesystem (/mnt/gfsA): gfs_controld join connect error: Permission denied error mounting lockproto lock_dlm [FAILED] Mounting GFS2 filesystem (/mnt/gfsB): gfs_controld join connect error: Permission denied error mounting lockproto lock_dlm [FAILED] type=AVC msg=audit(1285191620.106:26): avc: denied { connectto } for pid=2343 comm="mount.gfs2" path=00676673635F736F636B scontext=unconfined_u:system_r:mount_t:s0 tcontext=unconfined_u:system_r:gfs_controld_t:s0 tclass=unix_stream_socket type=SYSCALL msg=audit(1285191620.106:26): arch=c000003e syscall=42 success=yes exit=0 a0=3 a1=7fff93d24960 a2=c a3=7fff93d24963 items=0 ppid=2342 pid=2343 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=1 comm="mount.gfs2" exe="/sbin/mount.gfs2" subj=unconfined_u:system_r:mount_t:s0 key=(null) Version-Release number of selected component (if applicable): 2.6.32-71.el6.x86_64 How reproducible: Everytime