Michael DeHaan wrote:
The XML file works fine when I grab it from another server so I know the file is okay and being parsed fine. It just can't get the file from where it is supposed to be on Cobbler, so I am pretty sure it is permissions on the Cobbler side.
I don't think you understand.
If a parameter to --kickstart in cobbler is on the local filesystem, it's treated as a template.
If you add a --kickstart=http://, it's used verbatim.
I'm pretty sure it's /not/ permissions on the cobbler side.
Hi Michael - thanks for the help.
I still don't get it though. I created a new kickstart file and modifed the Suse profile to include /var/lib/cobbler/kickstarts/Suse11Yast as the kickstart. You can view the rendered ks and it is fine. Did a Cobbler sync.
Then you boot up and select Suse from the PXE menu and the autoyast= argument is still here and the ks= argument is not. Plus, even if it were, I think the Suse kernel is going to expect to get an autoyast and not ks argument
(Maybe I just need to delete the distro and recreate it with with --kickstart option and not the --breed=suse option)
Also, where DOES the autoyast argument get stored though? I could very easily just change it to point to where I have the file and it will work fine - for example, I can just hit table on the boot menu and modify the autoyast=http://whatever.com/my-autoyast and it works perfectly, no problem - except I can't seem to find where the autoyast kernel argument is saved so you have to manually change it each time.
I will test this more next week - thanks again for you help. I would like to be able to use these autoyast files to automate our Suse installs, so I appreciate the tips.
Cheers, Pete