Perhaps you could adjust one of the /etc/yum.conf parameters like metadata_expire down from its default of 1.5 hours or keepcache = false (not entirely sure that this one does what you want it to do). The metadata_expire one can be set at the repo level so you could set it only for your own repo.
On 18/11/2010 08:56, 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. > -- Trevor Hemsley Infrastructure Engineer ................................................. *C A L Y P S O * Brighton, UK OFFICE +44 (0) 1273 666 350 FAX +44 (0) 1273 666 351 ................................................. www.calypso.com This electronic-mail might contain confidential information intended only for the use by the entity named. If the reader of this message is not the intended recipient, the reader is hereby notified that any dissemination, distribution or copying is strictly prohibited. *P * /*/Please consider the environment before printing this e-mail /*/ -- 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.
