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 bug was initially created as a clone of Bug #1663891 +++
Description of problem: When creating boom entries, these don't actually appear in the grub boot menu. This only happens after manually regenerating the config. The documentation (https://github.com/bmr-cymru/boom) does not mention this, and this is also not necessary on RHEL 8 beta.
This might be a bug or missing feature in grub2 of course, so please reassign as appropriate.
Version-Release number of selected component (if applicable):
boom-boot-0.9-4.fc29.noarch
grub2-common-2.02-62.fc29.noarch
How reproducible: Always
Steps to Reproduce:
1. Create a snapshot:
lvcreate --snapshot -n rollback1 --size 1G fedora/root
2. Create a boom profile:
boom profile create --from-host --uname-pattern fc29
3. Create a boom entry for the rollback:
boom create --title "update rollback test" --rootlv fedora/rollback1
4. Reboot
Actual results: "Snapshots" submenu or rollback entry does not appear in grub menu. Only after "grub2-mkconfig > /boot/grub2/grub.cfg" and rebooting again it does.
Expected results: Generated entries appear in the grub menu without further ado.
Additional info:
--- Additional comment from Martin Pitt on 2019-01-07 09:54:17 UTC ---
Actually it seems this isn't necessary after every new boom create/remove operation, just once after package install. This adds this snippet to /boot/grub2/grub.cfg:
### BEGIN /etc/grub.d/42_boom ###
submenu "Snapshots" {
insmod blscfg
bls_import
}
### END /etc/grub.d/42_boom ###
which seems to be enough to activate the BLS functionality and read /boot/loader/entries/*. So installation of the package should trigger a grub update.
Current versions of boom will print a warning message when this is the case, suggesting the user re-run grub2-mkconfig:
# boom create --title "Boom test" --rootlv rhel/root
WARNING - Boom configuration not found in grub.cfg
WARNING - Run 'grub2-mkconfig > /boot/grub2/grub.cfg' to enable