From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
I'm doing a kickstart based installation on a Dell2650, using RHEL 3 U3.
The node contains a QLogic 2200 HBA, plus a single SCSI disk.
A dialog comes up with an unhandled python exception. The traceback
will be attached to this bug, as will the kickstart file.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install with attached kickstart file. crash occurs automatically
Actual Results: System crashes.
Expected Results: System should install properly.
Created attachment 107324 [details]
python error call stack
Created attachment 107325 [details]
The kickstart file used during the installation
Some sensitive information has been changed (nisdomain, comment text, and the
This was partly a case of having a misunderstanding of the hardware
situation on this machine. The local drive is seen as sda on this
machine, while the kickstart file was set up for sde.
I've lowered the severity, as there is an easy workaround (get the
drives listed correctly in the kickstart file). The bug is still
open, since this case should have been handled more gracefully than a
Kickstart's handling of errors is generally giving a traceback. Newer
code makes the errors be a little bit better, but there's still not a
good unified way of presenting them more reliably to a user. There's
another RFE open about overall improvements of kickstart's error handling.