Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1380795 - (selinux-policy) AVC messages are generated for sbd component after stopping cluster
(selinux-policy) AVC messages are generated for sbd component after stopping ...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy (Show other bugs)
7.3
All Linux
medium Severity medium
: rc
: ---
Assigned To: Lukas Vrabec
Milos Malik
:
: 1388444 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-09-30 10:45 EDT by Miroslav Lisik
Modified: 2018-04-10 08:25 EDT (History)
8 users (show)

See Also:
Fixed In Version: selinux-policy-3.13.1-175.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 08:24:04 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0763 None None None 2018-04-10 08:25 EDT

  None (edit)
Description Miroslav Lisik 2016-09-30 10:45:31 EDT
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:
Comment 2 Lukas Vrabec 2016-11-14 09:07:42 EST
*** Bug 1388444 has been marked as a duplicate of this bug. ***
Comment 10 errata-xmlrpc 2018-04-10 08:24:04 EDT
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

Note You need to log in before you can comment on or make changes to this bug.