Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1513075 - selinux inhibits pacemaker's logging policy [rhel-7.4.z]
Summary: selinux inhibits pacemaker's logging policy [rhel-7.4.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.4
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
Mirek Jahoda
URL:
Whiteboard:
Depends On: 1508360
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-14 17:29 UTC by Oneata Mircea Teodor
Modified: 2017-11-30 15:40 UTC (History)
13 users (show)

Fixed In Version: selinux-policy-3.13.1-166.el7_4.7
Doc Type: Bug Fix
Doc Text:
Prior to this update, the /var/log/pacemaker directories for the Pacemaker cluster resource manager were labeled as cluster_var_log_t. Consequently, an SELinux denial occurred when containerized Pacemaker tried to access the /var/log directory. An exception labeling the /var/log/pacemaker/bundles/ directory with the var_log_t label has been added, and Pacemaker is now able to map logging correctly with SELinux in Enforcing mode.
Clone Of: 1508360
Environment:
Last Closed: 2017-11-30 15:40:30 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:3305 normal SHIPPED_LIVE selinux-policy bug fix update 2017-11-30 20:15:43 UTC

Description Oneata Mircea Teodor 2017-11-14 17:29:23 UTC
This bug has been copied from bug #1508360 and has been proposed to be backported to 7.4 z-stream (EUS).

Comment 8 errata-xmlrpc 2017-11-30 15:40:30 UTC
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:3305


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