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 1842626 - boom: consolidate RHEL8 OS profiles
Summary: boom: consolidate RHEL8 OS profiles
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: boom-boot
Version: 8.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: LVM and device-mapper development team
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
: 1649423 1848123 (view as bug list)
Depends On:
Blocks: 1660923
TreeView+ depends on / blocked
 
Reported: 2020-06-01 17:46 UTC by Bryn M. Reeves
Modified: 2021-09-06 15:19 UTC (History)
7 users (show)

Fixed In Version: boom-boot-1.2-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 01:57:39 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4532 0 None None None 2020-11-04 01:57:48 UTC

Description Bryn M. Reeves 2020-06-01 17:46:11 UTC 
Description of problem:
The current boom-boot package for RHEL8 (boom-boot-1.1-2.el8) contains two built-in OsProfile definitions for RHEL8:

# boom profile list
OsID    Name                     OsVersion  
f44fb52 Red Hat Enterprise Linux 8.1 (Ootpa)
1ba0043 Red Hat Enterprise Linux 8.2 (Ootpa)

These are generated from the respective /etc/os-release files for the corresponding release.

There's no real need to do this unless a user is actually dealing with multiple minor versions in parallel AND needs to specify different options or other template values for the two releases.

We support the ability to have differentiated profiles for advanced use cases where this may be needed but for most users this is an unnecessary distraction and may lead to confusion (for example when making edits to a profile).

Version-Release number of selected component (if applicable):
boom-1.1-2.el8

How reproducible:
100%

Steps to Reproduce:
1. boom profile list


Actual results:
OsID    Name                     OsVersion  
f44fb52 Red Hat Enterprise Linux 8.1 (Ootpa)
1ba0043 Red Hat Enterprise Linux 8.2 (Ootpa)

Expected results:
OsID    Name                     OsVersion 
4abe4f7 Red Hat Enterprise Linux 8 (Ootpa)

Additional info:

commit 6c3ae3f6294213e187f83a0be7eca9e0818ebbd0
Author: Bryn M. Reeves <bmr>
Date:   Mon Jun 1 18:27:28 2020 +0100

    tests: consolidate RHEL8 OS profiles
Comment 1 Bryn M. Reeves 2020-06-24 12:20:25 UTC 
Note that the consolidated OsProfile should be installed to /boot/boom/profiles automatically.
Comment 2 Bryn M. Reeves 2020-06-24 14:50:36 UTC 
Fixed upstream in boom-1.2.
Comment 6 Bryn M. Reeves 2020-07-15 15:06:49 UTC 
*** Bug 1848123 has been marked as a duplicate of this bug. ***
Comment 7 Roman Bednář 2020-09-16 11:00:11 UTC 
Not sure about the presence of rhel7 and Fedora profiles, was this intended?


# ls /boot/boom/profiles
4abe4f7fd38fc7506cbe2f42b1b85d54af3b29b1-rhel8.profile    72e3679e3556b8e1620dd3b6e5d2a1f508e5ba43-rhel7.7.profile
4aff687826c2b83409c0cbd097a93c405681e227-rhel7.8.profile  8896596a45fcc9e36e9c87aee77ab3e422da2635-fedora30.profile

# cat /etc/os-release
NAME="Red Hat Enterprise Linux"
VERSION="8.3 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.3"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.3 Beta (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8.3:beta"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.3
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.3 Beta"

# boom profile list
OsID    Name                            OsVersion
8896596 Fedora                          30 (Workstation Edition)
4abe4f7 Red Hat Enterprise Linux        8 (Ootpa)
72e3679 Red Hat Enterprise Linux Server 7.7 (Maipo)
4aff687 Red Hat Enterprise Linux Server 7.8 (Maipo)

# rpm -qa | grep boom
python3-boom-1.2-2.el8.noarch
boom-boot-1.2-2.el8.noarch
boom-boot-grub2-1.2-2.el8.noarch
boom-boot-conf-1.2-2.el8.noarch
Comment 8 Bryn M. Reeves 2020-09-16 12:40:55 UTC 
Yes, that's expected: boom is designed for shared /boot volume (see the BootLoader Spec for more details: https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/).

Users can manage the boot entries for different installed operating systems using any installed instance of boom: we provide some additional profiles as examples and for users with upgrade (e.g. RHEL7-8 with Leapp/boom) use cases.
Comment 9 Bryn M. Reeves 2020-09-21 15:40:17 UTC 
*** Bug 1649423 has been marked as a duplicate of this bug. ***
Comment 12 errata-xmlrpc 2020-11-04 01:57:39 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (boom-boot bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4532
Note You need to log in before you can comment on or make changes to this bug.