On Nov 18, 2010, at 12:56 AM, Daniel Maher wrote: > Hello, > > I have run into problems in the past where a package has been added to our > yum repository, and a (new) class has been pushed to install that package, > but puppet fails because the yum db on the target machine is too stale, and > thus isn't aware of the existence of the new package. > > My question is this : what have other Puppet admins done in order to ensure > that a target machine has the freshest local dbcache before attempting to > install a package ? > > Thank you.
What ever you do, you will probably want to make sure you have a caching proxy server (or an on site mirror) between your clients and the yum server. -- 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.
