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.
Created attachment 1917577[details]
Boot failure
Created attachment 1917577[details]
Boot failure
Description of problem:
* RHEL9 Image Builder produces images that fails to boot when the target is VMware. Specifically the kernel boots, but you get [FAILED] Failed to mount /sysroot after a number of sense key errors. Screenshot 'bootfail.png' attached for reference.
Version-Release number of selected component (if applicable):
How reproducible:
* Always reproducible.
Steps to Reproduce:
1. Build a vanilla RHEL9 VM on VMware ESX 7.0.3 19482537 using the RHEL9 Minimal Boot CD
a. Choose server with GUI
b. Register and license with Red Hat and ensure up to date
2. Follow the instructions https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/pdf/composing_a_customized_rhel_system_image/red_hat_enterprise_linux-9-composing_a_customized_rhel_system_image-en-us.pdf
a. Add your user to the weldr group
b. Yum install osbuild-composer composer-cli cockpit-composer bash-completion
c. systemctl enable --now osbuild-composer.socket
d. systemctl enable --now cockpit.socket
e. Create a simple blueprint
name = “RHEL9base2”
description = “”
modules = []
groups = []
distro = “”
[[packages]]
name = “bash”
version = “*”
f. Push and start the blueprint
i. composer-cli blueprints push RHEL9base2.toml
ii. composer-cli compose start RHEL9base2
g. Image claims to have completed successfully (although log files has a lot of detail including some)
h. Upload resulting VMDK to VMware
i. Build a new VM, but delete the disk and replace with the VMDK (being sure to select IDE 0 – see page 53 and 54 in the above doc for details)
j. VM boots' but fails as above
Actual results:
--------------
The VM fails to boot.
Expected results:
------------------
The VM should boot properly.
Additional info:
-----------------
* Fdisk shows me the following
Disk /dev/sdb: 2.69 GiB, 2884632576 bytes, 5634048 sectors
Disk model: VMware Virtual I
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier:
Device Start End Sectors Size Type
/dev/sdb1 2048 4095 2048 1M BIOS boot
/dev/sdb2 4096 413695 409600 200M EFI System
/dev/sdb3 413696 1437695 1024000 500M Linux extended boot
/dev/sdb4 1437696 5634014 4196319 2G Linux filesystem
but the /dev/sdb4 can not even be mounted
[root@rhel9 ~]# mount /dev/sdb4 /mnt/otherroot/
mount: /mnt/otherroot: can't read superblock on /dev/sdb4.
* The issue occurs with the Images created from console.redhat.com as well.
* Same issue also occurs with RHEL 8.
Comment 12RHEL Program Management
2023-10-09 11:40:09 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 13RHEL Program Management
2023-10-09 11:41:44 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.