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:
Could not load BootEntry when using boom create. Unsure if this is expected or not; unclear on what the warnings mean. Outside of the warnings everything seemed to work normally.
Version-Release number of selected component (if applicable):
kernel-4.18.0-48.el8.x86_64
python3-boom-0.9-5.el8.noarch
boom-boot-conf-0.9-5.el8.noarch
boom-boot-grub2-0.9-5.el8.noarch
boom-boot-0.9-5.el8.noarch
Steps to Reproduce:
# yum -y install *boom*
# lvcreate --size 512m --snapshot --name snap_root rhel/root
# boom profile create --from-host --uname-pattern Linux
# boom create --profile "e6f881a" --title "RHEL Snapshot" --root-lv rhel/snap_root
Actual results:
[root@localhost ~]# boom create --profile "e6f881a" --title "RHEL Snapshot" --root-lv rhel/snap_root
WARNING - Could not load BootEntry '/boot/loader/entries/535a443e291d42bea50b989701c5a851-4.18.0-32.el8.x86_64.conf': 'id'
WARNING - Could not load BootEntry '/boot/loader/entries/535a443e291d42bea50b989701c5a851-0-rescue.conf': 'id'
WARNING - Could not load BootEntry '/boot/loader/entries/535a443e291d42bea50b989701c5a851-4.18.0-40.el8.x86_64.conf': 'id'
WARNING - Could not load BootEntry '/boot/loader/entries/535a443e291d42bea50b989701c5a851-4.18.0-48.el8.x86_64.conf': 'id'
Created entry with boot_id 0d0f768:
title RHEL Snapshot
machine-id 535a443e291d42bea50b989701c5a851
version 4.18.0-48.el8.x86_64
linux /vmlinuz-4.18.0-48.el8.x86_64
initrd /initramfs-4.18.0-48.el8.x86_64.img
options root=/dev/rhel/snap_root ro rd.lvm.lv=rhel/snap_root
Expected results:
No warnings
A cosmetic issue caused by boom not understanding default BLS entries not created by itself. These are properly ignored. IMO this can wait for next minor release
We actually discussed addressing this for GA - it's a trivial change to switch to "info" log level, and improves user experience (as well as matching with demos and docs we've prepared). If we can get it in then I think that's still the best idea.
I've committed two changes to address this bug: the first changes the log level of the message from WARNING to INFO (so it is only shown on the terminal if --verbose is given), and the second makes the exception used when an unknown key is found more specific, so that the problem is better described in the error message:
WARNING - Could not load BootEntry '/boot/loader/entries/611f38fd887d41dea7eb3403b2730a76-4.15.17-200.fc26.x86_64.conf': 'id'
vs:
INFO - Could not load BootEntry '/boot/loader/entries/611f38fd887d41dea7eb3403b2730a76-4.15.17-200.fc26.x86_64.conf': Unknown BLS key 'id'
commit 2c6240c90d7c9262d3566de38d19433979290287 (HEAD -> master)
Author: Bryn M. Reeves <bmr>
Date: Wed Jan 9 15:20:27 2019 +0000
bootloader: raise LookupError on unknown BLS keys
commit 40ddddf5c1fa14cd7d39731fd545fe02aab328d0 (origin/master)
Author: Bryn M. Reeves <bmr>
Date: Tue Jan 8 16:48:19 2019 +0000
boom: reduce log level of "Could not load BootEntry" messages
Marking this verified (SanityOnly).
I only saw INFO messages instead of WARNING now with the latest rpm.
kernel-4.18.0-80.el8 BUILT: Wed Mar 13 07:47:44 CDT 2019
boom-boot-0.9-7.el8 BUILT: Mon Jan 14 14:00:54 CST 2019
lvm2-2.03.02-6.el8 BUILT: Fri Feb 22 04:47:54 CST 2019
lvm2-libs-2.03.02-6.el8 BUILT: Fri Feb 22 04:47:54 CST 2019
lvm2-dbusd-2.03.02-6.el8 BUILT: Fri Feb 22 04:50:28 CST 2019
lvm2-lockd-2.03.02-6.el8 BUILT: Fri Feb 22 04:47:54 CST 2019
[root@hayes-01 ~]# boom list -V
INFO - Loading profiles from /boot/boom/profiles
INFO - Loaded 1 profiles
INFO - Loading boot entries from '/boot/loader/entries'
INFO - Could not load BootEntry '/boot/loader/entries/2ce843c4f1f2458da89ff8a539ccf929-4.18.0-80.el8.x86_64.conf': Unknown BLS key 'id'
INFO - Could not load BootEntry '/boot/loader/entries/2ce843c4f1f2458da89ff8a539ccf929-0-rescue.conf': Unknown BLS key 'id'
INFO - Loaded 0 entries
BootID Version Name RootDevice Options Machine ID