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 1315593 - [RFE] grub.conf has the last installed kernel as default boot kernel instead of the latest installed version as default
Summary: [RFE] grub.conf has the last installed kernel as default boot kernel instead ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: grubby
Version: 6.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Peter Jones
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1269194
TreeView+ depends on / blocked
 
Reported: 2016-03-08 07:53 UTC by Seiji Nishikawa
Modified: 2019-10-10 11:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-25 18:30:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Seiji Nishikawa 2016-03-08 07:53:19 UTC 
Description of problem:

grub.conf has the last installed kernel as a default boot kernel instead of the latest installed version of kernel as default.

Version-Release number of selected component (if applicable):

kernel-2.6.32-504.3.3.el6.x86_64
grub-0.97-83.el6.x86_64   
grubby-7.0.15-5.el6.x86_64


How reproducible:

Always

Steps to Reproduce:

1. Install the latest kernel e.g. kernel-2.6.32-573.el6.

2. Next install the older kernel than the one installed in step 1 e.g. kernel-2.6.32-431.el6.

3. The older kernel (in this example 2.6.32-431.el6) installed in step 2 is set as a default boot kernel in grub.conf instead of the latest version of installed kernel (in this example 2.6.32-573.el6).

Actual results:

The last installed kernel will always be a default boot kernel in grub.conf instead of the latest installed version of kernel. If an older kernel is getting installed after the newer version of kernel, we will have to manually update grub.conf to use the newer version of kernel.

Expected results:

We should like to have some option/way being introduced to update grub.conf to use latest version of kernel as the default boot kernel instead of last installed kernel.

Additional info:

Customer uses HP server automation tool which is used in the IT infrastructures to do the automation of the operations that are done at server OS level including kernel installation, which brings multiple versions of kernels installed at the same time; resulting in older kernel being set as a default boot kernel in grub.conf at times. We sould like to provide our customer with some good option/way to update grub.conf to always use the latest installed version of kernel as a default boot kernel.
Comment 2 David Kaspar // Dee'Kej 2016-03-08 15:20:22 UTC 
Hello Seiji,

I personally see the current behaviour as expected and I wouldn't definitely change the default behaviour of this. Most likely scenario is that end-user will install the older kernel because the latest/newer one isn't stable. In that case it desirable to boot into the older kernel, which should be in most cases more stable.

However, if the customer requires such a behaviour, introducing a new option for this is IMHO a good way to do it.

Nevertheless, grub is working correctly in this case (it does what it's suppose to do, by following instructions in grub.conf). Therefore, I'm switching this to grubby package, which is a configuration tool for grub.
Comment 3 Chris Williams 2016-07-25 18:30:06 UTC 
When Red Hat shipped 6.8 on May 10, 2016 RHEL 6 entered Production Phase 2. 
https://access.redhat.com/support/policy/updates/errata#Production_2_Phase
That means only "Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released"
That also means no new RFEs so this BZ is being closed WONTFIX.
Note You need to log in before you can comment on or make changes to this bug.