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.
Description of problem:
continuing from bug 1212128 ,
install rhel 7.2 and update or install multiple kernels
we not don't get systemd.debug but we do have mis-ordering of the kernels in the grub menu.
Version-Release number of selected component (if applicable):
How reproducible: 100%
Steps to Reproduce:
1. install rhel 7.2
2. install another kernel
3. kernels are now mismatched but grub defaults to highlighting on the correct kernel
Actual results:
kernels are in wrong order, but system will boot to correct one.
Expected results:
kernels to be in correct order in grub.
Additional info:
Retested with grubby-8.28-18.el7:
[root@localhost ~]# echo "MAKEDEBUG=yes" >> /etc/sysconfig/kernel
[root@localhost ~]# yum install ./kernel-3.10.0-507.el7.x86_64.rpm
The result is that the non-debug boot entry is listed first, following the debug boot entry. The problem is that the debug entry is selected to be booted by default, which is not expected:
Red Hat Enterprise Linux Server (3.10.0-507.el7.x86_64) 7.3 (Maipo)
Red Hat Enterprise Linux Server (3.10.0-507.el7.x86_64) 7.3 (Maipo) with> << selected by default
Red Hat Enterprise Linux Server (3.10.0-506.el7.x86_64) 7.3 (Maipo)
Red Hat Enterprise Linux Server (0-rescue-49a0cff6c58a443eba05fa166c4349>
Since the fix is incomplete, moving back to ASSIGNED.
On RHEL 7.3 the order is now as expected (first normal, second with debugging) altough #c9 states "moving to 7.4 release"
but now the debugging entry is selected as default boot entry.
see also: https://bugzilla.redhat.com/show_bug.cgi?id=1367792#c6
It sounds like two distinct problems are being discussed here: an unexpected ordering of the entries on the grub boot menu (Kathryn), vs the wrong entry being marked as the default (Jan, Thomas, and me too). Can someone clarify whether these are different symptoms of the same underlying problem in grubby, or should these be tracked as two separate bugs?
Comment 32Radosław Piliszek
2017-02-16 08:59:57 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, 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-2017:2042