Bug 1460114 - the filesystem_associate plugin tracebacks
the filesystem_associate plugin tracebacks
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: setroubleshoot-plugins (Show other bugs)
All Linux
medium Severity medium
: rc
: ---
Assigned To: Petr Lautrbach
Milos Malik
Depends On:
  Show dependency treegraph
Reported: 2017-06-09 03:27 EDT by Milos Malik
Modified: 2017-12-06 06:01 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-12-06 06:01:13 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Milos Malik 2017-06-09 03:27:41 EDT
Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:
* always

Steps to Reproduce:
1. get a RHEL-6.9 machine (targeted policy is active)
2. run following automated TC:
 * /CoreOS/setroubleshoot-plugins/Sanity/filesystem_associate
3. search for traceback in /var/log/messages

Actual results:
Jun  9 03:21:28 removed setroubleshoot: [avc.ERROR] Plugin Exception filesystem_associate
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 191, in analyze_avc
report = plugin.analyze(avc)
File "/usr/share/setroubleshoot/plugins/filesystem_associate.py", line 55, in analyze
avc.tcontext.type in file_types and \
NameError: global name 'file_types' is not defined

Expected results:
* no tracebacks
Comment 2 Jan Kurik 2017-12-06 06:01:13 EST
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:


This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:


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