Bug 2213226
| Summary: | Post conversion of UEFI based CentOS 7.9 to RHEL 7.9 fail with blank screen | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Pradeep Jagtap <prjagtap> |
| Component: | convert2rhel | Assignee: | Michal Bocek <mbocek> |
| Status: | CLOSED ERRATA | QA Contact: | Upgrades and Supportability <upgrades-and-supportability> |
| Severity: | medium | Docs Contact: | Miriam Portman <mportman> |
| Priority: | unspecified | ||
| Version: | 7.9 | CC: | ddiblik, egustavs, jcastran, z |
| Target Milestone: | rc | ||
| 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-13 07:51:19 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: | |||
|
Description
Pradeep Jagtap
2023-06-07 14:22:45 UTC
Workaround 1:
============
[1] Boot the system with the RHEL DVD in Troubleshooting mode
Refer to How to boot a system into rescue mode[https://access.redhat.com/solutions/770703] for details.
[2] Set up the network
Refer to Enabling networking in rescue environment without chrooting[https://access.redhat.com/solutions/2626631] for details.
[3] Enter the chroot
# chroot /mnt/sysimage
[4] Update shim-x64 package
# yum update shim-x64-15-11.el7.x86_64 -y
[5] Exit the chroot and reboot
# exit
# exit
Workaround 2:
============
[i] Boot the system with the RHEL DVD in Troubleshooting mode
Refer to How to boot a system into rescue mode[https://access.redhat.com/solutions/770703] for details.
[ii] Set up the network
Refer to Enabling networking in rescue environment without chrooting[https://access.redhat.com/solutions/2626631] for details.
[iii] Enter the chroot
# chroot /mnt/sysimage
[iv] Add new efibootmgr entry to use grubx64.efi instead of shimx64.efi
Replace the <disk> part shown in the below command with the disk that /boot/efi is on example sda.
# efibootmgr -c -d /dev/<disk> -p 1 -l \\EFI\\redhat\\grubx64.efi -L "Red Hat Enterprise Linux 7"
[v] Exit the chroot and reboot
# exit
# exit
Thanks, @pradee Thanks, @ Sorry, hitting enter when selecting the a person through @ is not a good idea. Thanks, @prjagtap, for reporting the issue and figuring out the root cause. I believe this bug is related to https://issues.redhat.com/browse/RHELC-899 and will be released in convert2rhel 1.3.0 soon. @ddiblik has tested your reproducer with convert2rhel 1.2 and the bug didn't manifest. So there's likely more to it than covered in your reproducer. But since you, Pradeep, have identified that the root cause is the old version of shim being installed, the fix of https://issues.redhat.com/browse/RHELC-899 is most likely to fix this issue. @mportman, no need to document it, considering the imminent release of 1.3 that should have it fixed, and the fact that we don't have a proper reproducer. This bug was verified by upstream pipeline for the fix provided in the PR#833 as well as the regression test suite. Tested with both onvert2rhel-1.3.1-1.el7.noarch.rpm and onvert2rhel-1.3.1-1.el8.noarch.rpm on all targets. 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 (convert2rhel 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/RHEA-2023:3569 |