Bug 2185868

Summary:	[RFE] Enable FIPS when building rpm-ostree images with ImageBuilder
Product:	Red Hat Enterprise Linux 9	Reporter:	Benjamin Schmaus <bschmaus>
Component:	osbuild	Assignee:	Image Builder team <osbuilders>
Status:	CLOSED MIGRATED	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:	Eliane Ramos Pereira <elpereir>
Priority:	medium
Version:	9.2	CC:	cllang, elpereir, miabbott, obudai, sbarcomb
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	.Enabling the FIPS mode is not supported when building `rpm-ostree` images with RHEL image builder Currently, there is no support to enable the FIPS mode when building `rpm-ostree` images with RHEL image builder.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-18 13:53:17 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Benjamin Schmaus 2023-04-11 12:59:15 UTC

RFE for FIPS when building a ImageBuilder image. There is a need from the NAPS team for all customers around DOD and defense to be able to generate rpm-ostree based images that are FIPS enabled when using Red Hat Device Edge. However this would also extend to any situations where rpm-ostree images are created with ImageBuilder and possibly used in the datacenter as well. The key here is the customer needs the compliance equivalency they get today with FIPS in rpms/Anaconda based deployments when using ImageBuilder and rpm-ostree based deployments.

Proposed title of this feature request:
Enable FIPS when building rpm-ostree images with ImageBuilder

Who is the customer behind the request? Account: name and account number
Multiple customers - internal RH NAPs identified

What is the nature and description of the request?
Add feature to Red Hat Image Builder so that it can generate FIPS rpm-ostree images

Why does the customer need this?
This is a security/compliance requirement that customers currently use with RHEL using a rpms/Anaconda based deployment. However with the use of rpm-ostree based images customers would like the same compliance for FIPS.

How would the customer like to achieve this?
Customer would like to provide an ImageBuilder blueprint that identifies the image should be built as FIPS enabled. ImageBuilder should then create the image so that when it is applied to device the device comes up and FIPS is enabled automatically.

For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Customer would like to provide an ImageBuilder blueprint that identifies the image should be built as FIPS enabled. ImageBuilder should then create the image so that when it is applied to device the device comes up and FIPS is enabled automatically.

Is there already an existing RFE upstream ?
No

Does the customer have any specific timeline dependencies?
No

Which release would they like to target?
RHEL 9

Is the sales team involved in this request and do they have any additional input?
No

List any affected packages or components.
Red Hat Image Builder and associated packages

Would the customer be able to assist in testing this functionality if implemented?
Yes - we could identify early customer to test and offer feedback

Comment 5 RHEL Program Management 2023-09-18 13:48:12 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-18 13:53:17 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.