From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3)
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):
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
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, ...)
Created attachment 107275 [details]
You appear to have specified to place partitions on the disk sdc which
isn't present in your system.
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.
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.