View Issue Details

IDProjectCategoryView StatusLast Update
0000056AlmaLinux-8grub2public2021-07-23 15:28
ReporterUnknownVictim Assigned Toalukoshko  
PrioritylowSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Platformx86_64OSAlmaLinuxOS Version8.3
Summary0000056: /boot/grub2/grub.cfg not being updated during new kernel installation
DescriptionInstalling newest kernel via "yum update" downloads and installs kernel-4.18.0-240.15.1.el8_3.x86_64 and its dependencies, however, /boot/grub2/grub.cfg is not updated during the process.

/boot/grub2/grub.cfg can be manually updated via the command "grub2-mkconfig -o /boot/grub2/grub.cfg".
Steps To ReproduceFreshly installed minimal server, run "yum update" to download and install the updated kernel and dependencies.
Check if /boot/grub2/grub.cfg has been updated with the new kernel.
(grep 4.18.0-240.15.1.el8_3.x86_64 /boot/grub2/grub.cfg)
TagsNo tags attached.
abrt_hash
URL

Activities

alukoshko

2021-04-04 16:10

developer   ~0000119

Hello and thanks for report.
It shouldn't be updated I believe as boot entries are located here: /boot/loader/entries/
Do you have new kernel available in GRUB?

UnknownVictim

2021-04-04 16:34

reporter   ~0000120

/boot/loader/entries/ is being updated during "yum update",

[[email protected] ~]# ls -l /boot/loader/entries/
total 12
-rw-r--r--. 1 root root 388 Apr 3 23:30 96caaef3565d4035b2459c52e5270b7e-0-rescue.conf
-rw-r--r--. 1 root root 368 Apr 3 23:37 96caaef3565d4035b2459c52e5270b7e-4.18.0-240.15.1.el8_3.x86_64.conf
-rw-r--r--. 1 root root 316 Apr 3 23:30 96caaef3565d4035b2459c52e5270b7e-4.18.0-240.el8.x86_64.conf
[[email protected] ~]#

however /boot/grub2/grub.cfg is not.
On reboot, the system is not loading the new kernel. /boot/grub2/grub.cfg was not reconfigured with the new kernel's details.
After running "grub2-mkconfig -o /boot/grub2/grub.cfg", /boot/grub2/grub.cfg is configured with the new kernel's details and the new kernel is loaded on reboots.

Hope that clarifies what I am seeing.

Thank you.

UnknownVictim

2021-05-09 05:25

reporter   ~0000188

FWIW, same issue see when installing kernel 4.18.0-240.22.1.el8_3.x86_64.

alukoshko

2021-07-07 18:10

developer   ~0000300

Is problem still occur in 8.4?

giulio

2021-07-23 15:28

reporter   ~0000312

By default, BLS boot config system is used:
- kernel-core rpm ships a bls.conf file
- /usr/lib/kernel/install.d/20-grub.install copies this file to /boot/loader/entries/<new-name>.conf during kernel install
- grub.cfg contains "blscfg" command which will read /boot/loader/entries/*.conf at runtime, and create boot menu on the fly
- grub.cfg is never automatically updated during kernel updates, because it does not contain any reference to any kernel/initramfs, so it doesn't need to be updated

If you disable BLS by using GRUB_ENABLE_BLSCFG=false in /etc/default/grub then see this:
https://bugzilla.redhat.com/show_bug.cgi?id=1899903
I think, going on, disabling BLS will be supported "best effort" by Red Hat / Fedora

OTOH, if you have GRUB_ENABLE_BLSCFG=true in /etc/default/grub and boot menu won't update, check whether blscfg is present in grub.cfg:
....
...
insmod blscfg
blscfg
### END /etc/grub.d/10_linux ###


Also, check that /etc/machine-id is always the same and is not somehow updated, otherwise /boot/loader/entries/*.conf files may be out of sync.

Issue History

Date Modified Username Field Change
2021-04-04 05:32 UnknownVictim New Issue
2021-04-04 16:10 alukoshko Note Added: 0000119
2021-04-04 16:34 UnknownVictim Note Added: 0000120
2021-05-09 05:25 UnknownVictim Note Added: 0000188
2021-07-07 18:10 alukoshko Note Added: 0000300
2021-07-07 18:10 alukoshko Assigned To => alukoshko
2021-07-07 18:10 alukoshko Status new => assigned
2021-07-23 15:28 giulio Note Added: 0000312