Bug 816701

Summary: Anaconda should not default to gpt on BIOS systems
Product: [Fedora] Fedora Reporter: Matthew Garrett <mjg>
Component: anacondaAssignee: Brian Lane <bcl>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: anaconda-maint-list, awilliam, bcl, g.kaviyarasu, jfeeney, jonathan, mads, mishu, paulcarroty, robatino, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: RejectedBlocker
Fixed In Version: anaconda-17.24-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-30 16:04:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matthew Garrett 2012-04-26 18:01:07 UTC 
We already blacklist Lenovos because this breaks them - it seems that it breaks some Dells too (http://lists.us.dell.com/pipermail/linux-desktops/2012-April/003976.html). The boot flag workaround doesn't seem to be sufficient. Since we're unlikely to ever be sure that we've found the full set of broken machines, it's safer to revert back to using MBR on BIOS systems.
Comment 1 Brian Lane 2012-04-26 22:35:53 UTC 
We should also add an inst.gpt option to force using GPT for those that want it.
Comment 2 Adam Williamson 2012-05-03 17:22:07 UTC 
Discussed at 2012-05-03 blocker review meeting. We agreed this does not constitute a blocker, though it's a sensible change and will make the release: there's no clear evidence it breaks enough systems to constitute criteria breakage, and indeed if it were truly a blocker, we should be recalling Fedora 16...



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers