Red Hat Bugzilla – Bug 46370
traceback during kickstart installs
Last modified: 2007-04-18 12:34:16 EDT
Description of Problem:
--Was not able to complete any kickstart installs.
--I used the anaconda-ks.cfg file that was generated
during an install on the same system that I was
attempting the kickstart install on.
--The only modification to anaconda-ks.cfg was for the hostname
and the install source:
nfs --server porkchop --dir /mnt/redhat/test/qa0627.3/i386
url --url ftp://porkchop.redhat.com/mnt/test/qa0627.3/i386
--Tried w/ NFS, FTP, and HTTP install sources.
Traceback occurs just after running anaconda:
File /usr/bin/anaconda, line 528, in ?
File /usr/lib/anaconda/kickstart.py, line 708, in setInstallData
self.read kickstart(id, self.file)
File /usr/lib/anaconda/kickstart.py, line 475, in readKickstart
args = isys_parseArgv(n)
File /usr/lib/anaconda/kickstart.py, line 277, in parseArgv
ValueError = bad string for parsing
File /usr/bin/anaconda, line 155, in ?
from kickstart import kickstart
ImportError: No module named kickstart
Please retry with any tree after qa0628.0.
TUI and GUI kickstart installs completed successfully w/
the 0629.0 tree.
"reboot" flag did not reboot computer.
The reboot issue is a known one.
a similar (but not identical) traceback is occuring in qa0711.4 ... this is a
sporadic problem as kickstart worked in qa0709.3 test tree ... reopening ...
This defect considered MUST-FIX for Fairfax gold-release.
This is because kickstart.py wasn't being pulled into the ftp/http images. msw
committed a fix for this on Friday
I noticed the same problem with FTP installs on beta2. Using updates disk fixed