-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
rhel-9.7
-
None
-
None
-
Critical
-
rhel-bootloader
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
On kernel update or reinstallation, the BLS entry contains both $tuned_params and $tuned_initrd* variables on their respective line, e.g.:
# /bin/kernel-install add $(uname -r) /lib/modules/$(uname -r)/vmlinuz # cat /boot/loader/entries/c02acfcda06fa680ce918117ce9e5aed-5.14.0-611.8.1.el9_7.x86_64.conf [...] initrd /initramfs-5.14.0-611.8.1.el9_7.x86_64.img $tuned_initrd options root=/dev/mapper/rhel-root ro resume=/dev/mapper/rhel-swap rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap console=tty0 console=ttyS0,115200n8 crashkernel=1G-2G:192M,2G-64G:256M,64G-:512M $tuned_params [...]
But after executing grub2-mkconfig -o /etc/grub2.cfg --update-bls-cmdline the $tuned_params variable disappears:
# grub2-mkconfig -o /etc/grub2.cfg --update-bls-cmdline # cat /boot/loader/entries/c02acfcda06fa680ce918117ce9e5aed-5.14.0-611.8.1.el9_7.x86_64.conf [...] initrd /initramfs-5.14.0-611.8.1.el9_7.x86_64.img $tuned_initrd options root=/dev/mapper/rhel-root ro resume=/dev/mapper/rhel-swap rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap console=tty0 console=ttyS0,115200n8 [...]
My /etc/default/grub has no TUNED line at all.
What is the impact of this issue to you?
This breaks changing tuned profile when it adds parameters to the kernel command line.
Please provide the package NVR for which the bug is seen:
grub2-tools-2.06-114.el9_7.noarch
tuned-2.26.0-1.el9.noarch
How reproducible is this bug?
Always, see above.
