Bug 134429 - installer stack trace during fc3t2 upgrade
Summary: installer stack trace during fc3t2 upgrade
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-02 11:06 UTC by Han-Wen Nienhuys
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-11-04 14:17:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Han-Wen Nienhuys 2004-10-02 11:06:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Gecko/20040809

Description of problem:



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


How reproducible:
Didn't try

Steps to Reproduce:
Hi,

while installing fc3t2 on a system that already had a semi-finished 
FC3t2 install (cd2 was corrupted), I chose

- upgrade existing system

at some point, the installer crashed, giving a stacktrace 

  /usr/bin/anaconda line 1162
  intf.run(id, ... 

when I pressed the debug button, I got a stacktrace which said
(halfway throuhg)

  OSError,  no such file, /mnt/sysimage/dev/hda2

(hda2 was my / partition; this makes it a quaint error message, since
/mnt/sysimage/dev/hda2 is only available after mounting hda2)

This happened while using the Rescue disc to upgrade (using FTP as
install medium.) I also got a crash when trying to upgrade with  the
regular install CD, and I think it was the same one. 

Finally, I did a fresh install.

I'm sorry that my report is rather sketchy. Hope this helps anyway.
 


Additional info:

Comment 1 Jeremy Katz 2004-10-04 13:24:59 UTC
Can you please provide the complete stack trace?  It's very hard for
me to figure out what's going on with only tiny little bits of it.

Comment 2 Jeremy Katz 2004-11-04 14:17:15 UTC
Closing due to inactivity.  Please reopen if you have further information to add
to this report.


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