Excerpts from Lydia Heck's message of Tue May 18 13:59:28 -0400 2010:
Even so cblr is set as an alias, should I not expect to have
m2067 (the system created using cobbler) sitting in the directory
structure at /var/www/cobbler/svc/op/ks/system/m2067 which is referenced in
ks=http://172.17.11.1/cblr/svc/op/ks/system/m2067 ?
I believe it did this at one point, but then we moved to mod_python
(and now we are moving to mod_wsgi) to do that templating on the fly.
You will find the kickstart template that generates into the kickstart
in /var/lib/cobbler/kickstarts. Which template is used shuld be set
in the cordelia profile.
Cobbler does this so it can dynamically generate the template at
request time. This leads to cobbler having the ability to do some
very neat things. The templating generation tends to be pretty fast
as well.
I used
cobbler system add --name=m2067 etc ....
But the file is not in that place.
Also: I expected /etc/dhcpd.conf to have been modified to reflect
the adding of the system. But there have been no changes.
Have you run 'cobbler sync' after adding the system? The dhcp
template is generated at sync time due to the amount of times it takes
to restart the dhcp server.
--
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME