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

[Carlos Camacho < >]

Hello,

Today Im bootstrapping new Windows nodes and this is what Imreceiving
when bootstraping the node.

host [2014-08-11T14:06:27+00:00] INFO: Processing
remote_file[C:\7z922-x64.msi] action create (frontiers_custom::7zip
line 10)
host [2014-08-11T14:06:27+00:00] INFO: remote_file[C:\7z922-x64.msi]
created file C:\7z922-x64.msi
host [2014-08-11T14:06:28+00:00] INFO: remote_file[C:\7z922-x64.msi]
updated file contents C:\7z922-x64.msi
host [2014-08-11T14:06:28+00:00] INFO: remote_file[C:\7z922-x64.msi]
owner changed to S-1-5-21-263322904-1275562841-2159875451-500
host [2014-08-11T14:06:28+00:00] INFO: Processing
windows_package[7-Zip] action install (frontiers_custom::7zip line 16)
host [2014-08-11T14:06:28+00:00] INFO: Installing
windows_package[7-Zip] version latest
host [2014-08-11T14:06:28+00:00] INFO: Starting installation...this
could take awhile.
host [2014-08-11T14:06:29+00:00] INFO: Processing
windows_path[C:/Program Files/7-Zip/] action add
(frontiers_custom::7zip line 22)
host [2014-08-11T14:06:29+00:00] INFO: Processing env[PATH] action
modify (c:/chef/cache/cookbooks/windows/providers/path.rb line 22)
host
host 
================================================================================
host Error executing action `modify` on resource 'env[PATH]'
host 
================================================================================
host
host Chef::Exceptions::Env
host ---------------------
host Cannot modify env[PATH] - key does not exist!
host
host Resource Declaration:
host ---------------------
host # In c:/chef/cache/cookbooks/windows/providers/path.rb
host
host  22:   env "PATH" do
host  23:     action :modify
host  24:     delim ::File::PATH_SEPARATOR
host  25:     value new_resource.path
host  26:   end
host  27: end
host
host Compiled Resource:
host ------------------
host # Declared in
c:/chef/cache/cookbooks/windows/providers/path.rb:22:in `block in
class_from_file'
host
host env("PATH") do
host   action [:modify]
host   retries 0
host   retry_delay 2
host   guard_interpreter :default
host   key_name "PATH"
host   value "C:/Program Files/7-Zip/"
host   delim ";"
host   cookbook_name "frontiers_custom"
host end
host
host [2014-08-11T14:06:29+00:00] INFO: Running queued delayed
notifications before re-raising exception
host [2014-08-11T14:06:29+00:00] ERROR: Running exception handlers
host [2014-08-11T14:06:29+00:00] ERROR: Exception handlers complete
host [2014-08-11T14:06:29+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
host [2014-08-11T14:06:29+00:00] FATAL: Chef::Exceptions::Env:
env[PATH] (c:/chef/cache/cookbooks/windows/providers/path.rb line 22)
had an error: Chef::Exceptions::Env: Cannot modify env[PATH] - key
does not exist!


As the same this error happens only with new client new version.


Best regards,


Carlos.


On Tue, Aug 5, 2014 at 8:32 AM, Carlos Camacho
<
 >
 wrote:
> No problem,
> Thanks to you for having and maintaining this amazing piece of software!
>
> Actually I'm not a Windows fan but i have to test and use Chef in our
> Windows environments, so i will test it for sure.
>
> Regards,
>
> Carlos.
>
>
>
>
> On Tue, Aug 5, 2014 at 2:26 AM, Adam Edwards 
> <
 >
>  wrote:
>> We've released a fix in the Windows cookbook for this issue to Supermarket
>> and tested it on different versions of Chef including Chef 10.32.2, Chef
>> 11.12.8, and Chef 11.14.2:
>> https://supermarket.getchef.com/cookbooks/windows. Please let us know if
>> you're still seeing this issue with the new version 1.34.0 of the Windows
>> cookbook.
>>
>> Thank you for your patience, and our apologies for not finding this prior 
>> to
>> the release of Chef 11.14.2. We are adding additional regression automation
>> through test-kitchen to catch this sort of problem on different platforms
>> prior to release and even commit.
>>
>> -Adam
>>
>> -----Original Message-----
>> From: Adam Edwards 
>> [mailto:
 
>> Sent: Monday, August 4, 2014 8:59 AM
>> To: 
>> '
 '
>> Subject: RE: [chef] Re: Re: Re: Problem bootstraping chef-client to Windows
>> machines
>>
>> Yes, it's definitely a problem in the Windows cookbook, which should
>> probably be using chef_gem to bring back the dependency. We'll test out a
>> fix to that cookbook and once that's verified get it out to Supermarket
>>
>> Thank you Carlos, and our apologies for not catching this dependency prior
>> to release. The cookbook should not have taken a dependency on Chef
>> satisfying its gem dependencies, something we can get better at catching 
>> now
>> that test-kitchen is getting imrpvoed cookbook testing support on Windows.,
>>
>> -Adam
>>
>> -----Original Message-----
>> From: Carlos Camacho 
>> [mailto:
 
>> Sent: Monday, August 4, 2014 7:13 AM
>> To: 
>> 
 
>> Subject: [chef] Re: Re: Re: Problem bootstraping chef-client to Windows
>> machines
>>
>> 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/e0c2469f3af617c34f13a32cc8b0490
>>> 204be7979#diff-ea2858b57306467ffd3011d3ce3e6510
>>>
>>> I (or someone else) will post some more details once we can look into
>>> this problem.
>>>
>>> Cheers,
>>>
>>> Steven