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.
OpenSCAP and SSG are now able to scan RHV-H systems correctly
Previously, using the OpenSCAP and SCAP Security Guide (SSG) tools to scan a Red Hat Enterprise Linux system working as a Red Hat Virtualization Host (RHV-H) returned `Not Applicable` results. With this update, OpenSCAP and SSG correctly identify RHV-H as Red Hat Enterprise Linux, which enables OpenSCAP and SSG to scan RHV-H systems properly.
Created attachment 1248453[details]
SCAP Scan of RHV-H hypervisor
Description of problem:
When performing an Openscap scan of a RHV-H hypervisor, the report comes back as notapplicable. This is due to RHV-H not being recognized as RHEL, which it is.
Version-Release number of selected component (if applicable):
7.x
How reproducible:
100%
Steps to Reproduce:
1. Install RHV-H
2. Conduct scap scan of system using the STIG for Red Hat Enterprise Linux 7 Server profile
3. View HTML report
Actual results:
No rules are matched due to scap not recognizing RHV-H as RHEL
Expected results:
RHV-H is RHEL, so profiles should apply
Additional info:
Hello Donny,
OpenSCAP and SCAP Security Guide currently checks presence of package redhat-release-{server,workstation,client,computenode} and version of the package. What is the release package on RHV-H?
You were asking for the version of the package installed.
yum list installed |grep redhat-release-*
redhat-release-virtualization-host.x86_64 4.0-6.1.el7 installed
redhat-release-virtualization-host-content.x86_64
Correct. We obsolete redhat-release-{server,workstation,client,computenode}.
Checking the content of /etc/redhat-release (or os-release) is the best method on RHV-H.
Applicability of RHEL7 SCAP content is determined based on (1) presence of a RPM package that provides "/etc/redhat-release" and (2) version of that RPM package starting with 7.
For redhat-release-server the version is 7.y-z.el7, but in your case it's 4.0-6.1.el7.
How does RHV version map to RHEL version? Can we make an assumption that if "redhat-release-virtualization-host" rpm of certain version is installed on the system then the system is RHEL7?
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
Created attachment 1248453 [details] SCAP Scan of RHV-H hypervisor Description of problem: When performing an Openscap scan of a RHV-H hypervisor, the report comes back as notapplicable. This is due to RHV-H not being recognized as RHEL, which it is. Version-Release number of selected component (if applicable): 7.x How reproducible: 100% Steps to Reproduce: 1. Install RHV-H 2. Conduct scap scan of system using the STIG for Red Hat Enterprise Linux 7 Server profile 3. View HTML report Actual results: No rules are matched due to scap not recognizing RHV-H as RHEL Expected results: RHV-H is RHEL, so profiles should apply Additional info: