Bug 759296

Summary: Crash when upgrading from Fedora 15 to 16
Product: [Fedora] Fedora Reporter: neopium
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 16CC: anaconda-maint-list, awilliam, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-30 03:19:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Bug report none

Description neopium 2011-12-01 22:54:06 UTC
Created attachment 539420 [details]
Bug report

Description of problem:
I upgraded with preupgrade from F15 to F16.
When restarting with anaconda, everything went well until it cleaned the packages. Then it crashed (see report attached

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

How reproducible:
Each time I restart the computer, the message appears again

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Adam Williamson 2011-12-02 19:56:02 UTC
anaconda team, my read on this is that it's barfing because the user's existing install is on a GPT-labelled disk with no BIOS boot partition. This is, I think, because it's a Mac. So it's hitting the check for a BIOS boot partition, but the upgrade process either doesn't know to try and create one, or it can't because the disk's full.



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

Comment 2 Chris Lumens 2012-11-30 03:19:04 UTC
This should no longer be a problem with the new upgrade procedure in F18 (fedup), since we are not using anaconda and anaconda doesn't even know about upgrades anymore.  If you do continue to see this problem with a fresh install, please feel free to reopen this bug.  Thanks.