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 1920819 [details]
Screenshot of the final error

Description of problem:

Unable to provision some ProLiant SL230s Gen8 systems. It works on some, not on others.

How reproducible:

Every time

Steps to Reproduce:
Provision from Satellite with RHEL 9

Actual results:

Dropped to emergency shell

Expected results:

Installation works

Additional info:

See ticket 03333044 for log files etc.

I think this is actually bug in the anaconda dracut module as there is already an anaconda bug 2141303, I'm closing this one as duplicate.

Please note that in the screenshot, there's only this warning, there's no error mentioned (which is probably futher back in the log), which caused the error. There are probably many more warnings - it would be good to see the rdsosreport.txt or debug log (there's one in the other bug) to compare the errors.

Both are most likely just timeouts, where the root disk was not properly mounted (for various reasons). It's necessary in that case to see the rdsosreport.txt where the disk layout is, as well as kernel arguments. If it's a architecture specific error, it may be very hard to reproduce though.

*** This bug has been marked as a duplicate of bug 2141303 ***

On a second look, it seems it has timed out on kickstart. So either it took much long than expected (you can raise the timeout), or the kickstart has stuck/failed on some point. It would be best to follow up on that path first (i.e. starting with some minimal kickstart and seeing if that fails, and in what conditions).