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 824041 - grub2 always chooses newest kernel available as default option
Summary: grub2 always chooses newest kernel available as default option
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: grub2
Version: 7.0
Hardware: All
OS: Linux
high
urgent
Target Milestone: rc
: ---
Assignee: Peter Jones
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1025505
TreeView+ depends on / blocked
 
Reported: 2012-05-22 15:44 UTC by Vladimir Benes
Modified: 2013-12-18 16:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
If Fedora 17 or later is installed on the system, the kernel uses a shared /boot partition, and the user installs Red Hat Enterprise Linux 7.0 Beta which uses the same /boot partition, the latest kernel will be used by GRUB 2. That is, Red Hat Enterprise Linux 7.0 Beta can use a Fedora kernel if this is later, resulting in certain modules to be limited or non-functioning (for example, sound or networking). To work around the problem, the correct kernel must be chosen manually.
Clone Of:
Environment:
Last Closed: 2013-12-18 16:16:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Vladimir Benes 2012-05-22 15:44:53 UTC 
Description of problem:
when installing rhel7 over f17 and using same boot partition (this seems to be quite common) grub mkconfig choses f17's kernel as default option as it's newer. Then I need to go into advanced option and chose the rhel7 one.
 

Version-Release number of selected component (if applicable):
grub2-2.0.0-27.beta5

How reproducible:
100%

Steps to Reproduce:
1.install F17 or any newer kernel into shared partition 
2.install RHEL7 with option to install grub enabled
3.boot RHEL7 default option
  
Actual results:
wrong plymouth
modules (e.g networking) unavailable
need to go into advance options and chose correct kernel there

Expected results:
correct kernel chosen as default option
Comment 1 Vladimir Benes 2012-05-22 15:51:20 UTC 
just to explain more: I installed RHEL7 next to F17 no update.. clean install.. no update
Comment 2 Ludek Smid 2012-06-22 14:38:40 UTC 
Could you verify that bug is still valid for RHEL 7.0 Alpha 2?
Comment 3 Vladimir Benes 2012-06-25 11:41:34 UTC 
(In reply to comment #2)
> Could you verify that bug is still valid for RHEL 7.0 Alpha 2?
yes, it does!
Comment 5 David Cantrell 2013-10-28 15:44:50 UTC 
This is entirely valid, but is the nature of things when dealing with Fedora and RHEL on the same system.  Fedora will almost always have a more recent kernel than RHEL.

I'm moving this out to 'rc' for the target because I don't feel it's really critical for beta.
Comment 6 RHEL Program Management 2013-12-18 16:16:53 UTC 
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.