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
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 Nov 2010, at 12:56 AM, Daniel Maher wrote:
> 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 aw
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 qu
