Hi, I was wondering what is the correct way to make sure changes in the manifest files are applied to the relevant nodes. When using puppet -tv everything works as expected, but when running puppetd as a daemon, caching is playing games with me. Apparently changes are not applied until the cache expires? If I make changes to the manifests, what is the preferred way to make sure these changes will happen on the clients. Restart the master? Delete the cached configs? Also, if I don''t do this, how long will it take until the cached configuration expires? Best regards, Dieter -- 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.
DieterVDW
2010-Mar-20 02:37 UTC
[Puppet Users] Re: Cache expiry time? Detect manifest errors?
Hmm currently the configuration does reload automatically. Not sure why it didn''t work earlier. It would be nice to have some more info about the caching mechanism though. Also, I''ve noticed that there aren''t really any warnings if you mess up the manifests. I get a few error lines in my puppetmasterd.log (--logdest), but that''s it. I''ve got reporting with tagmail configured on the client, but the clients just keep saying: "Puppet (info): Applying configuration version ''1269050245''" without complaining. I am using --no-usecacheonfailure on the puppet client, but doesn''t seem to do anything? I guess it''s the server sending the previous working config? What''s the best way to detect and signal there is an error in the manifests? It would be nice to know if you''ve made a mistake and the changes you''re expecting won happen. Thanks! D On Mar 20, 1:39 am, DieterVDW <dieter...@gmail.com> wrote:> Hi, > > I was wondering what is the correct way to make sure changes in the > manifest files are applied to the relevant nodes. > > When using puppet -tv everything works as expected, but when running > puppetd as a daemon, caching is playing games with me. Apparently > changes are not applied until the cache expires? > > If I make changes to the manifests, what is the preferred way to make > sure these changes will happen on the clients. Restart the master? > Delete the cached configs? > Also, if I don''t do this, how long will it take until the cached > configuration expires? > > Best regards, > > Dieter-- 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.