Rescue Kernel Regeneration Fails After Leapp Upgrade with Errors: 'cp: cannot stat /boot/bls.conf' and 'sed: can't read /boot/loader/entries/<UUID>-0-rescue.conf: No such file or directory

Solution Verified - Updated -

Issue

  • After performing a Leapp upgrade from RHEL 8.x to RHEL 9.x (or RHEL 9.x to RHEL 10.x), running the command to regenerate the rescue kernel and initial RAM disk:

    # /usr/lib/kernel/install.d/51-dracut-rescue.install add "$(uname -r)" /boot "/boot/vmlinuz-$(uname -r)"
    

    Results in the following error:

    cp: cannot stat '/boot/bls.conf': No such file or directory
    sed: can't read /boot/loader/entries/<UUID>-0-rescue.conf: No such file or directory
    

Environment

  • Red Hat Enterprise Linux 10
  • Red Hat Enterprise Linux 9
  • Red Hat Enterprise Linux 8

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