I found similar behavior, but only on Ubuntu and when gid is set to string values. I filed this bug regarding the issue -- https://tickets.opscode.com/browse/CHEF-4440Perhaps this is related?George Miranda — Partner Engineering
512.481.2876 – " style="color:rgb(105,117,130)" target="_blank"> – Linkedin Twitter
CHEF
TM
On Wed, Jul 16, 2014 at 5:14 PM, < " target="_blank"> > wrote:This is something that I have noticed for a while but has only started to
matter now that we are gathering metrics around the number of resources that
get updated during each chef run.
We are getting what we deem false metrics because we use Chef to manage
/etc/group and the client seems to update each group resource on every run even
if no modifications are really needed
Take for example the following simple resource
group "foobarbaz" do
action :create
members "user1,user2"
end
Everytime I run chef-client this resource is marked as updated. It seems that
the group provider does not bother to check existing group membership, it just
modifies the group to be what it is "supposed" to be.
While in the end this leaves /etc/group in the state that I require - it does
skew our metrics in that we always have resources to be updated on systems
where there really is not any update.
Is there anyway to get the Group provider to only update groups when they need
to be?
Archive powered by MHonArc 2.6.16.