Bug 2211011

Summary: Kickstart installation got stuck with message: cancel waiting for multipath siblings of sda
Product: Red Hat Enterprise Linux 9 Reporter: Richard Liu <richard.liu>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: unspecified    
Version: 9.3CC: jstodola
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-31 08:31:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
rhel9.3 kictstart install got stuck none

Description Richard Liu 2023-05-30 09:20:11 UTC
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.

Comment 1 Jan Stodola 2023-05-30 09:56:45 UTC
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

Comment 2 Richard Liu 2023-05-31 06:04:33 UTC
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

Comment 3 Jan Stodola 2023-05-31 08:31:59 UTC
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 ***