Bug 808821 - Installation of new kernel via yum ignores GRUB_DEFAULT entry in /etc/default/grub
Summary: Installation of new kernel via yum ignores GRUB_DEFAULT entry in /etc/default...
Keywords:
Status: CLOSED DUPLICATE of bug 742720
Alias: None
Product: Fedora
Classification: Fedora
Component: grubby
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-01 08:42 UTC by Elbin Pallimalil
Modified: 2012-05-10 01:01 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
: 820454 (view as bug list)
Environment:
Last Closed: 2012-04-09 02:58:43 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
/etc/default/grub (339 bytes, text/plain)
2012-04-01 08:47 UTC, Elbin Pallimalil 		no flags Details
/boot/grub2/grub.cfg (before) (2.32 KB, text/plain)
2012-04-17 18:53 UTC, Elbin Pallimalil 		no flags Details
/boot/grub2/grub.cfg (after) (2.95 KB, text/plain)
2012-04-17 18:54 UTC, Elbin Pallimalil 		no flags Details
View All

Description Elbin Pallimalil 2012-04-01 08:42:53 UTC 
Description of problem:
I have the following entry in /etc/default/grub
GRUB_DEFAULT="Microsoft Windows XP Professional (on /dev/sda1)"
But when a new kernel is installed via yum this new kernel is made the default.



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


How reproducible:
Always

Steps to Reproduce:
1. Set GRUB_DEFAULT to some particular kernel or other entry
2. Install another kernel via yum
  
Actual results:
The new installed kernel is made the default in Grub

Expected results:
The default boot option should be what was set in GRUB_DEFAULT


Additional info:
Comment 1 Elbin Pallimalil 2012-04-01 08:47:16 UTC 
Created attachment 574294 [details]
/etc/default/grub
Comment 2 Elbin Pallimalil 2012-04-09 02:58:43 UTC 

*** This bug has been marked as a duplicate of bug 742720 ***
Comment 3 Mads Kiilerich 2012-04-17 10:15:46 UTC 
If you say this is a duplicate then so be it. I can imagine other reasons why you could get the behaviour you describe, but without a before-and-after grub.cfg we can't tell.
Comment 4 Elbin Pallimalil 2012-04-17 18:53:16 UTC 
Created attachment 578125 [details]
/boot/grub2/grub.cfg (before)

Before adding a new kernel
Comment 5 Elbin Pallimalil 2012-04-17 18:54:23 UTC 
Created attachment 578130 [details]
/boot/grub2/grub.cfg (after)
Comment 6 Elbin Pallimalil 2012-04-17 18:56:26 UTC 
Added before and after grub.cfg so that you can verify.
Comment 7 Mads Kiilerich 2012-05-10 01:01:19 UTC 
Yes, in this case the problem is that whitespace is removed. The 'right' boot entry can thus not be found and grub will pick the first one it finds - which will be the new kernel.
Note You need to log in before you can comment on or make changes to this bug.