Bug 2138320

Summary: Dropped to emergency shell with Satellite/Kickstart installation
Product: Red Hat Enterprise Linux 9 Reporter: Torkil Svensgaard <torkil>
Component: dracutAssignee: Pavel Valena <pvalena>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 9.0CC: ahumbe, lagordon, lnarvaez, pvalena
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-27 11:53:01 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
Screenshot of the final error none

Description Torkil Svensgaard 2022-10-28 06:04:19 UTC
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.

Comment 5 Pavel Valena 2023-06-27 11:53:01 UTC
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 ***

Comment 6 Pavel Valena 2023-06-27 11:57:12 UTC
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).