-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-8.9.0
-
None
-
Important
-
1
-
rhel-sst-upgrades
-
None
-
False
-
-
None
-
Leapp: 9.6 & 10.0
-
None
-
None
-
-
x86_64
-
None
What were you trying to do that didn't work?
Upgrade from RHEL 8 to RHEL 9 after RHEL 7>8 upgrade on a Gen1 VM in Azure.
Please provide the package NVR for which bug is seen:
leapp-0.16.0-2.el8.noarch
How reproducible:
Every time a system is upgraded from RHEL 7>8>9
Steps to reproduce
- Upgrade from RHEL 7 to RHEL 8
- Upgrade from RHEL 8 to RHEL 9
Expected results
System should be able to boot from the new RHEL 9 kernel
Actual results
The old RHEL 7 boot entries from /boot/efi/EFI/redhat/grub.cfg are copied to /boot/grub2/grub.cfg, so the grub menu only shows RHEL 7 kernels (which are no longer installed) and the system fails to boot.
Additional information
Background: After upgrade from RHEL 7 > RHEL 8 (successful) > RHEL 9, server fails to boot and grub menu only shows RHEL 7 kernels even though there are no RHEL 7 kernels installed anymore. This affects Gen1 Azure VMs, meaning that they're set up with both /boot and /boot/efi, but it always boots in BIOS/Legacy mode (confirmed with Azure support that all Gen1 VMs always boot in Legacy/BIOS and this cannot change). Suspect that because on UEFI systems in RHEL 9 the /boot/efi/EFI/redhat/grub.cfg is just a small file that loads /boot/grub2/grub.cfg, leapp is copying /boot/efi/EFI/redhat/grub.cfg to /boot/grub2/grub.cfg during the upgrade. Prior to the upgrade to RHEL 9 the content in this file isn't used during boot at all because it's in Legacy/BIOS boot mode. However I don't see anything in the leapp logs that indicates that this is happening.
