Catalog changes not picked up immediately

[Giovanni Bordello]

Hi there,

when I do changes to my Puppet catalog files it takes some time between
these changes are picked up by the clients, even in manual mode. That
makes testing with "puppetd --test" quite hard because it can often be
up to a couple of minutes for the changes be served out.

Can I somehow flush the puppet master cache or from the client force the
reload of actual current files to speed things up?

Thanks!

Michal

[Felix Frank]

Hi,

we had similar problems until we spread out everything into modules?

Are you already relying on modules? Are you using Passenger?

Regards,
Felix

[hai wu]

We have same problem, using modules for all and using passenger. Have
to run puppet agent -tv at least 2 times if need to test a change
right away ..

> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

--
Sent from my mobile device

[Martin Alfke]

On 04/05/2011 04:10 PM, hai wu wrote:
> We have same problem, using modules for all and using passenger. Have
> to run puppet agent -tv at least 2 times if need to test a change
> right away ..

I can confirm this behavior with puppet 2.6.2, using modules and running
on passenger on RHEL5 and on Debian Squeeze.

[Adam Winberg]

On 04/05/2011 04:10 PM, hai wu wrote:
> We have same problem, using modules for all and using passenger. Have
> to run puppet agent -tv at least 2 times if need to test a change
> right away ..

I can confirm this behavior with puppet 2.6.2, using modules and running
on passenger on RHEL5 and on Debian Squeeze.

Sound like http://projects.puppetlabs.com/issues/5318, we have had this issue quite some time.