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 1967849[details]
rhel9.3 kictstart install got stuck
Description of problem:
Kickstart installation got stuck with message:
cancel waiting for multipath siblings of sda
cancel waiting for multipath siblings of sdb
Version-Release number of selected component (if applicable):
RHEL-9.3.0-20230529.38-x86_64-dvd1.iso
How reproducible:
Steps to Reproduce:
1.Copy content from RHEL-9.3.0-20230529.38-x86_64-dvd1.iso
2.Add kickstart file, change config info in isolinux.cfg, grub.conf, grub.cfg, etc.
3.Generate the customized ISO, mount the new ISO to Dell PowerEdge R640/R630, reboot the server to start installation.
Actual results:
Installation process got stuck, please see the attachment.
Expected results:
Installation should be successful.
Additional info:
We created an automation tool for rhel installation, which works for rhel from 8.x to 9.2, however, it doesn't work for rhel9.3, it's like a bug introduced in 9.3?
BTW, the server has no multipath installed, and rhel 8.x to 9.2 can be successfully installed with the same automation tool.
Richard, can you please provide the kernel command line of your customized ISO?
Could you try adding "inst.wait_for_disks=0" to the kernel command line to se if it helps?
It's possible you are hitting bug 2209599.
Thanks,
Jan
Hello Jan,
After adding "inst.wait_for_disks=0" to the isolinux.cfg, kickstart works as expected.
append initrd=initrd.img inst.ks=cdrom:/ks.cfg inst.stage2=hd:LABEL=RHEL-9-3-0-BaseOS-x86_64 inst.wait_for_disks=0 quiet
Regards,
Richard
Thanks for confirming that "inst.wait_for_disks=0" works as a temporary workaround. Based on that I'm closing this bug as a duplicate of bug 2209599.
*** This bug has been marked as a duplicate of bug 2209599 ***
Created attachment 1967849 [details] rhel9.3 kictstart install got stuck Description of problem: Kickstart installation got stuck with message: cancel waiting for multipath siblings of sda cancel waiting for multipath siblings of sdb Version-Release number of selected component (if applicable): RHEL-9.3.0-20230529.38-x86_64-dvd1.iso How reproducible: Steps to Reproduce: 1.Copy content from RHEL-9.3.0-20230529.38-x86_64-dvd1.iso 2.Add kickstart file, change config info in isolinux.cfg, grub.conf, grub.cfg, etc. 3.Generate the customized ISO, mount the new ISO to Dell PowerEdge R640/R630, reboot the server to start installation. Actual results: Installation process got stuck, please see the attachment. Expected results: Installation should be successful. Additional info: We created an automation tool for rhel installation, which works for rhel from 8.x to 9.2, however, it doesn't work for rhel9.3, it's like a bug introduced in 9.3? BTW, the server has no multipath installed, and rhel 8.x to 9.2 can be successfully installed with the same automation tool.