Closed sarimali closed 8 years ago
What version of chef-client are you using? I think you might be running into this issue on 12.6.0:
yep... thanks! which version should i be using?
Until a new version is released with that fix, I'd recommend 12.5.1
Still seeing that even after changing to omnibus 12.5.1. I then checked the .kitchen.yml in the repo and saw 11.18.6 and tried its the same error.
Did you destroy the box? Kitchen wasn't reverting for me when I was trying to roll back with this issue. I had to destroy and rebuild.
Other details about the setup? Windows version, current version of Powershell etc.?
looks like i was forcing the latest regardless ... whoops
provisioner:
name: chef_zero
chef_metadata_url: 'https://www.chef.io/chef/metadata?p=windows&m=x86_64&pv=2012r2&v=latest'
:) We've all been there!
im getting this now... Expected process to exit with [0, 42, 127, 3010], but received '5' ... i tried destroy first this time and i did this fix:
windows_service 'wuauserv' do
startup_type :automatic
action [ :enable, :start ]
end
no luck, any ideas?
Just a side point im experimenting the new dsc_resource in chef. Powershell 4 wouldn't work with dsc_script so i decided to give ps5 a shot. i can share my cookbook if you want to see what im doing.
Oh- it's an update. You're probably running into the winrm permissions issues using chef_zero... Try using chef-zero-scheduled-task: https://github.com/smurawski/chef-zero-scheduled-task