Bug 1640522

Summary: SELinux Security Context probe produces a flood of annoying messages
Product: Red Hat Enterprise Linux 7 Reporter: Jan Černý <jcerny>
Component: openscapAssignee: Jan Černý <jcerny>
Status: CLOSED ERRATA QA Contact: Matus Marhefka <mmarhefk>
Severity: low Docs Contact: Mirek Jahoda <mjahoda>
Priority: low    
Version: 7.7CC: akapse, jcerny, matyc, mhaicman, mmarhefk, openscap-maint, wsato
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openscap-1.2.17-10.el7 Doc Type: Bug Fix
Doc Text:
.OpenSCAP scanner results no longer contain a lot of SELinux context error messages Previously, the OpenSCAP scanner logged the inability to get the SELinux context on the `ERROR` level even in situations where it is not a true error. Consequently, scanner results contained a lot of SELinux context error messages and both the `oscap` command-line utility and the `SCAP Workbench` graphical utility outputs were hard to read for that reason. The `openscap` packages have been fixed, and scanner results no longer contain a lot of SELinux context error messages.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-29 19:53:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Černý 2018-10-18 09:26:54 UTC
Description of problem:
SELinux Security Context probe produces a flood of annoying messages
that look like this:

Can't get context ...

This makes the output hard to orient in.

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

How reproducible:
always

Steps to Reproduce:
1.oscap xccdf eval --oval-results --report xccdf_org.ssgproject.content_profile_ospp42-draft.html --progress --profile xccdf_org.ssgproject.content_profile_ospp42-draft /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml
2. see the stderr
3.

Actual results:
A lot of "Can't get context" messages are written on stderr.

Expected results:
These messages are displayed only in DEVEL verbosity level.

Additional info:

Comment 2 Jan Černý 2018-10-18 09:27:21 UTC
This was fixed upstream in https://github.com/OpenSCAP/openscap/pull/1222

Comment 3 Marek Haicman 2018-10-18 11:17:16 UTC
Just a note (for testing purposes) this is triggered specifically by rule xccdf_org.ssgproject.content_rule_selinux_confinement_of_daemons

Comment 8 Jan Černý 2019-05-13 09:24:57 UTC
*** Bug 1676894 has been marked as a duplicate of this bug. ***

Comment 13 errata-xmlrpc 2020-09-29 19:53: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 (openscap bug fix and enhancement update), 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-2020:3914