[chef] Re: Re: Version locking a cookbook in environment AND role

[DV < >]

I am hoping to have entire environment locked down to cookbook version
0.0.10, while the nodes with that role assigned locked down to 0.0.11.
If both environment and role are setting the same "lockdown" attribute
and role takes precedence, I would expect it to work that way.
However, if what chef-client is getting is something along the lines
of "java cookbook that's 0.0.10 and 0.0.11" then I see why it's not
working as I intend it to.

- DV

On Thu, Sep 27, 2012 at 12:54 PM, Peter Donald 
<
 >
 wrote:
> Hi,
>
> On Fri, Sep 28, 2012 at 5:26 AM, DV 
> <
 >
>  wrote:
>>
>> I'm having trouble version locking a cookbook in the environment AND
>> role at the same time.
>>
>> In my environment file I have:
>>
>> cookbook "java", "= 0.0.10"
>>
>> In my role I have:
>>
>> run_list(
>>     ...
>>     
>> "
 ",
>>     ...
>> )
>
>
>
> It looks like you are attempting to lock them to different versions so I am
> not surprised that this does not work. It can not satisfy both constraints.
> (But note I have not tried it out). What version of the java cookbook do you
> expect a node in that environment with that role to use?
>
> --
> Cheers,
>
> Peter Donald



-- 
Best regards, Dmitriy V.