Bug 2130181

Summary:	FIPS enabled profiles built in offline mode with image-builder won't boot
Product:	Red Hat Enterprise Linux 8	Reporter:	Evgeny Kolesnikov <ekolesni>
Component:	scap-security-guide	Assignee:	Vojtech Polasek <vpolasek>
Status:	CLOSED ERRATA	QA Contact:	Milan Lysonek <mlysonek>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.7	CC:	ggasparb, jcerny, jjaburek, matyc, mhaicman, mlysonek, wsato
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
URL:	https://github.com/ComplianceAsCode/content/issues/9559
Whiteboard:
Fixed In Version:	scap-security-guide-0.1.69-1.el8	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-14 15:36:38 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:

Description Evgeny Kolesnikov 2022-09-27 12:30:40 UTC

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

Comment 3 Evgeny Kolesnikov 2023-04-25 10:26:00 UTC

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

Comment 14 errata-xmlrpc 2023-11-14 15:36:38 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 (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