[root@inCore ~]# cobbler sync
# *** ERROR *** # # There is a templating error preventing this file from rendering correctly.
# # This is most likely not due to a bug in Cobbler and is something you can fix. # # Look at the message below to see what things are causing problems. # # (1) Does the template file reference a $variable that is not defined? # (2) is there a formatting error in a Cheetah directive? # (3) Should dollar signs ($) be escaped that are not being escaped? # # Try fixing the problem and then investigate to see if this message goes # away or changes. # # # cannot find 'system' while searching for 'iface.system.netboot_enabled' # File "/usr/lib/python2.5/site-packages/cobbler/templar.py", line 115, in render # data_out = str(t) # # File "/usr/lib64/python2.5/site-packages/Cheetah/Template.py", line 982, in __str__ # def __str__(self): return getattr(self, mainMethName)() # # File "cheetah_DynamicallyCompiledCheetahTemplate_1238622594_65_47014.py", line 265, in respond #
Error templating file: /etc/dhcpd.conf
My dhcpd.template file:
[root@inCore ~]# cat /etc/cobbler/dhcp.template # ****************************************************************** # Cobbler managed dhcpd.conf file # # generated from cobbler dhcp.conf template ($date) # Do NOT make changes to /etc/dhcpd.conf. Instead, make your changes # in /etc/cobbler/dhcp.template, as /etc/dhcpd.conf will be # overwritten. # # ******************************************************************
ddns-update-style interim;
allow booting; allow bootp; #if $omapi_enabled omapi-port $omapi_port; #end if
ignore client-updates; set vendorclass = option vendor-class-identifier;
subnet 192.168.10.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; range dynamic-bootp 192.168.10.100 192.168.10.254; filename "/pxelinux.0"; default-lease-time 21600; max-lease-time 43200; next-server $next_server; }
subnet 192.168.56.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; range dynamic-bootp 192.168.56.100 192.168.56.254; filename "/pxelinux.0"; default-lease-time 21600; max-lease-time 43200; next-server $next_server; }
subnet 192.168.122.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; range dynamic-bootp 192.168.122.100 192.168.122.254; filename "/pxelinux.0"; default-lease-time 21600; max-lease-time 43200; next-server $next_server; }
#for dhcp_tag in $dhcp_tags.keys(): ## group could be subnet if your dhcp tags line up with your subnets ## or really any valid dhcpd.conf construct ... if you only use the ## default dhcp tag in cobbler, the group block can be deleted for a ## flat configuration # group for Cobbler DHCP tag: $dhcp_tag group { #for mac in $dhcp_tags[$dhcp_tag].keys(): #set iface = $dhcp_tags[$dhcp_tag][$mac] host $iface.name { hardware ethernet $mac; #if $iface.ip_address: fixed-address $iface.ip_address; #end if #if $iface.subnet: option subnet-mask $iface.subnet; #end if #if $iface.gateway: option routers $iface.gateway; #end if #if $iface.system.netboot_enabled: filename "$iface.filename"; ## Cobbler defaults to $next_server, but some users ## like to use $iface.system.server for proxied setups next-server $next_server; ## next-server $iface.system.server; #end if } #end for } #end for
Christopher Dale wrote:
[root@inCore ~]# cobbler sync
# *** ERROR *** # # There is a templating error preventing this file from rendering correctly.
When doing RPM upgrades, always watch for .rpmnew files.
In this case the templates have changed ( a consequence of performance upgrades) so you will need to look at /etc/cobbler/dhcp.template.rpmnew and make the appropriate changes to your /etc/cobbler/dhcp.template.
Then run cobbler sync and you should be good to go.
--Michael
On Thu, Apr 2, 2009 at 7:52 AM, Michael DeHaan mdehaan@redhat.com wrote:
Christopher Dale wrote:
[root@inCore ~]# cobbler sync
# *** ERROR *** # # There is a templating error preventing this file from rendering correctly.
When doing RPM upgrades, always watch for .rpmnew files.
Obviously we should test new versions on our own, but do you mind mentioning when you break things like this in the release announcement or at least link to it please? In some setups the dhcp templates need to be heavily customized and it takes a fair amount of work to migrate over. Just a suggestion from the peanut gallery.
Jeff Schroeder wrote:
On Thu, Apr 2, 2009 at 7:52 AM, Michael DeHaan mdehaan@redhat.com wrote:
Christopher Dale wrote:
[root@inCore ~]# cobbler sync
# *** ERROR *** # # There is a templating error preventing this file from rendering correctly.
When doing RPM upgrades, always watch for .rpmnew files.
Obviously we should test new versions on our own, but do you mind mentioning when you break things like this in the release announcement or at least link to it please? In some setups the dhcp templates need to be heavily customized and it takes a fair amount of work to migrate over. Just a suggestion from the peanut gallery.
Didn't realize it when I released it. Generally this is something we want to mention.
--Michael
How bout my bug, any ideas? :-)
On Thu, Apr 2, 2009 at 12:42 PM, Michael DeHaan mdehaan@redhat.com wrote:
Jeff Schroeder wrote:
On Thu, Apr 2, 2009 at 7:52 AM, Michael DeHaan mdehaan@redhat.com
wrote:
Christopher Dale wrote:
[root@inCore ~]# cobbler sync
# *** ERROR *** # # There is a templating error preventing this file from rendering correctly.
When doing RPM upgrades, always watch for .rpmnew files.
Obviously we should test new versions on our own, but do you mind mentioning when you break things like this in the release announcement or at least link to it please? In some setups the dhcp templates need to be heavily customized and it takes a fair amount of work to migrate over. Just a suggestion from the peanut gallery.
Didn't realize it when I released it. Generally this is something we want to mention.
--Michael _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
I can put one in if you would like.
On Thu, Apr 2, 2009 at 2:25 PM, Michael DeHaan mdehaan@redhat.com wrote:
Christopher Johnston wrote:
How bout my bug, any ideas? :-)
Which Trac ticket # ?
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Christopher Johnston wrote:
I can put one in if you would like.
On Thu, Apr 2, 2009 at 2:25 PM, Michael DeHaan <mdehaan@redhat.com mailto:mdehaan@redhat.com> wrote:
Christopher Johnston wrote: > How bout my bug, any ideas? :-) Which Trac ticket # ? _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org <mailto:cobbler@lists.fedorahosted.org> https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Yes, this is the easiest way to reference and track bugs. I otherwise don't know what "my bug" is :)
--Michael
cobbler@lists.fedorahosted.org