Bug 597497 - Anaconda stops upgrade F12 -> F13 with 'unhandled exception'
Summary: Anaconda stops upgrade F12 -> F13 with 'unhandled exception'
Status: CLOSED DUPLICATE of bug 577260
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-29 08:02 UTC by Klaus-Peter Schrage
Modified: 2010-05-29 11:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-29 11:27:39 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
anaconda traceback (217.21 KB, text/plain)
2010-05-29 08:02 UTC, Klaus-Peter Schrage
no flags Details

Description Klaus-Peter Schrage 2010-05-29 08:02:26 UTC
Created attachment 417822 [details]
anaconda traceback

Description of problem:
Trying to upgrade to the latest version of Fedora (like done many times before) , the system installer stops after I have chosen the the system to upgrade.

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

How reproducible:
always on my system

Steps to Reproduce:
1. Boot from Fedora DVD (as well as from boot cd pointing to iso on hard disk)
2. Choose 'Upgrade an existing system'
3. Point installer to 'Fedora 12 (installed on /dev/sda5)'
Actual results:
'An unhandled exception has occurred. ...' (see attached traceback)

Expected results:
Install process should continue

Additional info:
1. Hard disk layout:
/dev/sda3: boot (250 M)
/dev/sda5: root (50 G)

2. A fresh install of F13 to some unused space on the hard disk, using the same /boot partition, went flawelessly. 

3. The DVD has passed the mediacheck.

Comment 1 Chris Lumens 2010-05-29 11:27:39 UTC

*** This bug has been marked as a duplicate of bug 577260 ***

Note You need to log in before you can comment on or make changes to this bug.