undefined method `groups' for Chef::Resource::UserAccount about chef-user

[ohlol]

Where did you get the cookbook from? The one on supermarket is not updated. I tweeted @fnichol about it but have yet to hear anything.

[jcderose]

@umangd1 I couldn't tell you why this works, but I moved all my cookbook version dependency statements from my Berksfile into metadata.rb in the (custom) wrapper cookbook calling the user cookbook. So previously it looked like:

# my-cookbook/Berksfile

source 'https://supermarket.chef.io'

metadata

cookbook 'user', github: 'fnichol/chef-user'
cookbook 'some_cookbook1', '= 1.8.6'        
cookbook 'some_cookbook2', '= 0.9.1'        
cookbook 'some_cookbook3', '= 1.1.2'

# my-cookbook/metadata.rb

...

depends 'user'
depends 'some_cookbook1'
depends 'some_cookbook2'
depends 'some_cookbook3'

And now it looks like:

# my-cookbook/Berksfile

source 'https://supermarket.chef.io'

metadata

cookbook 'user', github: 'fnichol/chef-user'

# my-cookbook/metadata.rb

...

depends 'user'
depends 'some_cookbook1', '= 1.8.6' 
depends 'some_cookbook2', '= 0.9.1'
depends 'some_cookbook3', '= 1.1.2'

[jcderose]

@ohlol I'm pulling the cookbook from the github repo.

source 'https://supermarket.chef.io'

metadata

cookbook 'ap-baseline', git: 'path/to/cookbook'
cookbook 'user', github: 'fnichol/chef-user'

[umangd1]

facing same issue. I installed user cookbook via knife. Version is 0.4.2, same as in this repository.
@jcderose how did you get it working?

[umangd1]

this is weird. I have a simple example with no other dependency. As @ohlol pointed out, the supermarket version is not the latest. I installed the latest version using knife-github-cookbooks gem and not facing this error anymore.

[theckman]

I just ran in to this issue as well. I'm downloading 0.4.2 from the Chef supermarket and it does not contain the a provider with the groups resource.

[nozpheratu]

Seems groups isn't available even from the Github source.... I can see it there in the source code, but the file that Berks pulls in doesn't have it, even if I explicitly set the source to the git repo.

[theckman]

It is available in the GitHub source. I think you need to explicitly provide the commit ref:

cookbook 'user', git: 'https://github.com/fnichol/chef-user.git', ref: 'fd2094cc8a'

[nozpheratu]

@theckman I found my issue, it was with Berkshelf's retarded dependency resolver. If you require cookbook "a" that uses a git as a source in cookbook "b", Berkshelf will default to using the version available on supermarket for cookbook "b" so long as the version matches rather than the Github source......

So basically I have to specify

cookbook 'user', git: 'https://github.com/fnichol/chef-user.git

In both cookbook's Berkfiles...

[theckman]

@nozpheratu Ah, yeah. I hadn't even considered that. I usually keep my user stuff confined to a single cookbook, so I've only ever needed to hit one spot. 👍

[nozpheratu]

@theckman This issue extends to other cookbooks that are fetched from git sources as well. The only reason I figured it out so soon after posting that is because I literally ran into the same problem an hour ago with another cookbook. 😞

[nozpheratu]

Completely unrelated to the issue, but I shouldn't call their dependency solver retarded. After looking into the code it looks like it relies on semantic versioning to operate correctly, so the issue is more a lack of proper version control (which you can't really expect when pulling directly from a Github repo I suppose).