I also faced with same problem and setting metadata_expire to 1 minute works for me. Schedule yum clean in puppet run is not good idea, because you always get at least one resource changed, and never will green nodes in puppet dashboard.
On Thursday, November 18, 2010 10:56:56 AM UTC+2, 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. > > -- > Daniel Maher <dma AT witbe DOT net> > "The Internet is completely over." -- Prince > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/69de2c88-9b5e-41c2-9c4f-3752b970ddbc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
