Chef 11.14.2 breaks due to ruby-wmi dependency

[Scythril]

Just a heads up, if you start using Chef 11.14.2 with this cookbook (as I am while using the latest Chef Omnibus installer via vagrant), it breaks on the ruby-wmi dependencies.

One of the notes on Chef 11.14.2 here is that the ruby-wmi gem was replaced with the wmi-lite gem. Is that something you guys plan to also do in the windows cookbook?

[ghost]

I'm hitting this right now as well. If you're deploying with knife, it looks like you're able to control the version of chef-client with a --bootstrap-version flag.

[justinrstout]

I too am hitting this when bootstrapping with WinRM. My workaround was to use the --bootstrap-version option to specify the previous stable version of chef client (11.12.8).

[Scythril]

Similar thing for Vagrant, use

config.omnibus.chef_version = '11.12.8'

[btm]

I'm currently testing #100 as a potential fix.

[btm]

#101 was merged and released, The windows cookbook version 1.34.0 fixes this bug.

[btm]

This is being fixed a different way (sans any gem dependencies) in #108

[jeremiahsnapp]

@btm So is windows cookbook 1.34.0 actually broken right now or are you just refactoring things?

[btm]

1.34.0 worked fine if you were using 11.14.2 omnibus which included wmi-lite or had internet access to install the wmi-lite gem. 1.34.2 has no external wmi gem dependencies.