Bug 138700 - anaconda exception: "list index out of range" during custom install
anaconda exception: "list index out of range" during custom install
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
  Show dependency treegraph
Reported: 2004-11-10 14:34 EST by Bruno Hertz
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-10 21:53:55 EST
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 floppy save (490.83 KB, text/plain)
2004-11-10 14:37 EST, Bruno Hertz
no flags Details

  None (edit)
Description Bruno Hertz 2004-11-10 14:34:12 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0

Description of problem:
Anaconda install bails out of custom install with exception/traceback
on P4. Reproducable with graphic or text install, i.e. installation is
not possible. Customization basically consists of selecting a target
root partition /dev/hda6, disabling firewall and custom package
selection. Floppy save available under above URL.

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

How reproducible:

Steps to Reproduce:
1. Custom install on my i686 system with designated root partition
/dev/hda6 and custom package selection.

Additional info:
Comment 1 Bruno Hertz 2004-11-10 14:37:19 EST
Created attachment 106434 [details]
anaconda traceback floppy save
Comment 2 Bruno Hertz 2004-11-10 17:04:09 EST
Please put this on hold: I now performed the media test which I used
to skip and it failed. I guess that maybe the source of failure, I'll
fix this and keep you posted.
Comment 3 Bruno Hertz 2004-11-10 21:53:55 EST
OK, sorry for the trouble. Error was due to faulty media, hence no bug.

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