-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-10.0.beta
-
None
-
No
-
None
-
rhel-sst-cs-bootloaders
-
5
-
False
-
-
None
-
None
-
None
-
None
-
None
In live image installation scenarios, the posttrans scriptlet from grub2-common [1], which is responsible for generating the grub.cfg file, does not get executed.
This issue arises because packages files (including the grub2-common) are deployed by the installer via `rsync`. Therefore the usual RPM installation triggers are not invoked.
As a result, the grub.cfg file is not generated leading to boot issues after installation.
Request:
To remove Anaconda's custom handling of grub configuration [2] I suggest that the logic for generating the grub.cfg file be moved from the posttrans scriptlet into a separate, reusable helper script. This script should be callable directly by Anaconda during the installation process, enabling it to generate the necessary grub.cfg for both live image installations and other payload scenarios.
[1] https://src.fedoraproject.org/rpms/grub2/blob/rawhide/f/grub2.spec#_382
[2] https://github.com/rhinstaller/anaconda/pull/5996
Reproducible: Always
- blocks
-
RHEL-58830 RHEL-10: Anaconda creates its own version of EFI/redhat/grub.cfg wrapper
- Planning