What were you trying to do that didn't work?

Attempting to clean up following a leapp upgrade from RHEL8 to RHEL9. A modification to the boom boot entries made by kdumpctl/grubby during the upgrade process causes the boot_id of the snapshot boot entry to change.

It's possible for external tools to modify boom manage boot entries. In this case the boot_id of the modified entry no longer matches the value stored in the boot entry filename: this leads to boom refusing to delete the boot entry since it is marked read-only.

Please provide the package NVR for which bug is seen:

boom-boot-1.3-2.el8.noarch

How reproducible:

100%

Steps to reproduce

1. create a boom boot entry on RHEL8 then upgrade to RHEL9 using leapp
2. boom list

   [root@localhost ~]# boom list
   BootID  Version                      Name                     RootDevice                            
   7275070 4.18.0-513.24.1.el8_9.x86_64 Red Hat Enterprise Linux /dev/mapper/rhel-root                 
   8ae3e64 4.18.0-513.24.1.el8_9.x86_64 Red Hat Enterprise Linux /dev/rhel/root_snapshot_before_changes
   

1. Boot into the RHEL8 snapshot and try to delete the listed boot entry

   [root@localhost ~]# boom delete 8ae3e64
   

Expected results

[root@localhost ~]# boom delete 8ae3e64
Deleted 1 entry

Actual results

[root@localhost ~]# boom delete 8ae3e64
Cannot delete read-only boot entry: /boot/loader/entries/6db8de82fe42457a93cb9fab744d2e99-5f9e916-4.18.0-513.24.1.el8_9.x86_64.conf

Upstream status

A recent change to boom allows boom boot entries with mis-matched boot_id values to be automatically repaired. This allows subsequent boom operations (delete, edit etc.) to work on the modified entry without further user intervention:

commit 40d96634870e16ff3e719e16e432b7c9bf803181
Author: Bryn M. Reeves <bmr@redhat.com>
Date:   Tue May 14 10:46:07 2024 -0400

    boom.bootloader: repair boom entries with mismatched boot_id
    
    When loading a boom boot entry from a file name that does not match the
    boot_id re-write the entry so that it can be manipulated by future
    invocations of the boom command.
    
    Signed-off-by: Bryn M. Reeves <bmr@redhat.com>