General discussion about Chef

[chef] Re: Re: Re: Re: Re: group resource always updated


Chronological Thread 
  • From: Mark Selby < >
  • To: " " < >
  • Subject: [chef] Re: Re: Re: Re: Re: group resource always updated
  • Date: Thu, 17 Jul 2014 11:08:00 -0700
I have also confirmed that this fixes the problem. What is the best way to communicate to the Chef Docs owner that it may be a good idea to update the official docs?


On Thu, Jul 17, 2014 at 9:08 AM, George Miranda < " target="_blank"> > wrote:
Confirmed.  Array gets the expected behavior.  Single comma separated string "works", but always updates every time.
On Thu, Jul 17, 2014 at 9:04 AM, Ranjib Dey < " target="_blank"> > wrote:
can you try specifying memebers as an array
group "foobarbaz" do
  members ['user1', 'user2']
end


On Thu, Jul 17, 2014 at 8:58 AM, Mark Selby < " target="_blank"> > wrote:
Here are the details of what I am seeing. Please let me know if you need anymore info. I can confirm that for me with the lastest chef client I am still seeing this behavior on Ubuntu.

(test) ~ 931# cat /etc/issue.net 
Ubuntu 12.04.4 LTS

(test) ~ 933# chef-client --version
Chef: 11.12.8

(test) ~ 923# grep user[0-9] /etc/passwd
user1:x:1023:1023::/home/user1:/bin/sh
user2:x:1024:1024::/home/user2:/bin/sh

(test) ~ 932# grep foobarbaz /etc/group
foobarbaz:x:1025:user1,user2

# client has a single recipe in the run list. The recipe is
group "foobarbaz" do
  members "user1,user2"
end

(test) ~ 934# chef-client          
Starting Chef Client, version 11.12.8
resolving cookbooks for run list: ["nbs_test::default"]
Synchronizing Cookbooks:
  - nbs_test
Compiling Cookbooks...
Converging 1 resources
Recipe: nbs_test::default
  * group[foobarbaz] action create
    - alter group group[foobarbaz]
    - replace group members with new list of members


Running handlers:
Running handlers complete

Chef Client finished, 1/1 resources updated in 3.549844354 seconds


# here is the debug outout of this recipe

Recipe: nbs_test::default
  * group[foobarbaz] action create[2014-07-17T15:52:47+00:00] INFO: Processing group[foobarbaz] action create (nbs_test::default line 1)
[2014-07-17T15:52:47+00:00] DEBUG: Platform ubuntu version 12.04 found
[2014-07-17T15:52:47+00:00] DEBUG: Executing groupmod foobarbaz
[2014-07-17T15:52:47+00:00] DEBUG: ---- Begin output of groupmod foobarbaz ----
[2014-07-17T15:52:47+00:00] DEBUG: STDOUT: 
[2014-07-17T15:52:47+00:00] DEBUG: STDERR: 
[2014-07-17T15:52:47+00:00] DEBUG: ---- End output of groupmod foobarbaz ----
[2014-07-17T15:52:47+00:00] DEBUG: Ran groupmod foobarbaz returned 0
[2014-07-17T15:52:47+00:00] DEBUG: group[foobarbaz] setting group members to: user1,user2
[2014-07-17T15:52:47+00:00] INFO: group[foobarbaz] altered

    - alter group group[foobarbaz]
    - replace group members with new list of members



On Wed, Jul 16, 2014 at 10:55 PM, George Miranda < " target="_blank"> > wrote:
Scratch that.  I went to verify this was indeed still a bug so I could move it to Github Issues.  Using chef 11.12.8, I can no longer reproduce the bug.

Can you provide some more details:  chef-client version, platform, and an actual snippet of code that reproduces the bug you're seeing?




On Wed, Jul 16, 2014 at 7:10 PM, George Miranda < " target="_blank"> > wrote:
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-4440

Perhaps this is related?





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.

§