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.

Bug 1447341

Summary: openscap starts producing warning and error messages which are not useful to user
Product: Red Hat Enterprise Linux 7 Reporter: Marek Haicman <mhaicman>
Component: openscapAssignee: Martin Preisler <mpreisle>
Status: CLOSED ERRATA QA Contact: Marek Haicman <mhaicman>
Severity: high Docs Contact: Mirek Jahoda <mjahoda>
Priority: medium    
Version: 7.4CC: hkhot, matmille, mhaicman, mpreisle, openscap-maint
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
*OpenSCAP* now produces only useful messages and warnings Previously, default scan output settings have been changed, and debug messages were also printed to standard output. As a consequence, the *OpenSCAP* output was full of errors and warnings. The output was hard to read and the *SCAP Workbench* was unable to handle those messages, too. With this update, the change of default output setting has been reverted, and *OpenSCAP* now produces useful output.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 08:45:48 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:
Attachments:
Description Flags
example full of such errors none

Description Marek Haicman 2017-05-02 12:58:09 UTC 
Created attachment 1275678 [details]
example full of such errors

Description of problem:
When performing scanning with --progress flag, errors and warnings are printed in such way it breaks the output.

Version-Release number of selected component (if applicable):
openscap-1.2.14-1.el7.x86_64

How reproducible:
reliably

Steps to Reproduce:
1. scan machine with some more complex profile
2.
3.

Actual results:

xccdf_org.ssgproject.content_rule_aide_build_database:W: oscap:     Referenced variable has no values (oval:ssg-variable_aide_build_new_database_absolute_path:var:1).
W: oscap:     Referenced variable has no values (oval:ssg-variable_aide_operational_database_absolute_path:var:1)
fail

xccdf_org.ssgproject.content_rule_mount_option_noexec_removable_partitions:W: oscap: Skipping external variable oval:ssg-var_removable_partition:var:1.
pass

xccdf_org.ssgproject.content_rule_selinux_confinement_of_daemons: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/9142/exe: No such file or directory
pass



Expected results:
If warnings and errors needs to be printed, put it after the first line containing a result

Additional info:
Comment 3 Martin Preisler 2017-05-19 09:47:19 UTC 
If you redirect stderr it will clean up the output, correct?

oscap xccdf eval --progress ...... 2>/dev/null

Regardless, I think we should revert this in RHEL 7.4 and give ourselves more time to recategorize some of the messages.
Comment 4 Marek Haicman 2017-05-19 11:25:39 UTC 
*** Bug 1447446 has been marked as a duplicate of this bug. ***
Comment 6 Marek Haicman 2017-06-12 17:29:07 UTC 
Verified fix (revert) in version openscap-1.2.14-2.el7.x86_64


OLD (openscap-1.2.14-1.el7.x86_64):
:: [   PASS   ] ::       Command 'oscap xccdf eval --benchmark-id xccdf_org.ssgproject.content_benchmark_RHEL-7 --oval-results --report xccdf_org.ssgproject.content_profile_cjis-rhel7-server.html --progress --profile xccdf_org.ssgproject.content_profile_cjis-rhel7-server /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml' (Expected 0,2, got 2)
:: [   PASS   ] ::       File '/var/tmp/rlRun_LOG.fqP5DwP0' should contain '^xccdf_org.ssgproject.content' 
:: [   PASS   ] ::       File '/var/tmp/rlRun_LOG.fqP5DwP0' should not contain ':error$' 
:: [   PASS   ] ::       File '/var/tmp/rlRun_LOG.fqP5DwP0' should not contain ':unknown$' 
W: probe_rpminfo: Failed to extract the Key ID value: regex="Key ID [a-fA-F0-9]{16}", string="(none)"
W: oscap:     Referenced variable has no values (oval:ssg-variable_aide_build_new_database_absolute_path:var:1).
W: oscap:     Referenced variable has no values (oval:ssg-variable_aide_operational_database_absolute_path:var:1)
W: oscap: rbt_str_add: non-zero return code
W: oscap: rbt_str_add: non-zero return code
W: oscap: rbt_str_add: non-zero return code
W: oscap: rbt_str_add: non-zero return code
W: oscap: rbt_str_add: non-zero return code
W: oscap: rbt_str_add: non-zero return code
W: oscap: rbt_str_add: non-zero return code
W: oscap: rbt_str_add: non-zero return code
W: oscap: rbt_str_add: non-zero return code
W: oscap: rbt_str_add: non-zero return code
W: oscap: rbt_str_add: non-zero return code
W: oscap: rbt_str_add: non-zero return code
W: oscap: rbt_str_add: non-zero return code
W: oscap: rbt_str_add: non-zero return code
W: oscap: rbt_str_add: non-zero return code
:: [   FAIL   ] ::       File 'unexpected' should not contain '.' 
:: [ 13:19:57 ] ::       [ INFO    ] :: Sending /tmp/tmp.eXOa1ALIDB/xccdf_org.ssgproject.content_profile_cjis-rhel7-server.html as tmp-tmp.eXOa1ALIDB-xccdf_org.ssgproject.content_profile_cjis-rhel7-server.html
:: [ 13:19:57 ] ::       File '/tmp/tmp.wV36EO8MG5/tmp-tmp.eXOa1ALIDB-xccdf_org.ssgproject.content_profile_cjis-rhel7-server.html' stored here: /var/tmp/BEAKERLIB_6524003_STORED_tmp-tmp.eXOa1ALIDB-xccdf_org.ssgproject.content_profile_cjis-rhel7-server.html
:: [   FAIL   ] ::     using profile 'xccdf_org.ssgproject.content_profile_cjis-rhel7-server'

NEW:
:: [   PASS   ] ::       Command 'oscap xccdf eval --benchmark-id xccdf_org.ssgproject.content_benchmark_RHEL-7 --oval-results --report xccdf_org.ssgproject.content_profile_cjis-rhel7-server.html --progress --profile xccdf_org.ssgproject.content_profile_cjis-rhel7-server /usr/share/xml/scap/ssg/content/ssg-rhel7-ds.xml' (Expected 0,2, got 2)
:: [   PASS   ] ::       File '/var/tmp/rlRun_LOG.LwSV56MW' should contain '^xccdf_org.ssgproject.content' 
:: [   PASS   ] ::       File '/var/tmp/rlRun_LOG.LwSV56MW' should not contain ':error$' 
:: [   PASS   ] ::       File '/var/tmp/rlRun_LOG.LwSV56MW' should not contain ':unknown$' 
:: [   PASS   ] ::       File 'unexpected' should not contain '.' 
:: [   PASS   ] ::     using profile 'xccdf_org.ssgproject.content_profile_cjis-rhel7-server'
Comment 11 errata-xmlrpc 2017-08-01 08:45:48 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:2291