[chef] Re: Re: Re: Re: Re: yum::epel problems in wrapped cookbook

[Jeffrey Jones < >]

Hello Steven

On 15/06/13 06:22, Steven Danna wrote:
> On 6/14/13 7:57 AM, Julian C. Dunn wrote:
> > Hey Jeffrey: I don't see your recipe code anywhere but judging from the
> > gist you have something like this:
> >
> > connector::default has include_recipe "torquebox-web-server"
> > torquebox-web-server::default has include_recipe "yum::epel"
> >
> > Is "yum" anywhere in your metadata for any of those cookbooks?
> >
> > Even I'm not entirely sure whether include_recipe also loads attributes
> > from the dependent cookbook...
> The attribute files of all cookbooks in the run list and their
> dependencies get loaded during the converge phase.  What is interesting
> here is that a breaking change for Chef 11 was that chef-solo won't be
> able  to include_recipe unless you've also specified "depends" in your
> metadata. Thus, I believe this should be working correctly.
>
> If you use
>
>      include_attribute "yum::epel"
>
> in your default attribute file for the connector cookbook, does that
> resolve the issue?
>
> Cheers,
>
> Steven
I have added the debug output after adding the "include_attribute" section.
It looks like the old error has been fixed but a new error has appeared.

"[2013-06-17T02:12:46+00:00] FATAL: NameError: Cannot find a resource 
for yum_key on centos version 6.4"

I am guessing that the attributes/epel.rb file is being executed by the 
selection logic inside the file is failing for some reason?

https://gist.github.com/rurounijones/5771208 ("Add attribute" section 
for full debug output)

Cheers

Jeff