Bug 1330921 - setenforce plugin uses /selinux instead of /sys/fs/selinux
Summary: setenforce plugin uses /selinux instead of /sys/fs/selinux
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: setroubleshoot-plugins
Version: 7.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Petr Lautrbach
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-27 10:30 UTC by Milos Malik
Modified: 2016-11-04 06:32 UTC (History)
4 users (show)

Fixed In Version: setroubleshoot-plugins-3.0.62-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 06:32:23 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2441 0 normal SHIPPED_LIVE setroubleshoot-plugins bug fix update 2016-11-03 14:02:25 UTC

Description Milos Malik 2016-04-27 10:30:15 UTC 
Description of problem:
 * SELinux FS is mounted into /sys/fs/selinux directory on RHEL-7
 * the plugin should reflect that

Version-Release number of selected component (if applicable):
setroubleshoot-3.2.25-2.el7.x86_64
setroubleshoot-server-3.2.25-2.el7.x86_64
setroubleshoot-plugins-3.0.59-1.el7.noarch

How reproducible:
always

Steps to Reproduce:
# grep -R /selinux /usr/share/setroubleshoot/plugins/setenforce.py
    SELinux has prevented $SOURCE from writing to a file under /selinux.
    Files under /selinux control the way SELinux is configured.
    All programs that need to write to files under /selinux should have already had policy
#

Expected results:
 * the description contains /sys/fs/selinux instead of /selinux
Comment 5 errata-xmlrpc 2016-11-04 06:32:23 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://rhn.redhat.com/errata/RHBA-2016-2441.html
Note You need to log in before you can comment on or make changes to this bug.