The current approach of duplicating the grub.cfg between /boot and /boot/efi/EFI/redhat means that out-of-band package updates will cause the efi version to become stale, and in some cases prevent the host from booting without manual intervention.

This will be identical to the RHEL grub.cfg redirect, but also enabling the lvm module, for 2 reasons:

• 16.2 Custom image and 17.0 overcloud image have /boot on an lvm partition, so this will be consistent with the workaround for upgrades
• If for whatever reason a user finds themselves at a grub prompt, they will be able to explore the whole filesystem including LVM volumes