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:
oscap-docker has been ported to python2 and several reusable functions are now exposed as a python package [1]. These are used by OpenSCAP-daemon which is used by atomic scan. For atomic scan to work with packaged components we need to either rebase OpenSCAP to version 1.2.6 or add a downstream patch with the new oscap-docker to the 1.2.5 version.

Atomic scan bug that requires this: https://bugzilla.redhat.com/show_bug.cgi?id=1272037
See also https://bugzilla.redhat.com/show_bug.cgi?id=1202868

[1] https://github.com/OpenSCAP/openscap/commit/0c145eede09b7dfc33cd3ab42351934aa23b0b6a

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

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

I have found issue in oscap-docker utility. Due to [possible] bug in RHEL-shipped python2, the argparse library behaves differently (parser defaults takes precedence to subparser defaults), preventing any use of the utility.

As a workaround, it is necessary to remove line 68:
parser.set_defaults(func=parser.print_help)

I have filed python bug bz1340036, for workaround-related discussion use bz1333812 for now, thanks :)

Upstream commit https://github.com/OpenSCAP/openscap/commit/fa334865b1eb24c6eabfe4c80a339c84ffc2d250 fixes the issue.

Returning, due to bug #1344762

This rebase passed regression suite, also bugs reported ( bz1340036 and bz1344762 ) are verified to be fixed in version openscap-1.2.10-2.el7

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://rhn.redhat.com/errata/RHEA-2016-2316.html