I run chef-client frequently (ever 2 minutes or so) on a REL Linux box and I stumbled
upon a " error because RHN has detected an abuse of service from this
system" (See
https://access.redhat.com/knowledge/solutions/8165 for complete Error
Message).
This happens in a simple package resource ('package "unzip" ').
It looks like the yum provider maintains a cache
(http://www.rubydoc.info/github/opscode/chef/master/Chef/Provider/Package/Yum/YumCache)
which is invalidated on every chef run and thus hits
the network.
Is there a way to avoid hitting the RHN every time? Checking if a package is
already installed should be a local operation.
My use case for frequent runs is continuous deployment. I guess I could implement a
semi push model by having the build server flip a flag and poll the flag with
"chef free" cron job,
that in turn starts chef-client; But I'd like to avoid this if possible.
Regards,
Martin
Archive powered by MHonArc 2.6.16.