Bug 140488 - Anaconda crashes on kickstart GUI and Text during partitioning
Summary: Anaconda crashes on kickstart GUI and Text during partitioning
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda
Version: 3.0
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2004-11-23 01:25 UTC by John Van Boxtel
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2004-12-01 19:03:58 UTC

Attachments (Terms of Use)
Crash Dump (44.90 KB, text/plain)
2004-11-23 01:32 UTC, John Van Boxtel
no flags Details

Description John Van Boxtel 2004-11-23 01:25:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3)
Gecko/20041001 Firefox/0.10.1

Description of problem:
While performing a kickstart installation, on a HP/Compaq DL380 G3
with attached storage shelf, Anaconda will crash with an execption
error.  If I do not specify the drive in the kickstart config, the
installation works fine.  If I specify the drive I want the partitions
created on this is when it crashes.

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

How reproducible:

Steps to Reproduce:
1.Setup an NFS installation server, per documentation
2.Create a kickstart disk specifing a disk under the partition creation
3.Boot the kickstart (I used a floppy)
4.Installation will crash when it goes to partition the drive

Actual Results:  Anaconda crashed with an exception error in "autopart"

Expected Results:  The drive should have been partitioned, and
installation continue

Additional info:

Strangly, it tells me that the NFS server directory could not be
mounted, then I hit OK, and enter (without changing values) and it
works.  This also shows up in the logs (doNFSinstall, NFS mount
attempt, doNFSinstall, mounts, ...)

Comment 1 John Van Boxtel 2004-11-23 01:32:42 UTC
Created attachment 107275 [details]
Crash Dump

Comment 2 Jeremy Katz 2004-11-23 03:44:45 UTC
You appear to have specified to place partitions on the disk sdc which
isn't present in your system.

Comment 3 John Van Boxtel 2004-11-23 16:42:47 UTC
Shouldn't I get an error such as "no device found sdc" instead of a
crash?  I will try using a different device, which probably will fix
it, but I still think that the installer should not crash, but exit
with an error.

Comment 4 Jeremy Katz 2004-12-01 19:03:58 UTC
Kickstart doesn't always report invalid inputs in the most user friendly of
ways.  Changes for that are listed as an RFE filed elsewhere.

RHEL4 will at least do slightly better about giving more understandable
tracebacks and then hopefully for RHEL5, we'll have things so that the errors
get reported up in an even more user-friendly fashion.

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