Bug 549110 - Preupgrade "exception occurred"
Summary: Preupgrade "exception occurred"
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-20 13:17 UTC by Graham White
Modified: 2014-01-21 23:12 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-12-21 14:11:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Preupgrade install info and stack trace. (282.40 KB, text/plain)
2009-12-20 13:17 UTC, Graham White
no flags Details

Description Graham White 2009-12-20 13:17:46 UTC
Created attachment 379468 [details]
Preupgrade install info and stack trace.

Description of problem:
Towards the end of the preupgrade process going from F11 to F12 a Python exception occurred just after the "installing bootloader" part of the installation.

Hardware:
AMD Athlon64 i386 basearch machine running F11.
All partitions on a hardware dm-raid device.

Version-Release number of selected component (if applicable):
I believe I was using preupgrade-1.1.3-1.fc11.noarch

How reproducible:
Install F11, run preupgrade to F12.

Actual results:
Preupgrade failure with "exception occurred".  I was offered the opportunity to save the bug report, which I did by SCP to another machine.  The installer then tried to exit but failed to do so, a blank screen remained showing only the mouse cursor with animated "work in progress" type blue dots around it in circles.

Expected results:
Full and safe upgrade to F12.

Additional info:
Preupgrade output and python stack trace attached.

Comment 1 Radek Vykydal 2009-12-21 14:11:36 UTC
This bug should be fixed in rawhide/F13 (anaconda-13.7-1) with commit 558abca4d3f6740eadba96ead716839440112759 which consolidates handling of grub target device names obtained in UI and in /etc/sysconfig/grub of upgraded system. The bug concerns particularly grub installed in mbr of dmraid device where "mapper/" part of its path was not removed after reading it from the config file.

Thanks for the bug report.


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