Christopher Dale wrote:
> I don't think we ship any stock snippets that require
variable
> definitions that aren't sourced from settings. Can you think of some?
> While I like the idea of being able to list what variables a kickstart
> uses, I am not sure that is so easily extracted from Cheetah... in fact,
> I'm pretty sure that is impossible to do cleanly.
No, have created some templates for multipathing, xen bridging and
host file generation for the private IPs for various clusters. Over
time, I would make small mods to support a new use case, but did not
go back and update the other profiles, subprofiles and systems that
used them. So, when I would go to use these, I would either get a
cheetah error from the getks script or just a ks that wasn't right.
Being able to easily check whether or not everything get defined would
be useful. My adaption to this is that I ensure that the element has
a default value that alerts me to the fact that I have ommitted
assigning a legit value. So, I will continue in that way, but would
be happy to entertain anyone elses approach to dealing with self
inflicted errors.
By "stock" I mean ones that ship with Cobbler, non-modified by anyone
else... those should not need any extra --ksmeta variables applied.
I was going to say does just running "cobbler validateks" work for you
in that case, but it looks like it currently skips profiles and systems
that use a kickstart template it has already checked. This is a
leftover from old behavior when these things weren't dynamic and
/really/ needs to change.
Either way, that /should/ point out errors in kickstart templates.
Anyway, validateks, once tweaked a bit, is the answer.