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.

As part of the FDO onboarding flow, we ship a previously null/clevis-pin-null encrypted raw image that has to be re-encrypted when FIDO onboards the device. The feature is well contained within the service info server and provides better usability without having the user runs commands from the onboarding mechanism.

Tracked in https://issues.redhat.com/browse/THEEDGE-1663

Verified scratch build https://kojihub.stream.rdu2.redhat.com/kojifiles/work/tasks/228/1050228/ on RHEL9.0, passed.

Verified with nightly build, success.

[root@yih-rhel90 rhel-edge]# rpm -qa|grep fdo
fdo-rendezvous-server-0.4.5-1.el9_0.x86_64
fdo-owner-onboarding-server-0.4.5-1.el9_0.x86_64
fdo-owner-cli-0.4.5-1.el9_0.x86_64
fdo-manufacturing-server-0.4.5-1.el9_0.x86_64
fdo-init-0.4.5-1.el9_0.x86_64
fdo-client-0.4.5-1.el9_0.x86_64
fdo-admin-cli-0.4.5-1.el9_0.x86_64

[root@yih-rhel90 rhel-edge]# rpm -qa|grep osbuild
osbuild-composer-dnf-json-46.2-1.el9_0.x86_64
osbuild-composer-core-46.2-1.el9_0.x86_64
python3-osbuild-53-1.el9_0.noarch
osbuild-selinux-53-1.el9_0.noarch
osbuild-53-1.el9_0.noarch
osbuild-luks2-53-1.el9_0.noarch
osbuild-lvm2-53-1.el9_0.noarch
osbuild-ostree-53-1.el9_0.noarch
osbuild-composer-worker-46.2-1.el9_0.x86_64
osbuild-composer-46.2-1.el9_0.x86_64

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: fido-device-onboard), 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:2567