Windows chefdk 0.1.1 verify failing when run in base directory

[smiskiewicz]

System info:
Windows 7
Microsoft Windows [Version 6.1.7601]

When running in the base directory chef verify is failing:

C:\>chef verify
Running verification for component 'berkshelf'
Running verification for component 'test-kitchen'
Running verification for component 'chef-client'
Running verification for component 'chef-dk'
...C:/opscode/chefdk/embedded/lib/ruby/gems/2.0.0/gems/mixlib-shellout-1.4.0-x86
-mingw32/lib/mixlib/shellout/windows/core_ext.rb:346:in `create': Input/output e
rror - CreateProcessW (Errno::EIO)
        from C:/opscode/chefdk/embedded/lib/ruby/gems/2.0.0/gems/mixlib-shellout
-1.4.0-x86-mingw32/lib/mixlib/shellout/windows.rb:86:in `run_command'
        from C:/opscode/chefdk/embedded/lib/ruby/gems/2.0.0/gems/mixlib-shellout
-1.4.0-x86-mingw32/lib/mixlib/shellout.rb:227:in `run_command'
        from c:/opscode/chefdk/embedded/apps/chef-dk/lib/chef-dk/helpers.rb:29:i
n `system_command'
        from c:/opscode/chefdk/embedded/apps/chef-dk/lib/chef-dk/component_test.
rb:86:in `sh'
        from c:/opscode/chefdk/embedded/apps/chef-dk/lib/chef-dk/component_test.
rb:92:in `block in run_in_tmpdir'
        from c:/opscode/chefdk/embedded/apps/chef-dk/lib/chef-dk/component_test.
rb:98:in `block in tmpdir'
        from C:/opscode/chefdk/embedded/lib/ruby/2.0.0/tmpdir.rb:88:in `mktmpdir
'
        from c:/opscode/chefdk/embedded/apps/chef-dk/lib/chef-dk/component_test.
rb:97:in `tmpdir'
        from c:/opscode/chefdk/embedded/apps/chef-dk/lib/chef-dk/component_test.
rb:90:in `run_in_tmpdir'
        from c:/opscode/chefdk/embedded/apps/chef-dk/lib/chef-dk/command/verify.
rb:114:in `block (2 levels) in <class:Verify>'
        from c:/opscode/chefdk/embedded/apps/chef-dk/lib/chef-dk/component_test.
rb:76:in `instance_eval'
        from c:/opscode/chefdk/embedded/apps/chef-dk/lib/chef-dk/component_test.
rb:76:in `run_smoke_test'
        from c:/opscode/chefdk/embedded/apps/chef-dk/lib/chef-dk/command/verify.
rb:167:in `block (2 levels) in invoke_tests'

Running in a directory is successful.
C:\Dev>chef verify
Running verification for component 'berkshelf'
Running verification for component 'test-kitchen'
Running verification for component 'chef-client'
Running verification for component 'chef-dk'

........................................

Verification of component 'chef-client' succeeded.
Verification of component 'berkshelf' succeeded.
Verification of component 'chef-dk' succeeded.
Verification of component 'test-kitchen' succeeded.

[tfitch]

I'm seeing this same issue with trying to run Test Kitchen on Windows boxes. Trying to do a kitchen list command. But that top of the Backtrace is the

Kitchen: Message: Input/output error - CreateProcessW
Kitchen: ------Backtrace-------
C:/opscode/chefdk/embedded/lib/ruby/gems/2.0.0/gems/mixlib-shellout-1.4.0-x86
-mingw32/lib/mixlib/shellout/windows/core_ext.rb:346:in `create'

So I want to get a +1 on this more or less.

[sersut]

Thanks for the reports guys. I think these will be separate issues. @tfitch can you give us a little bit more detail on your config? Are you only seeing this when you're in root as well?

[tfitch]

@sersut Sorry for the delayed response (lost in an avalanche of GitHub notifications). I'm actually relaying this messaging on behalf of one of our enterprise customers. He's got pretty good access to tweak his machine, it isn't totally locked down like some people have, but he's still getting this error. He can run his command prompt as Administrator (aka root) and still got this error.

One thing I know he's doing that interests me is he's using ConEmu for his command prompt. I don't know why, other than I'm sure it's what he's most comfortable with. I suspect the core issue is around his $PATH. Lots of moving parts here... He's tried both ChefDK and removing the DK and manually installing the DK tools as gems and still got the exact same error. So with that info, it's feeling more like a TK issue... But the only reference I've seen to the CreateProcessW error was on this issue logged in the DK and not in TK. Thus I'm talking about it here.

[imdwalrus]

I'm the enterprise customer referenced above. The error occurs in the native Windows command prompt as well. Mischa and Seth recommended ConEmu in their Learning Chef book. It provides a tabbed interface which is convenient for managing multiple terminal sessions concurrently.

[irvingpop]

This appears to be fixed in the latest version of ChefDK (0.3.2)