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.
DescriptionAntonio Murdaca
2023-03-13 08:40:08 UTC
Description of problem:
https://issues.redhat.com/browse/THEEDGE-3181
Burning an RHEL 9.x iso generated as edge-simplified-installer does not provide a UEFI bootable disk. Only boots to shell
Version-Release number of selected component (if applicable):
8.x, 8.9
How reproducible:
always on hardware with some hiccup in UEFI firmware
Steps to Reproduce:
Minimized, easy-to-follow steps that will trigger the bug. Include any special setup steps or specific tools you used
setup nginx image repo in podman
create a blueprint for producing a minimal edge image
cat <<EOF > blueprint-fdo.toml name = "blueprint-fdo" description = "Blueprint for FDO" version = "0.0.1" packages = [] modules = [] groups = [] distro = "" [customizations] installation_device = "/dev/sda" [customizations.fdo] manufacturing_server_url = "${FDO_MANUFACTURING_URL}" diun_pub_key_insecure = "true" EOF
build image
sudo composer-cli compose start-ostree blueprint-fdo edge-simplified-installer --ref rhel/9/x86_64/edge --url http://192.168.122.86:8090/repo/
Export image using: sudo composer-cli compose image xxxxxxx
Burn image to flash using various installer softwares or the recommended dd command. Same results
Set device to boot from USB and boot with flash inserted.
Actual results:
Device boots to UEFI Shell 2.2.
Expected results:
Rhel installer should run and onboarding proceed
Additional info:
Comment 5Hendrik van Niekerk
2023-03-13 09:38:48 UTC
Tested scenario using OnLogic HX500, which was one of the 2 devices confirmed to display the behaviour in question.
Using RHEL 9.1 build image and output a simplified-edge-installer, using pr 3327 as base, the issue was confirmed to be resolved and the HX500 system booted successfully. Verified that other devices, a NUC11k also still boots from the same image.
In order to verify this bug, tests on Onlogic bare-metal hardware HX401 and K410 have been performed.
Following lines summarize test results:
- RHEL-9.3 iso generated as edge-simplified-installer provides UEFI bootable disk for K410.
- RHEL-9.3/CS9 iso generated as edge-simplified-installer provide UEFI bootable disks for HX401, but an issue has been found https://bugzilla.redhat.com/show_bug.cgi?id=2232406
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 (osbuild, osbuild-composer, and cockpit-composer bug fix and enhancement 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/RHEA-2023:6318