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.
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-2018:0763
Description of problem: If you stop a cluster configured with sbd fencing, several avc messages are generated. Example of AVC message: time->Fri Sep 30 16:24:47 2016 type=SYSCALL msg=audit(1475245487.905:347): arch=c000003e syscall=87 success=no exit=-13 a0=7fb3e0bfb00c a1=7fff3a9a0170 a2=0 a3=7fff3a9a0260 items=0 ppid=3814 pid=3817 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="sbd" exe="/usr/sbin/sbd" subj=system_u:system_r:sbd_t:s0 key=(null) type=AVC msg=audit(1475245487.905:347): avc: denied { write } for pid=3817 comm="sbd" name="/" dev="tmpfs" ino=6581 scontext=system_u:system_r:sbd_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=dir Version-Release number of selected component (if applicable): selinux-policy-3.13.1-102.el7.noarch How reproducible: always Steps to Reproduce: 1. Configure cluster with sbd fencing: [root@virt-024 ~]# pcs cluster auth virt-0{24,27} virt-024: Already authorized virt-027: Already authorized [root@virt-024 ~]# pcs cluster setup --name cluster virt-0{24,27} Destroying cluster on nodes: virt-024, virt-027... virt-024: Stopping Cluster (pacemaker)... virt-027: Stopping Cluster (pacemaker)... virt-027: Successfully destroyed cluster virt-024: Successfully destroyed cluster Sending cluster config files to the nodes... virt-024: Succeeded virt-027: Succeeded Synchronizing pcsd certificates on nodes virt-024, virt-027... virt-024: Success virt-027: Success Restarting pcsd on the nodes in order to reload the certificates... virt-024: Success virt-027: Success [root@virt-024 ~]# pcs stonith sbd enable Running SBD pre-enabling checks... virt-027: SBD pre-enabling checks done virt-024: SBD pre-enabling checks done Warning: auto_tie_breaker quorum option will be enabled to make SBD fencing effective. Cluster has to be offline to be able to make this change. Checking corosync is not running on nodes... virt-024: corosync is not running virt-027: corosync is not running Sending updated corosync.conf to nodes... virt-024: Succeeded virt-027: Succeeded Distributing SBD config... virt-024: SBD config saved virt-027: SBD config saved Enabling SBD service... virt-024: sbd enabled virt-027: sbd enabled Warning: Cluster restart is required in order to apply these changes. 2. Start the cluster: [root@virt-024 ~]# pcs cluster start --all virt-027: Starting Cluster... virt-024: Starting Cluster... [root@virt-024 ~]# ausearch -m AVC <no matches> 3. Stop the cluster and check the AVC messages: [root@virt-024 ~]# pcs cluster stop --all virt-024: Stopping Cluster (pacemaker)... virt-027: Stopping Cluster (pacemaker)... virt-027: Stopping Cluster (corosync)... virt-024: Stopping Cluster (corosync)... [root@virt-024 ~]# ausearch -m AVC ---- time->Fri Sep 30 16:24:47 2016 type=SYSCALL msg=audit(1475245487.905:347): arch=c000003e syscall=87 success=no exit=-13 a0=7fb3e0bfb00c a1=7fff3a9a0170 a2=0 a3=7fff3a9a0260 items=0 ppid=3814 pid=3817 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="sbd" exe="/usr/sbin/sbd" subj=system_u:system_r:sbd_t:s0 key=(null) type=AVC msg=audit(1475245487.905:347): avc: denied { write } for pid=3817 comm="sbd" name="/" dev="tmpfs" ino=6581 scontext=system_u:system_r:sbd_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=dir ---- time->Fri Sep 30 16:24:47 2016 type=SYSCALL msg=audit(1475245487.905:348): arch=c000003e syscall=87 success=no exit=-13 a0=7fb3e0bfa00c a1=7fff3a9a0180 a2=35ff82d2 a3=7fb3df565c8c items=0 ppid=3814 pid=3817 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="sbd" exe="/usr/sbin/sbd" subj=system_u:system_r:sbd_t:s0 key=(null) type=AVC msg=audit(1475245487.905:348): avc: denied { write } for pid=3817 comm="sbd" name="/" dev="tmpfs" ino=6581 scontext=system_u:system_r:sbd_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=dir ---- time->Fri Sep 30 16:24:47 2016 type=SYSCALL msg=audit(1475245487.905:349): arch=c000003e syscall=87 success=no exit=-13 a0=7fb3e0bf800c a1=7fff3a9a0170 a2=0 a3=7fff3a9a0260 items=0 ppid=3814 pid=3817 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="sbd" exe="/usr/sbin/sbd" subj=system_u:system_r:sbd_t:s0 key=(null) type=AVC msg=audit(1475245487.905:349): avc: denied { write } for pid=3817 comm="sbd" name="/" dev="tmpfs" ino=6581 scontext=system_u:system_r:sbd_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=dir ---- time->Fri Sep 30 16:24:47 2016 type=SYSCALL msg=audit(1475245487.905:350): arch=c000003e syscall=87 success=no exit=-13 a0=7fb3e0bf700c a1=7fff3a9a0180 a2=35ff82d2 a3=7fb3df565c8c items=0 ppid=3814 pid=3817 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="sbd" exe="/usr/sbin/sbd" subj=system_u:system_r:sbd_t:s0 key=(null) type=AVC msg=audit(1475245487.905:350): avc: denied { write } for pid=3817 comm="sbd" name="/" dev="tmpfs" ino=6581 scontext=system_u:system_r:sbd_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=dir ---- time->Fri Sep 30 16:24:47 2016 type=SYSCALL msg=audit(1475245487.905:351): arch=c000003e syscall=87 success=no exit=-13 a0=7fb3e0bf500c a1=7fff3a9a0180 a2=0 a3=7fb3df565c8c items=0 ppid=3814 pid=3817 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="sbd" exe="/usr/sbin/sbd" subj=system_u:system_r:sbd_t:s0 key=(null) type=AVC msg=audit(1475245487.905:351): avc: denied { write } for pid=3817 comm="sbd" name="/" dev="tmpfs" ino=6581 scontext=system_u:system_r:sbd_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=dir ---- time->Fri Sep 30 16:24:47 2016 type=SYSCALL msg=audit(1475245487.905:352): arch=c000003e syscall=87 success=no exit=-13 a0=7fb3e0bf400c a1=7fff3a9a0190 a2=35ff82d2 a3=7fb3df565c8c items=0 ppid=3814 pid=3817 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="sbd" exe="/usr/sbin/sbd" subj=system_u:system_r:sbd_t:s0 key=(null) type=AVC msg=audit(1475245487.905:352): avc: denied { write } for pid=3817 comm="sbd" name="/" dev="tmpfs" ino=6581 scontext=system_u:system_r:sbd_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=dir Actual results: Several AVC messages are generated after stopping cluster configured with sbd fencing. Expected results: No AVC messages are generated after stopping cluster configured with sbd fencing. Additional info: