Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The version of boom packages in RHEL7 contains a bug in the handling of additional kernel command line options specified with --add-opts. This causes the boot_id of affected boot entries to change unexpectedly preventing boom from removing them with the "boom delete" command.
Version-Release number of selected component (if applicable):
lvm2-python-boom-1.2-2.el7_9.5.noarch
How reproducible:
100%
Steps to Reproduce:
1. Create a boot entry with multiple options specified with --add-opts:
[root@localhost ~]# boom create --title "AddOpts Test" --root-lv rhel/root --add-opts "a b c"
Created entry with boot_id c40fcac:
title AddOpts Test
machine-id 7d70d7fcc6884be19987956d0897da31
version 3.10.0-1160.88.1.el7.x86_64
linux /vmlinuz-3.10.0-1160.88.1.el7.x86_64
initrd /initramfs-3.10.0-1160.88.1.el7.x86_64.img
options root=/dev/rhel/root ro rd.lvm.lv=rhel/root a b c
grub_users $grub_users
grub_arg --unrestricted
grub_class kernel
2. Inspect the boot_id reported by "boom list"
[root@localhost ~]# boom list
BootID Version Name RootDevice
098813e 3.10.0-1160.88.1.el7.x86_64 Red Hat Enterprise Linux Server /dev/rhel/root
3. Attempt to delete the entry via either reported boot_id:
[root@localhost ~]# boom delete c40fcac
No matching entry found.
[root@localhost ~]# boom delete 098813e
Entry does not exist: /boot/loader/entries/7d70d7fcc6884be19987956d0897da31-098813e-3.10.0-1160.88.1.el7.x86_64.conf
Actual results:
The entry boot_id reported when the entry is created does not match the value reported when the entry is read back in from disk and it is not possible to delete the entry with "boom delete".
Expected results:
The boot_id remains consistent and the entry can be removed with "boom delete".
Additional info:
Users can work around this problem my manually removing the problem boot entry from /boot/loader/entries with the rm command:
[root@localhost ~]# rm -f /boot/loader/entries/7d70d7fcc6884be19987956d0897da31-098813e-3.10.0-1160.88.1.el7.x86_64.conf