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.

Description of problem:

Creating a simplified installer with "diun_pub_key_root_certs" creates a grub cmdline containing

fdo.diun_pub_key_root_certs=/fdo_diun_root_certs.pem

The problem is the osbuild stage that writes down the root cert writes with a different name: /fdo_diun_pub_key_root_certs.pem

The installation just fails and hangs because it cannot provision the device

The fix is pretty easy and it's already available to be merged upstream here https://github.com/osbuild/osbuild-composer/pull/2434

The workaround is to manually edit the grub cmdline to fix the cert name


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


How reproducible:

always


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Verified the workaround, it works.

Use this blueprint with diun cert to compose a simplified-installer image:

[root@yih-rhel86 images]# composer-cli blueprints show fdocert 
name = "fdocert"
description = "A rhel-edge simplified-installer image"
version = "0.0.1"
packages = []
modules = []
groups = []
distro = ""

[customizations]
installation_device = "/dev/vda"
[customizations.fdo]
manufacturing_server_url = "http://www.testfdo.com:8080"
diun_pub_key_root_certs = "-----BEGIN CERTIFICATE-----
*********Content of DIUN CERT********************
-----END CERTIFICATE-----"

And after the provision started, connect to console and press E and change the grub command line to diun_pub_key_root_certs, the provision is successful.

Verified in scratch build https://github.com/osbuild/osbuild-composer/pull/2434, can compose diun_pub_key_root_certs image and provision it successfully.

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 (new packages: osbuild-composer), 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-2022:2522