Tom Brown wrote:
You should just use the variables that are part of the interface
since they are already made available for that purpose. As for why
that is not working for you, a good place to start looking is at
/var/www/cobbler/profiles/$name and /var/www/cobbler/systems/$name
for a file that shows you all the variables expanded, just like they
would be available in your templates.
Then make sure you are using those same variables in your templates.
Also look at the rendered kickstarts in
/var/www/cobbler/kickstarts/$name and
/var/www/cobbler/kickstarts_sys/$name and compare those to the
templates you are using.
Make sure that they look like you want in both cases.
By looking at what variables you have available to use, and seeing
how the kickstarts are actually rendered, it will become much more
clear what is going on.
You shouldn't have to do an install to debug the kickstart.
Try "cobbler validateks" first, which will do a quick scan of your
rendered kickstarts to see if they have the right syntax.
After that, look at them manually and compare the two, to understand
what cobbler is generating from the templates.
thanks - below is what the rendered kix looks like for that system
from the /var/www/cobbler/systems/<systemname>
I'm not seeing it in the email or attached.
to me that looks correct as in the template the variables used are
network --bootproto=static --device=eth0 --onboot=on --ip=$ip_address
--netmask=$netmask --gateway=$gateway --nameserver=$nameserver
--hostname=$hostname
and the rendered kix looks like the below - is there anything else i
can check ?
Same here.
If a rendered kickstart looks normal to you then it's just a kickstart
problem (outside of Cobbler), where you could possibly ask
kickstart-list@xxxxxxxxxx
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
