-
Notifications
You must be signed in to change notification settings - Fork 170
chef verify doesn't work after installing chefdk 0.7.0 on Windows7 #482
Comments
Thanks for the detailed bug report. I'm not very familiar with windows but I will ask my colleagues who are. |
After doing some google searching it seems this issue was raised before at #102 the problem seem to occur when running chef verify at the root c:\ directory when switching to any sub-dir chef verify worked. This might be due to some funky PATH setup. The error of course doesn't suggest path is a problem |
@cshowers I am unable to repro this on a Windows 2012r2 box as an unprivileged user. I'm going to try it out on a Windows 7 box to see if that makes a difference. I currently suspect that there's some weirdness in how we launch the various sub commands. |
@ksubrama I can repro on Win 10 - if chef verify is run from c:\ for 0.6.2 it'll error as described above. Works from from a non root directory. |
Wanted to chime in and say that I noticed this today (after I updated), and the |
@smurawski Just managed to narrow this down. Turns out we currently execute "chef verify" - so if you are in a directory that contains a folder called chef, windows will execute the directory (which opens explorer.exe on it) instead. I guess we should have said chef.bat instead. We'll our exec calls as part of a future release. |
just submitted chef/mixlib-shellout#107 to address this |
Downgrade chef/chefdk RubyGems from 2.4.8 to 2.4.4.
I just updated to latest chefdk and cant get it to work. Version 0.6.2 worked fine. Below are settings
All the paths looks good and chef is using correct embedded ver of Ruby. but I cant' figure out why I'm getting this CreateProcessW error in core_ext.rb
I installed all the components in the new chefdk windows installer
I then ran chef-shell init command:
this created powershelll profile in Microsoft.PowerShell_profile.ps1:
I'm using Windows 7 SP1
The text was updated successfully, but these errors were encountered: