Bug 2224085

Summary: Leapp is stuck in Interim System when --debug is specified
Product: Red Hat Enterprise Linux 8 Reporter: Sergii Golovatiuk <sgolovat>
Component: leapp-repositoryAssignee: Petr Stodulka <pstodulk>
Status: CLOSED MIGRATED QA Contact: upgrades-and-conversions
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.6CC: jpretori
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-12 14:47:24 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
Virtual Console output none

Description Sergii Golovatiuk 2023-07-19 18:29:05 UTC 
Created attachment 1976587 [details]
Virtual Console output

Description of problem:

Leapp is stuck in Interim System when --debug is specified.

How reproducible:

Always

Steps to Reproduce:
1. Get Dell PowerEdge R640 with iDRAC
2. Install RHEL 8.6
3. Run leapp upgrade with --debug
4. Reboot and see iDRAC console

Actual results:

System is stuck with "early console in setup code" and doesn't reboot

Expected results:

After IPU in Interim OS, system is rebooted into targeted OS.

Additional info:

BIOS Version	2.10.0
iDRAC Firmware Version	4.40.00.00 

Though it was reproduced on 2.12-2.18.1 with iDRAC versions 5.00.00.00-7.00.00.00

It's a continuation of https://bugzilla.redhat.com/show_bug.cgi?id=2196288
Comment 1 RHEL Program Management 2023-09-12 14:46:52 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 2 RHEL Program Management 2023-09-12 14:47:24 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.