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:
When scanning using new scap-security-guide, which uses .bz2 CVE OVAL feed, it prints success report as ERROR, probably because it does not expect the bz2 archive there.
Version-Release number of selected component (if applicable):
[dahaic@localhost ~]$ rpm -qa scap-workbench
scap-workbench-1.1.4-4.el7.x86_64
How reproducible:
reliably
Steps to Reproduce:
1. try to scan with "fetch remote resources" option set, using ssg version scap-security-guide-0.1.33-4.el7.noarch
Actual results:
13:39:49 error The 'oscap' process has written the following content to stderr: Downloading: https://www.redhat.com/security/data/oval/com.redhat.rhsa-RHEL7.xml.bz2 ... ok
Expected results:
No errors
Additional info:
Hi team,
Oscap tools used to send the "Downloading: ... ok" message through stdout but changed to stderr recently. Workbench still expects this message in stdout and reports an error when it comes through stderr.
The pull request https://github.com/OpenSCAP/scap-workbench/pull/116 fizes this issue.
Verified fix being included in version scap-workbench-1.1.4-5.el7.x86_64
OLD (scap-workbench-1.1.4-4.el7.x86_64):
23:43:25 info Processing...
23:43:41 error The 'oscap' process has written the following content to stderr: Downloading: https://www.redhat.com/security/data/oval/com.redhat.rhsa-RHEL7.xml.bz2 ... ok
23:43:41 info The oscap tool has finished. Reading results...
23:43:41 info Processing has been finished!
NEW:
23:39:47 info Processing...
23:40:00 info Downloading: https://www.redhat.com/security/data/oval/com.redhat.rhsa-RHEL7.xml.bz2 ... ok
23:40:00 info The oscap tool has finished. Reading results...
23:40:00 info Processing has been finished!
Both tested together with:
openscap-1.2.14-2.el7.x86_64
scap-security-guide-0.1.33-4.el7.noarch
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:2296