[chef] Re: Re: Re: Problem bootstraping chef-client to Windows machines

[Carlos Camacho < >]

Ok perfect,

I thought that i was using a chef-client release candidate, maybe its
useful to only bootstrap new nodes/clients with 1 lower version to
mitigate some issues and
add one more safeguard.

The issue its exactly what you are describing, "Windows cookbook has a
dependency on ruby-wmi, but doesn't resolve this dependence and it
fails"

In this case to have a conclusion, its a problem with the Windows
cookbook instead the chef-client (Works perfect in Linux as usual)??


Best regards,

Carlos.

On Mon, Aug 4, 2014 at 3:43 PM, Steven Danna 
<
 >
 wrote:
> Hi Carlos,
>
>>> Its normal to release new client versions with this type of problems!?!?
>
> The goal is that such problems are caught in testing and via the
> distribution of release candidates and betas.  Unfortunately, it seems
> a problem might have gotten past those safeguards in this case.
>
> My suspicion is that the windows cookbook has a dependency on ruby-wmi
> but doesn't ensure it is installed.  This potentially worked in past
> versions of Chef because of Chef's own dependencies but changed with
> the following commit:
>
> https://github.com/opscode/chef/commit/e0c2469f3af617c34f13a32cc8b0490204be7979#diff-ea2858b57306467ffd3011d3ce3e6510
>
> I (or someone else) will post some more details once we can look into
> this problem.
>
> Cheers,
>
> Steven