Bug 769084

Summary:	preupgrade to F16 overwrites mbr when fedora was never in control of the mbr.
Product:	[Fedora] Fedora	Reporter:	Kyle <mr_hankeys8rd>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	anaconda-maint-list, dennis, g.kaviyarasu, jonathan, mads, pjones, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-19 20:46:36 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 Kyle 2011-12-19 21:24:09 UTC

Description of problem: Fedora-grub was originally installed to a partition, leaving the mbr untouched. Previous upgrades to fedora only upgraded  (fedora)/boot/grub/, allowing the mbr to be maintained by the admin. With the upgrade from F14 to F16, grub2 was installed to the mbr, requiring a rewrite of the mbr to restore normal functionality.

As a result, when fedora is selected as the operating system to boot, the only option is the preupgrade to verne, or other (windows).

Version-Release number of selected component (if applicable): F14(grub legacy) > F16(grub2)



  
Actual results: grub2 installed to mbr.


Expected results: Fedora should operate within it's originally installed domain, in this case grub2 should have been installed to the partition boot record.

Comment 1 Mads Kiilerich 2012-04-16 22:48:35 UTC

Anaconda told grub2 what to do.

I am sure anaconda asked and gave you the option of controlling where and if a new boot loader should be installed. It is possible that the default could have been chosen in a smarter way - I don't know.

Comment 2 Jesse Keating 2012-07-19 20:46:36 UTC

Upgrades present the user a choice of what to do with the boot loader.  We don't do anything automatically.