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:

This is a continuation of BZ #1840578 and BZ #1694962.

As of today, GPFS file systems are not considered as remote file systems, which cause some oscap rules to recurse in such file systems, causing various issues:
- slowness of the scan
- high memory usage

There should be a convenient way to exclude such file systems automatically or administratively through some configuration file.
Customers cannot rely on the workaround described in KCS https://access.redhat.com/solutions/4193501.

For example, if the proposed solution in BZ #1840578 is implemented, this could be easily implemented through specifying "InaccessibleDirectories" systemd property.


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

openscap-scanner-1.2.17-9.el7.x86_64 and later

We have discussed this internally.

We would like to change the OpenSCAP so that it recognizes GPFS as a remote system. GPFS volumes would be skipped in all rules where the OVAL object definition uses `recurse_file_system` attribute set to `local`. In similar way, we already skip NFS, SMB and other network file systems in these rules.  This solution means that to exclude the remote file systems and GPFS it requires changes on content side: all the rules must use this `recurse_file_system` attribute.

However, we don't want to provide a command line option that excludes specific paths because that would mean the option would override the instructions in SCAP content. We think that it would mean the scanner would behave differently from the specification.

https://github.com/OpenSCAP/openscap/commit/1541487788a7ffeae0f9ba3ecd4bf7c2a181ef5d

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 (openscap bug fix and enhancement update), 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-2021:1784