Hi Scott,
Thanks for the help. It seems that using template_remote_kickstarts:
0 will maintain the requirement for not locally templating/serving a
remote kickstart if the kickstart path is remote.
What is the purpose of this flag if not designed to "trust" the
execution of remote templates? The description and current behavior
seems broken. I find it very useful to use source control on
kickstart files in combination with cobbler templating and serving
them up.
On Fri, May 20, 2011 at 4:56 PM, Scott Henson <shenson(a)redhat.com> wrote:
On Fri, 20 May 2011 16:14:00 -0500, Matthew Sellers
<matt(a)indigo.nu> wrote:
> Hi All,
>
> I have a problem with cobbler using externally sourced kickstart files
> that use template variables. It seems that pxegen.py refuses to use
> the template service if the kickstart file is externally sourced.
<snip>
> I have worked around this with a little patch on these lines but I
> wanted to see if this is a true bug. Ill submit a ticket and patch
> if appropriate.
It isn't a bug. It is more of a security feature. These scripts are
running python on your cobbler server.
I'm assuming that you are trying to run scripts from a centrally managed
place on multiple cobbler servers? If that is the case you might want to
check out replicate for maintaining one master version of cobbler's
config files and syncing them out to be used.
--
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME