[chef] Re: Re: Re: Re: Intermittent problem when provisioning with vagrant

[Cassiano Leal < >]

I kind of missed the difference here. :)

Either way, I tried both approaches. Both seem to work fine (I say "seem" because it's intermittent, so it could be that I'm just being lucky…). I like the include_attribute approach better, though, since it allows me to keep the recipe attribute-free.

Thanks for all the input, I'll come back here if it bites me again!

-- 

Cassiano Leal

On Monday, October 22, 2012 at 16:15, Daniel DeLeo wrote:

On Monday, October 22, 2012 at 11:08 AM, Cassiano Leal wrote:

That attribute is originally set on the zynkbase cookbook, which is loaded as a dependency.

If I understand the discussion you linked correctly, one possible solution would be to set the node[:gearman][:dir] attribute in the zynkconverter default recipe, is that correct?

Thanks for your help!

-- 

Cassiano Leal

On Monday, October 22, 2012 at 15:58, Bryan Baugher wrote:

It looks like the attribute node[:zynk] is nil at the time the default attribute file is loaded. Where is the value for 'node[:zynk][:appdir]'being set? 

Also, you should not use nested attributes (like what you have on line 1) in your attributes file as Chef cannot guarantee the ordering of when attributes are set from (attribute files, roles, environments..). I am guessing this is your issue.

There was a recent discussion about this, http://lists.opscode.com/sympa/arc/chef/2012-10/msg00266.html

This is a slightly different issue. What's happening here is you're getting bit by nondeterministic load order of attribute files. There's been a lot of discussion on this bug/topic recently as well, but anyway, the way to fix it is to use `include_attribute "zynkbase"` in zynkconverter/attributes/default.rb, which will ensure that attributes file loads first.

-- 

Daniel DeLeo