[chef] Re: community cookbooks fail after upgrade to chef11

[Morgan Blackthorne < >]

Where are you seeing the issue? ISTR seeing something like this with a change to the knife.rb config, but the cookbooks themselves worked fine.

--

~*~ StormeRider ~*~

"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS

On Tue, May 28, 2013 at 2:41 PM, Kyle Sloan < " target="_blank"> > wrote:

New to chef/ruby so this may be something rather silly that I'm missing

I am using vagrant with berkshelf to work with testing cookbooks.  They all work with the default vagrant box http://files.vagrantup.com/precise32.box, which is running chef10

When I upgrade the chef version on the vagrant box with gem to 11.4.4, the cookbooks start to fail.  I upgrade/do nothing else on the box but the gem update and then try vagrant reload.

Two of the books failing are community cookbooks -- tmux and ack, which are fairly basic.
https://github.com/opscode-cookbooks/tmux
https://github.com/cap10morgan/ack-cookbook

For tmux, I'm getting this error:
FATAL: NoMethodError: undefined method `[]' for nil:NilClass

The ack one is very similar

When I replace the recipe/default.rb with hard values instead of variables, everything works, so its almost like the attributes aren't being passed in?  I am including the recipe from my "application cookbook" (maybe I need to set all the attributes in my application cookbook as include_recipe doesn't pull these? But it worked in chef10?)


from my_app_cookbook/recipes/default.rb

# none of these should require parameters/attributes, take the defaults
include_recipe "ack"
include_recipe "tmux"


Sorry this isn't much to go on, but can someone confirm that tmux/ack are working for on chef11, or point me in a direction?