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.

During RHEL 8 > RHEL 9 upgrade, after rebooting into the upgrade initramdisk and issuing the first post-reboot Leapp execution, it's possible to see the false positive emergency mode even when the upgrade is still in progress and no issue occured in reality. This can happen if user pres e.g. Enter when booted inside the upgrade environment. If user does not do anything else, usually despite the emergency console, upgrade is finished correctly in a time.


To check whether the emergency console has been raised by "falsely", check whether the leapp is still running:
   # ps -e | grep leapp && echo "The upgrade is still running do nothing and wait"

Just waiting, if there is no issue, the machine will be later upgrade automatically and the system boot to rhel 9. If you realize it takes a lot of time, you can use the command again to check whether the upgrade still continues or whether the error has been hit really.



Additional info:
 - most probably the issue is connected to the fact the systemd-nspawn is executed with the --console=pipe option which has been discovered in the past it need to be used on RHEL 9 to work correctly on some machines. It's going to be investigated

The fix has been merged in upstream:
  * https://github.com/oamg/leapp-repository/pull/906

The related BZ for the documentation:
 * https://bugzilla.redhat.com/show_bug.cgi?id=2088112

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (leapp-repository bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:7590