This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2185868 - [RFE] Enable FIPS when building rpm-ostree images with ImageBuilder
Summary: [RFE] Enable FIPS when building rpm-ostree images with ImageBuilder
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: osbuild
Version: 9.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Image Builder team
QA Contact: Release Test Team
Eliane Ramos Pereira
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-11 12:59 UTC by Benjamin Schmaus
Modified: 2023-09-18 13:53 UTC (History)
5 users (show)

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.
Clone Of:
Environment:
Last Closed: 2023-09-18 13:53:17 UTC
Type: Story
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2183207 0 high CLOSED Images built with stig profile remediation fail to boot with FIPS error 2023-09-18 13:55:46 UTC
Red Hat Issue Tracker   RHEL-4655 0 None Migrated None 2023-09-18 13:52:11 UTC
Red Hat Issue Tracker RHELBU-2253 0 None None None 2023-04-19 13:46:13 UTC
Red Hat Issue Tracker RHELPLAN-154385 0 None None None 2023-04-11 12:59:59 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.