Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Probes dump debug error messages to the stderr even when default verbosity is used.
Version-Release number of selected component (if applicable):
openscap-1.2.16-1.el7.x86_64
scap-security-guide-0.1.36-7.el7.noarch (for reproducer)
How reproducible:
reliably
Steps to Reproduce:
1. oscap xccdf eval --xccdf-id scap_org.open-scap_cref_ssg-rhel7-xccdf-1.2.xml --oval-results --report xccdf_org.ssgproject.content_profile_C2S.html --progress --profile xccdf_org.ssgproject.content_profile_C2S /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml
2.
3.
Actual results:
stderr is full of:
E: probe_selinuxsecuritycontext: Can't get context for /proc/2/exe: No such file or directory
E: probe_selinuxsecuritycontext: Can't get context for /proc/3/exe: No such file or directory
E: probe_selinuxsecuritycontext: Can't get context for /proc/5/exe: No such file or directory
E: probe_selinuxsecuritycontext: Can't get context for /proc/6/exe: No such file or directory
E: probe_selinuxsecuritycontext: Can't get context for /proc/7/exe: No such file or directory
E: probe_selinuxsecuritycontext: Can't get context for /proc/8/exe: No such file or directory
E: probe_selinuxsecuritycontext: Can't get context for /proc/9/exe: No such file or directory
E: probe_selinuxsecuritycontext: Can't get context for /proc/10/exe: No such file or directory
...
Expected results:
stderr is empty
Additional info:
If no verbosity level is specified, the default verbosity level is WARNING, which means that all warnings and errors are displayed.
Also, if no log file is specified, the messages are printed to stderr.
The problem is that some messages are categorized as warnings and errors even if they are not serious. This is a historic remainder from old times when verbose output was not useful and was only available for people who compiled it with debug flag.
The default verbosity level was introduced in OpenSCAP 1.2.14 by https://github.com/OpenSCAP/openscap/pull/630, because this behavior is something we expect from any utility.
This has to be fixed by putting the messages into a right category.
After a discussion with wsato I realized we have no time for a proper fix.
For RHEL 7.5 we will apply the same fix as we did in 7.4, which means to add a downstream patch that reverts PR #630.
Then we can work upstream to do a proper fix in upstream code, which will take some time.
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/RHEA-2018:0796