Open yuravk opened 1 month ago
hI @yuravk , this is actually bug in grub2 on rhel9.4. We are waiting for the fix.
Hi @pirat89 , is there a jira at redhat that could be tracked for progress/status? I just lifted our upgrade path from 8.8 > 9.2 to 8.10 > 9.4 and I'm hitting this issue. I tried the proposed fixing actor in https://github.com/oamg/leapp-repository/pull/1229 but it did not solve it... Thanks!
@morete Hi. I just returned from vacation. yes, it is tracked here: https://issues.redhat.com/browse/RHEL-40362 however I see it has restricted access :shrug: . Here is related KCS article: https://access.redhat.com/solutions/7075830
We will leave here a new update when we have more info. Currently we have internally new grub2 build available for testing which should fix this behaviour. So far, fixed grub2 package is expected to be released earlier than leapp-repository, that's why we have not merged any changes in this repository yet.
Also the #1229 PR has been developed for a little bit different issue. Unfortunately, the fix in grub2 introduced a different problems for UEFI. That's why it's affecting now larger set of machines.
We can confirm the problem is going to be fixed with the next grub2 9.4.z-stream release. Upgrades are passing with the new build as expected.
@pirat89 thanks for the update. Few weeks back I managed to see the EFI grub.cfg file after the failed upgrade is trying to source the old BIOS grub.cfg file location (which we no longer use, so does not exist) so I did workaround it by changing the automation code to create the grub config on both locations BIOS and EFI config file paths prior to running the leapp upgrade command and once the upgrade is finished then the automation reverts the workaround by deleting the old BIOS grub.cfg and updating the EFI grub.cfg... that made all work as expected so with that "temporal" workaround the upgrade works fine...
@morete thanks for the info, yes that should be possible workaround for now.
I can confirm the issue was fixed for me with grub2 2.06-82.el9
packages.
Actual behavior System doesn't boot because of missed
/boot/grub2/grub.cfg
GRUB configuration file, after upgrading of recent Red Hat Enterprise Linux release 8.10 to 9.4, and if Extensible Firmware Interface (EFI) is used.To Reproduce
leapp upgrade --debug
Expected behaviour
OS version
GRUB packages
GRUB's config file in case if EFI:
points into the broken symlink:
[root@localhost-live /]# ls -la /boot/grub2/grub.cfg ls: cannot access '/boot/grub2/grub.cfg': No such file or directory
cat /etc/redhat-release
Red Hat Enterprise Linux release 8.10 (Ootpa)
uname -a
Linux rhel8.tst 4.18.0-553.8.1.el8_10.x86_64 #1 SMP Fri Jun 14 03:19:37 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux
efibootmgr
BootCurrent: 0004 BootOrder: 0004,0000,0001,0002,0003 Boot0000 EFI Virtual disk (0.0) Boot0001 EFI VMware Virtual SATA CDROM Drive (0.0) Boot0002 EFI Network Boot0003 EFI Internal Shell (Unsupported option) Boot0004* Red Hat Enterprise Linux
rpm -qa "leapp"
python3-leapp-0.17.0-1.el8.noarch leapp-upgrade-el8toel9-0.20.0-2.el8.noarch leapp-deps-0.17.0-1.el8.noarch leapp-0.17.0-1.el8.noarch leapp-upgrade-el8toel9-deps-0.20.0-2.el8.noarch
subscription-manager list
+-------------------------------------------+ Installed Product Status +-------------------------------------------+ Product Name: Red Hat Enterprise Linux for x86_64 Product ID: 479 Version: 8.10 Arch: x86_64 Status: Subscribed Status Details: Starts: xx/xx/xxxx Ends: xx/xx/xxxx
ls -la /etc/grub2-efi.cfg
lrwxrwxrwx. 1 root root 31 Feb 21 15:12 /etc/grub2-efi.cfg -> ../boot/efi/EFI/redhat/grub.cfg
ls -la /boot/efi/EFI/redhat/grub.cfg
-rwx------. 1 root root 6645 May 29 11:01 /boot/efi/EFI/redhat/grub.cfg