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:
Images built with image-builder on-prem using the ospp, cui & stig profiles won't boot. The issue is that these profiles enable fips mode and the images won't boot with /boot on a separate partition.

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

How reproducible:


Steps to Reproduce:
1. using osbuild-composer to build an image on-prem, create a blueprint with the following customizations:

[customizations.openscap]
profile_id = "ospp"  # or cui
datastream = "/usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml"

2. Attempt to boot the image

Actual results:
Image won't boot

Expected results:
Image boots

Additional info:
A workaround for this is to add /boot/<PARTITION> to the kernel arguments.

Upstream issue: https://github.com/ComplianceAsCode/content/issues/9559

We modified the CaC content in a way that it won't try to enable
the FIPS mode in the ImageBuilder pipeline as the result won't
FIPS-compliant due to lack of support for FIPS in IB workers.

https://github.com/ComplianceAsCode/content/pull/10245

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 (scap-security-guide bug fix 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/RHBA-2023:7056