kernel entries in grub.cfg are not correctly updated when GRUB_ENABLE_BLSCFG=false in RHEL 10

Solution Verified - Updated -

Issue

  • When GRUB_ENABLE_BLSCFG=false is set in /etc/default/grub in RHEL 10, kernel changes are not properly reflected in /boot/grub2/grub.cfg file:
    1. After installing a new kernel, the generated grub.cfg entry is missing the initrd line.
    2. After removing a kernel, its corresponding entry remains in grub.cfg.

Environment

  • Red Hat Enterprise Linux 10
  • GRUB_ENABLE_BLSCFG=false set in /etc/default/grub
  • grub2-*2.12-14.el10_0.x86_64

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content