-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-10.0.beta
-
None
-
Moderate
-
sst_installer
-
ssg_front_door
-
18
-
1
-
False
-
-
No
-
Red Hat Enterprise Linux
-
None
-
None
-
None
-
Unspecified Release Note Type - Unknown
-
-
x86_64
-
None
What were you trying to do that didn't work?
I just found out through debugging RHEL-36186 that Anaconda was implementing the stub file /boot/efi/EFI/redhat/grub.cfg by itself (pyanaconda/modules/storage/bootloader/efi.py):
172 def write_config(self): 173 config_path = "%s%s" % (conf.target.system_root, self.efi_config_file) : 190 fd.write("search --no-floppy --fs-uuid --set=dev %s\n" % fs_uuid) 191 fd.write("set prefix=($dev)%s\n" % grub_dir) 192 fd.write("export $prefix\n") 193 fd.write("configfile $prefix/grub.cfg\n")
IMHO this is a bug, it should let grub2-common generate the stub file, because this file may evolve.
For example, it will evolve because of RHEL-4388.
Additionally without this reimplementation we would have hit RHEL-36186 earlier before RHEL9 was even released.
Please provide the package NVR for which bug is seen:
Anaconda RHEL9
How reproducible:
N/A
- clones
-
RHEL-36187 RHEL-9: Anaconda creates its own version of EFI/redhat/grub.cfg wrapper
- Planning
- is related to
-
INSTALLER-3977 Anaconda creates its own version of EFI/redhat/grub.cfg wrapper
- New
- relates to
-
RHEL-4388 EFI grub.cfg wrapper doesn't always execute properly, leading to getting "grub>" prompt
- New
-
RHEL-36186 EFI grub.cfg wrapper is wrong when having /boot on a Software Raid
- Integration