Bug 369441 - Partitioning failed due to IndexError: list index out of range using a kickstart file
Summary: Partitioning failed due to IndexError: list index out of range using a kickst...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 8
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-07 09:09 UTC by Jonas Weismueller
Modified: 2008-08-06 20:26 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-08-06 20:26:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jonas Weismueller 2007-11-07 09:09:11 UTC
Description of problem:
An exception occurred during kickstart installation.

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

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
zerombr
# 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.
3.
  
Actual results:
File "/usr/lib/anaconda/text.py", line 545, in run (step, instance) =
anaconda.dispatch.currentStep()
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 14:40:00 UTC
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.