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.
This is because on the virt host there is no profile set up. By default boom will not list boot entries for which it cannot find a valid profile (since we can't manipulate them usefully without an OsProfile). These entries can be optionally displayed by using --all:
[root@localhost ~]# boom list
BootID Version Name RootDevice
[root@localhost ~]# boom list --all
BootID Version Name RootDevice
40da505 5.14.0-337.el9.x86_64 /dev/mapper/rhel-root
887dc88 0-rescue-a693ef7fe2c44a559151b64919509e17 /dev/mapper/rhel-root
If you create a profile that matches the OS version then the "normal" system boot entry will start showing up:
[root@localhost ~]# boom profile create --from-host
Created profile with os_id 6514b55:
OS ID: "6514b555d12abeb890c92453c3127d7bf1f52329",
Name: "Red Hat Enterprise Linux", Short name: "rhel",
Version: "9.3 (Plow)", Version ID: "9.3",
Kernel pattern: "/vmlinuz-%{version}", Initramfs pattern: "/initramfs-%{version}.img",
Root options (LVM2): "rd.lvm.lv=%{lvm_root_lv}",
Root options (BTRFS): "rootflags=%{btrfs_subvolume}",
Options: "root=%{root_device} ro %{root_opts} crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=/dev/mapper/rhel-swap rd.lvm.lv=rhel/swap rhgb quiet",
Title: "%{os_name} %{os_version_id} (%{version})",
Optional keys: "grub_users grub_arg grub_class id", UTS release pattern: "el9"
[root@localhost ~]# boom list
BootID Version Name RootDevice
40da505 5.14.0-337.el9.x86_64 Red Hat Enterprise Linux /dev/mapper/rhel-root
The rescue boot entry will only show up with --all because the version strings used in that boot entry do not conform to the normal expected uname pattern.
The physical host where the system boot entry is showing up seems to have already had an OsProfile created as there is a boom-managed boot entry in /boot/loader/entries:
-rw-r--r--. 1 root root 537 Jul 13 21:07 7b2d82dad70f4ece8f867b6a482308de-cd14f03-5.14.0-322.el9.x86_64.conf