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.
DescriptionNicholas, Crawford
2014-10-19 16:35:45 UTC
Description of problem:
On systems with patched kernels running grub2-mkconfig causes the system to boot the base kernel. i.e. instead of 3.10.0-128.8.1.el7 it boots 3.10.0-128.el7.
Version-Release number of selected component (if applicable):
grub2-tools-2.02-0.2.10.el7
How reproducible:
100%
Steps to Reproduce:
1. RHEL 7 system patched with a non-base kernel (8.1.el7)
2. run grub2-mkconfig -o /boot/grub2/grub.cfg
3. as config is built look at order
4. reboot
5. watch base kernel boot
Actual results:
boots older base kernel, ignores grub2-editenv list/grub2-set-default.
Expected results:
boots patched kernel, or selected kernel in grub2-editenv list/grub2-set-default.
Additional info:
It appears that RHEL7 is using the wrong selector for setting the grub2-set-default. It could potentially be "working as intended" and then this bug would be related to the %post script in kernel patches. Though documentation all specifies menuentry as the selector.
[root@localhost ~]# grub2-editenv list
saved_entry=Red Hat Enterprise Linux Server (3.10.0-123.8.1.el7.x86_64) 7.0 (Maipo)
[root@localhost ~]# uname -r
3.10.0-123.el7.x86_64
The selection appears to be based on the text following $menuentry_id_option in grub.cfg, listed by the following.
[root@localhost ~]# grep "^menuentry" /boot/grub2/grub.cfg | cut -d "'" -f4
gnulinux-3.10.0-123.el7.x86_64-advanced-3de2aca4-9fdd-42fd-9480-420d59b19a76
gnulinux-3.10.0-123.8.1.el7.x86_64-advanced-3de2aca4-9fdd-42fd-9480-420d59b19a76
gnulinux-0-rescue-b4d7fa385e6d4bd08a804d2082ef14d4-advanced-3de2aca4-9fdd-42fd-9480-420d59b19a76
in this case I run the following to preserve the patched kernel to survive grub2-mkconfig
[root@localhost ~]# grub2-set-default gnulinux-3.10.0-123.8.1.el7.x86_64-advanced-3de2aca4-9fdd-42fd-9480-420d59b19a76
[root@localhost ~]# grub2-editenv list
saved_entry=gnulinux-3.10.0-123.8.1.el7.x86_64-advanced-3de2aca4-9fdd-42fd-9480-420d59b19a76
[root@localhost ~]# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.10.0-123.el7.x86_64
Found initrd image: /boot/initramfs-3.10.0-123.el7.x86_64.img
Found linux image: /boot/vmlinuz-3.10.0-123.8.1.el7.x86_64
Found initrd image: /boot/initramfs-3.10.0-123.8.1.el7.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-b4d7fa385e6d4bd08a804d2082ef14d4
Found initrd image: /boot/initramfs-0-rescue-b4d7fa385e6d4bd08a804d2082ef14d4.img
now after a reboot I get the following.
[root@localhost ~]# grub2-editenv list
saved_entry=gnulinux-3.10.0-123.8.1.el7.x86_64-advanced-3de2aca4-9fdd-42fd-9480-420d59b19a76
[root@localhost ~]# uname -r
3.10.0-123.8.1.el7.x86_64
Comment 1Nicholas, Crawford
2014-10-19 16:37:05 UTC
Comment 3Nathan G. Grennan
2014-12-08 23:57:36 UTC
Created attachment 966037[details]
Workaround patch
The bug is either the sort command, or a misuse of the sort command in grub-mkconfig_lib. The issue revolves around .x86_64 being at the end of the strings.