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.

Bug 1740621

Summary: OSPP Kickstart disk configuration is different from OSPP security profile
Product: Red Hat Enterprise Linux 8 Reporter: Gabriel Gaspar Becker <ggasparb>
Component: scap-security-guideAssignee: Watson Yuuma Sato <wsato>
Status: CLOSED ERRATA QA Contact: Milan Lysonek <mlysonek>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.1CC: ggasparb, matyc, mhaicman, mlysonek
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: scap-security-guide-0.1.46-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 21:17:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Scan result after OSPP profile kickstart installation. none

Description Gabriel Gaspar Becker 2019-08-13 11:45:55 UTC
Description of problem:
The kickstart provided in the package to be used with OSPP security profile selection does not configure correctly the disk partition, causing any installation using the kickstart to not apply the profile and thus not remediating the machine according to the profile

Version-Release number of selected component (if applicable):
scap-security-guide-0.1.45-2.el8

How reproducible:
100%

Steps to Reproduce:
1. Install RHEL8.1 using kickstart: /usr/share/scap-security-guide/kickstart/ssg-rhel8-ospp-ks.cfg
2.
3.

Actual results:
Disk partition is not compatible with the OSPP security profile

Expected results:
Disk partition is compatible with the OSPP security profile and the machine is verified and remediated accordingly.

Additional info:

Comment 2 Gabriel Gaspar Becker 2019-08-19 14:47:17 UTC
Fixed upstream: https://github.com/ComplianceAsCode/content/pull/4716

Comment 3 Watson Yuuma Sato 2019-09-05 14:16:07 UTC
This is fixed by rebase to 0.1.46

Comment 5 Milan Lysonek 2019-09-10 11:42:03 UTC
Created attachment 1613554 [details]
Scan result after OSPP profile kickstart installation.

Comment 6 Milan Lysonek 2019-09-10 11:49:45 UTC
Verified for scap-security-guide-0.1.46-1.el8.
Machine installed using OSPP kickstart and OAA, after installation verified using additional openscap scan, that disk configuration is aligned with OSPP profile. See attached html report (comment 5).

Comment 8 errata-xmlrpc 2019-11-05 21:17:09 UTC
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-2019:3453