Ok... so I'm a thrill seeker.... I'm trying to modularize my %post section using
%include so I don't have to edit 6 different kickstart config files every time we update our image.
Looks good in theory (though the docs are pretty thin - took some experimenting to figure out that I needed to reference the include files through /mnt/source/...). But I'm running into a rather puzzling problem.
NFS based install. Boot parameters are:
ks=nfs:10.1.2.1:/export/kickstart/RedHat_7.3/kickstart/test.cfg initrd=initrd.img lang= devfs=nomount ramdisk_size=8192 text
This works fine until I move several lines out of the %post section of test.cfg into an include file (/export/kickstart/RedHat_7.3/kickstart/local) and then try to reference it from within the %post section as:
%include /mnt/source/kickstart/local
Pffft! Anaconda craps out with out much of a clue as to why:
Probing for mouse type: Generic - 3 Button Mouse (PS/2)
Traceback (innermost last):
File "/usr/bin/anaconda", line 602, in ?
instClass.setINstallData(id)
File "/usr/lib/anaconda/kickstart.py", line 889, in setInstallData
self.readKickstart(id,self.file)
File "/usr/lib/anaconda/kickstart.py", line 545, in readKickstart
where = self.readKickstart(id, ars[1], where=where)
File "/usr/lib/anaconda/kickstart.py", line 595, in readKickstart
script = script + n
NameError: script
install exited abnormally
sending termination signals....
(apologies if I typoed anything above - I had to enter it by hand from a second monitor)
If I comment out the %include line in test.cfg it runs fine. If I replace the
%include line with the contents of the included file, it runs fine. it only barfs when I reference the included file with %include.
I think I've covered all the obvious places where I could have screwed up, but no joy. So, before I start poking around the anaconda code (and I'm NOT a python guy - so that could be a little scary), anyone else see similar problems?
Cheers-
----
Eric D. Christensen
