Bug 369441 - Partitioning failed due to IndexError: list index out of range using a kickstart file
Partitioning failed due to IndexError: list index out of range using a kickst...
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-11-07 04:09 EST by Jonas Weismueller
Modified: 2008-08-06 16:26 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-08-06 16:26:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jonas Weismueller 2007-11-07 04:09:11 EST
Description of problem:
An exception occurred during kickstart installation.

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

How reproducible:
These are the related lines of my kickstart file:

bootloader --location=mbr --driveorder=hda --append="selinux=0 apm=off panic=30"
# Clear the Master Boot Record
# Partition clearing information
clearpart --all --initlabel 
# Disk partitioning information
part /boot --asprimary --fstype="ext3" --size=100 --bytes-per-inode=4096
part swap --asprimary --fstype="swap" --recommended --bytes-per-inode=4096
part / --asprimary --fstype="ext3" --grow --size=1 --bytes-per-inode=4096

Steps to Reproduce:
1. Setup a cobbler server with Fedora 8 Test 3
2. Create a kickstart file having the configuration for partitioning like above.
Actual results:
File "/usr/lib/anaconda/text.py", line 545, in run (step, instance) =
File "/usr/bin/anaconda", line 952, in <module> anaconda.intf.run(anaconda)
IndexError: list index out of range

Expected results:

Additional info:
Comment 1 Chris Lumens 2007-11-07 09:40:00 EST
Please attach the complete traceback to this bug report.

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