What were you trying to do that didn't work?

Trying to create the ReaR ISO on a UEFI system, the procedure fails by default with:

[root@vm-uefi8 ~]# rear mkrescue
[...]
  2023-11-09 07:40:04.612333077 grub2-mkstandalone may fail to make a bootable EFI image of GRUB2 (no /usr/*/grub*/x86_64-efi/moddep.lst file)
  2023-11-09 07:40:04.613301337 GRUB2 modules to load: fat part_gpt xfs
  grub2-mkstandalone: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist. Please specify --target or --directory. 

This is expected to happen because the missing package should not be used on RHEL.

Instead it's mandatory to put the following variables in local.conf:

UEFI_BOOTLOADER=/boot/efi/EFI/redhat/grubx64.efi
SECURE_BOOT_BOOTLOADER=/boot/efi/EFI/redhat/shimx64.efi 

This is documented in KCS https://access.redhat.com/solutions/7006730 but the KCS won't be seen by customers having systems with grub2-efi-x64-modules package preinstalled somehow. Even in such case, the variables should always be used to be able to automatically support SecureBoot and to align to what RHEL does: EFI always boots shim then grubx64.

I think we need to have these vars be there by default somehow.

Maybe this is somehow a dup of BZ https://bugzilla.redhat.com/show_bug.cgi?id=2196445, I'm not following much the ReaR work these days.

Ideally ReaR should just work out of the box for RHEL/Fedora customers.

There is also that duplicate entry when booting the ISO "Secure Boot", "Non Secure Boot" if I remember correctly, all this could be handled through this Jira, which could end up in being "Provide zeroconf UEFI support on RHEL".

Please provide the package NVR for which bug is seen:

rear-2.6

How reproducible:

Always