Puppet users - Apr 2011 - Catalog changes not picked up immediately

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

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On 04/05/2011 02:10 AM, Giovanni Bordello wrote:
> 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?
Hi,

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

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

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-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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 ..

On 4/5/11, Felix Frank <felix.frank@alumni.tu-berlin.de>
wrote:
> On 04/05/2011 02:10 AM, Giovanni Bordello wrote:
>> 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?
>
> Hi,
>
> we had similar problems until we spread out everything into modules?
>
> Are you already relying on modules? Are you using Passenger?
>
> 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-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
-- 
Sent from my mobile device

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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.
> 
> On 4/5/11, Felix Frank <felix.frank@alumni.tu-berlin.de> wrote:
>> On 04/05/2011 02:10 AM, Giovanni Bordello wrote:
>>> 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?
>>
>> Hi,
>>
>> we had similar problems until we spread out everything into modules?
>>
>> Are you already relying on modules? Are you using Passenger?
>>
>> 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-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>>
> 
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

> 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.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.