Description of problem:
If there's a second hard drive installed in our desktop systems as we
install them, then we cannot install RH Desktop. We must disconnect
the drive to continue. This appears to be a bug in the python
Version-Release number of selected component (if applicable):
RH Academic Desktop 3 Release 3
Steps to Reproduce:
1. Install two hard drives: one SCSI (primary), one IDE (secondary).
This second HD is not perfectly formatted. (I've attached the
scripts we used for format these drives.)
2. Start an install off a CD with a specific ks.cfg (I've attached it).
3. The system gripes about "disk improperly formatted". We ignore
this warning, as it is just a warning on our 32-bit systems.
4. We get a screen of python errors indicating that up2date has failed.
A large screen of python errors, which (since I can't cut-and-paste) I
won't transcribe here.
Should let us continue installing after the error, as our 32-bit
systems do. If we remove the hard drive and continue the install
I'll attach a copy of our ks.cfg and our scratch drives later.
Created attachment 109328 [details]
Our ks.cfg file
This is installed on the CD media, which starts an automatic install. Used for
single-step system installation.
Created attachment 109329 [details]
scratch disk creation script
We use this script to create the scratch drives. It's not bug-free, and
usually causes a warning on future RH installs; it's probably just an
off-by-one error on drive creation. Regardless, it shouldn't make the install
Please provide the exception you receive. You should be able to save it to a
floppy and provide it. Without it, it's pretty much impossible for me to say
what's going on.
I don't have floppy drives on these systems.
If you switch to tty2 when the exception occurs, you should be able to scp off
the exception (it's stored in /tmp/anacdump.txt)
Created attachment 113223 [details]
Requested copy of the error message
Sorry this took so long; we didn't have spare machines to attempt to reinstall.
The message was transcribed by hand.
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received the feedback we
requested, we will assume the problem was not reproduceable or has been fixed in
a later update for this product. If you have further information, feel free to
add to the report and reopen.