On 12/01/2010 04:04 PM, Trevor Hemsley wrote: > On 01/12/2010 14:53, Martijn Grendelman wrote: >> Hi Trevor, >>> More likely just adding >>> >>> usecacheonfailure = false >>> >>> to the [puppetd] stanza in /etc/puppet/puppet.conf will help. >> I am yet unfamiliar with that option, but just as a remark, there was >> really no 'failure' involved here, it was just that enhancements to my >> code weren't picked up, and Puppet was running an older incantation of my >> function. > > I have often made a 'simple' change to one of my manifests that results > in a syntax error. Without that option, puppet helpfully ignores the > error and presents the older version of the manifest to you resulting in > exactly the symptoms you are complaining about.
I don't believe this is accurate. On syntax error, the puppetmaster cannot compose a catalogue. Puppetd will per default use its cached catalogue then. This happens on the client node, the master is unaware of this. When running puppetd --test, nousecacheonfailure is implied. Again, settings that apply to puppetd are *not* going to have an impact on puppetmaster behaviour. The original problem sounds like a bug to me. Regards, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
