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:
OpenSCAP scanner comes in (together with other tools) from openscap-utils package. There are use cases when emphasis is put on minimized installed footprint. These use-cases would benefit if the oscap command-line tool is shipped in a separate sub-package.

The openscap-utils should still require openscap-scanner. Meaning the limited install base is optional for the said use-cases.

How will users know that only a sub-package will be enough in order to run the oscap tool?

The scanner has been always part of openscap-utils package. After this change if a user tries to install openscap-utils package, openscap-scanner will get installed as a dependency and bring in the scanner binary.

The user doesn't need to know about the possibility to remove openscap-utils and just keep openscap-scanner. We will continuously add this information to the documentation. Going forward, we will only teach users to install openscap-scanner, but the openscap-utils remains as it brings other tools with other dependencies.

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-2015-0392.html