Upgrading to 2.6.8 and applying the patch worked for me! Thank you!
On 20 Jun., 19:13, Daniel Pittman <dan...@puppetlabs.com> wrote: > On Mon, Jun 20, 2011 at 05:11, markus <markus.fenste...@googlemail.com> wrote: > > I've got a MCollective Setup (1.2.0) with Puppet (2.6.4), an > > provision agent and an external node configuration script that fetches > > configurations from a database. > > > Sometimes it happens, that puppet caches the configuration of the > > server and doesn't notice a change in the configuration. > > Odds are, no: I suspect that if you run the agent a second time you > will have things work; 2.6.4 had a nasty bug that would cause the > master to ignore changes to your manifests the first time you ran it > after the file changed (and, theoretically, but never observed, more > than once.) > > If you find that is the case, upgrading to 2.6.9 will fix things up, > or you can dig up the patch set I posted to the list earlier; it > should apply cleanly to 2.6.4 as a point-fix to get things working. > (You only need to upgrade the *master* for this to be fixed; a 2.6.4 > client will work fine.) > > Daniel > -- > ⎋ Puppet Labs Developer –http://puppetlabs.com > ✉ Daniel Pittman <dan...@puppetlabs.com> > ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 > ♲ Made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.