chef-provisioning included with the Chef DK is current at v 1.1.1, however the latest is 1.2.0.

[bookshelfdave]

Running basic Chef Provisioning examples from the provisioning README result in:
No socketless chef-zero server on given port 8889, which has been resolved by chef-boneyard/chef-provisioning#337

This issue can be resolved by running gem update chef-provisioning via the chef-dk, however chef verify reports that winrm breaks:

STDERR: /opt/chefdk/embedded/lib/ruby/site_ruby/2.1.0/rubygems/specification.rb:2104:in `raise_if_conflicts': Unable to activate winrm-s-0.2.4, because winrm-1.3.3 conflicts with winrm (~> 1.2.0) (Gem::ConflictError)

Is there anything we can do to help with the winrm issue?

Cheers -
Dave

[tyler-ball]

The root-root cause of this is that chef-provisioning 1.2 depends on winrm 1.3.x and knife-windows 0.8.5 depends on winrm 1.2.x. There is a knife-windows 1.0 update in the works that will bump up to the winrm 1.3.x dependency.

Until then, though, there are a couple of options:

1. Hold off on updating chef-provisioning until knife-windows 1.0 is released
2. Update https://github.com/chef/chef/blob/master/lib/chef/resources.rb#L84-L89 to stop loading chef/provisioning at chef startup time
   • This will fix chef verify but if some user is trying to load both knife-windows and chef-provisioning they would still experience issues
   • This would also mean that all users would need to have a require 'chef/provisioning' in their provisioning cookbooks. Although we could also accomplish this was transitive requires in all the require "chef/provisioning/#{driver}" files.

[tyler-ball]

This will be fixed in ChefDK 0.7.0 by including knife-windows 1.0 and chef-provisioning 1.2

[danielsdeleo]

Fix is merged.

[lantrix]

Know this is closed; but is it just me or is this also occurring on an OOTB ChefDK 0.6.2 install?
Specifically chef verify causing

Unable to activate winrm-s-0.2.4, because winrm-1.3.3 conflicts with winrm (~> 1.2.0)

[lantrix]

In fact this doesn't just break chef verify for me but other things like knife configure

[tyler-ball]

@lantrix You probably have chef-provisioning 1.2 installed. You can do a chef gem uninstall chef-provisioning and then it should ask you what version you want to uninstall. Chef-provisioning 1.1 (the version packaged with 0.6.x) should work with OOTB with knife-windows 0.8.5.

You can also try moving ~/.chefdk to ~/.old.chefdk - this is where gems installed by chef gem install end up