[et-mgmt-tools] network configuration - Cobbler add versus ksmeta

[Michael DeHaan]

Tom Brown wrote:
>
> Hi - i am experimenting on how to pass network configuration to 
> cobbler - i do it either by adding most information directly to the 
> cobbler add command or passing it within the --ksmeta. Below are 2 
> examples, the first is populated with information mainly from within 
> ksmeta, only the name, mac and profile to use is passed to cobbler add 
> the rest is within ksmeta. This installs fine. The second example is 
> where only the nameserver info is passed using ksmeta everything else 
> comes from the cobbler add directly. The issue is the second example 
> boots, gets an IP but then fails trying to retrieve the netstg2.img.
>

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.

--Michael