Bug 756119

Summary:	After a kernel update Grub2 don't write grub.cfg correctly
Product:	[Fedora] Fedora	Reporter:	Paolo Leoni <ulixes84>
Component:	grub2	Assignee:	Peter Jones <pjones>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	16	CC:	dennis, mads, pjones
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-22 20:02:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Paolo Leoni 2011-11-22 17:58:51 UTC

Description of problem:
After a kernel update, /boot/grub2/grub.cfg it's modified in a wrong way on some parameters.

- First issue (minor): "echo" parameter isn't modified with correct version of kernel that is booting. So, kernel that is starting is ok, but screen will display a differently version, normally the old version.

- Second issue (major): "set default" parameter is slightly modified, so the entry previously inserted won't be recognized by grub2.

This cause manual editing of grub2 configurations after every kernel update.

e.g:
Before update:

....

set default="Windows 7 (loader) (on /dev/sda1)"

....

After update:

....

set default="Windows7 (loader) (on /dev/sda1)"

...

(note that between "windows" and "7" now miss a space)   

Version-Release number of selected component (if applicable):
grub2.x86_64                     1:1.99-12.fc16

How reproducible:


Steps to Reproduce:
1. Setup a dualboot with a different OS as default grub2 boot  
2. update kernel 
3. now default OS is fedora
  
Actual results:
grub2 don't write correctly grub.cfg

Expected results:
grub2 write correctly the configuration file.

Additional info:

Comment 1 Mads Kiilerich 2011-11-22 20:02:17 UTC

These issues have already been reported - and they are all issues in grubby.

With several different issues mentioned in one report it is not possible to mark this as a duplicate.