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.

Bug 1652705

Summary: boom list shows warnings
Product: Red Hat Enterprise Linux 8 Reporter: Marko Myllynen <myllynen>
Component: boom-bootAssignee: Bryn M. Reeves <bmr>
Status: CLOSED DUPLICATE QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: agk, bmr, jbrassow, mcsontos, mpitt
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-28 21:25:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marko Myllynen 2018-11-22 16:23:40 UTC
Description of problem:
RHEL 8.0 Beta installation after installing boom-boot:

root@localhost:~# boom list
WARNING - Could not load BootEntry '/boot/loader/entries/72628edb4fc140ce92c3a3a2e02fcaac-4.18.0-32.el8.x86_64.conf': 'id'
BootID  Version                  Name                     RootDevice
root@localhost:~# 

Version-Release number of selected component (if applicable):
boom-boot-0.9-5.el8.noarch

Comment 1 Bryn M. Reeves 2018-11-23 11:20:29 UTC
You don't have any BLS entries that boom can currently load: we have a few options here, including ignoring them (i.e. boom will only deal with the entries that it has created), or allowing them to be used read-only (you can only clone the system provided entries, not edit them).

Unfortunately these changes broke so late that we have not been able to make any changes for 8.0: there are a few minor changes that we could make that would make things less confusing for end users but some of this crosses components, and we will not be able to make any bigger changes until 8.1.

Comment 2 Martin Pitt 2019-01-07 08:39:24 UTC
Maybe Marko meant the WARNING? I get that, too. Right after installing boom-boot, `boom list` says

# boom  list
WARNING - Could not load BootEntry '/boot/loader/entries/7b5128c16c4c4526ba5f8a834bd7f1cc-4.18.0-57.el8.x86_64.conf': 'id'
WARNING - Could not load BootEntry '/boot/loader/entries/7b5128c16c4c4526ba5f8a834bd7f1cc-0-rescue.conf': 'id'

and these stay around even after creating entries:

# boom  list
WARNING - Could not load BootEntry '/boot/loader/entries/7b5128c16c4c4526ba5f8a834bd7f1cc-4.18.0-57.el8.x86_64.conf': 'id'
WARNING - Could not load BootEntry '/boot/loader/entries/7b5128c16c4c4526ba5f8a834bd7f1cc-0-rescue.conf': 'id'
BootID  Version                  Name                     RootDevice         
5fef6eb 4.18.0-57.el8.x86_64     Red Hat Enterprise Linux /dev/rhel/rollback1

Comment 3 Bryn M. Reeves 2019-01-07 14:10:38 UTC
These warnings are due to the fact that late in the RHEL8 development process the system boot mechanism was switched from entries in grub.cfg to using the BLS facility. Up until this boom was the only user of BLS in the base distribution so we have been in catchup to make these work cleanly side-by-side.

We should be able to make a change for GA to reduce the log level of these messages (and the system BLS entries will not appear in boom tool output in 8.0) so users will not see this when running the tool. We will also be working for a later release to support the system entries in boom as read-only: the user will be able to clone them and use them as the basis of new entries, but not modify or remove them.

Comment 4 Bryn M. Reeves 2019-01-07 14:11:59 UTC
That's what we're talking about: the warnings appear because the system entries have an extra key, 'id', that is not currently in the upstream BLS spec. These will hopefully disappear before GA and we will add support for manipulating them in a future update.

Comment 5 Marian Csontos 2019-01-28 21:25:23 UTC

*** This bug has been marked as a duplicate of bug 1661746 ***