Description
Affected Puppet, Ruby, OS and module versions/distributions
- Distribution: RedHat Linux 9
- Module version: all up to 5.1.2
How to reproduce (e.g Puppet code you use)
Just need to make a change to one of the kernel_parameter resources to generate a new grub.cfg.
What are you seeing
/boot/efi/EFI/redhat/grub.cfg with the output of grub2-mkconfig
What behaviour did you expect instead
/boot/efi/EFI/redhat/grub.cfg should be the stub installed from grub2-common rpm
Any additional information you'd like to impart
On redhat systems, augeasproviders_grub will always update /boot/efi/EFI/redhat/grub.cfg with the output of grub2-mkconfig when there are changes. For systems greater than EL9, this causes problems. This file should be a stub refering to files in /boot/grub2 which enables it to use /boot/grub2/grub.cfg. This is regardless of whether the system is booting in BIOS or EFI mode.
Without this stub, grub environments no longer works. For example tuned updates to cmdline options no longer work.
I will create a pull request here for the workaround we are currently using.
Refs:
That file being updated was pointed out by a support call we opened with redhat on "tuned not updating cmdline parameters". The reason for this change they pointed out is: How to configure Grub2 to be able to boot alternatively on UEFI or BIOS mode (you need redhat support access).