Upgrading chef-client on windows. about chef_client_updater HOT 5 CLOSED

Hey we're facing the same problem on a virtual machine (VMWare vSphere) . It's working fine on a physical host running Windows Server 2016.

Best,
Daniel

from chef_client_updater.

Same issue here. All failures against VMs

from chef_client_updater.

Similar issue for upgrading Chef-Client on Windows. No compile or run time errors but client run hangs waiting for the current run to finish... any ideas? Works flawlessly on my *nix nodes.

  * chef_client_updater_updater[Install Latest Approved Version] action update[2017-05-25T18:37:44-04:00] INFO: Processi
ng chef_client_updater_updater[Install Latest Approved Version] action update (pilot_chef_client_updater::default line 1
6)
[2017-05-25T18:37:44-04:00] WARN: Replacing ourselves with the new version of Chef to continue the run.
[2017-05-25T18:37:50-04:00] WARN: Chef client 2904 is running, will wait for it to finish and then run.

from chef_client_updater.

We're seeing the same problem too.
Platform: Windows Server 2012 R2

• Tried with chef_client_updater.post_install_action as both kill and exec.
• Tried with and without --no-fork option on chef-client call.
• Tried with versions 1.1.1 and 1.0.2 of chef_client_updater.

from chef_client_updater.

hopefully cleaned up by #23 via merging in the changes in #18

if there's still windows issues after those changes are released, please cut a new issue (even if its the same problem).

from chef_client_updater.