-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kitchen verify
fails on Windows
#57
Comments
In case it helps, I got further with this by updating winrm, winrm-s, inspec and test-kitchen to the latest versions:
However I now get a undefined method `encoding'
|
Hi @aarsan and @stuartpreston Could you try the latest |
With TK 1.6 and kitchen-inspec 0.12.3 I get much further, past the problems with the legacy driver and it now appears to behave the same way as the rest of the winrm tooling... Good job! Unfortunately I'm having issues doing sspi negotiate in a Windows domain environment though and test-kitchen/test-kitchen#957 is tracking the issues related to this. (currently a username and password is required to be specified to be able to do negotiate auth). Then I hit the 'port' resource doesn't work correctly on Windows 2008 R2, becuase the Get-NetTCPConnection cmdlet doesn't exist there by default: My code:
I'll use the command resource as a workaround. |
Regarding the sspi negotiate, I assume we do not transfer the all parameters in https://github.com/chef/kitchen-inspec/blob/master/lib/kitchen/verifier/inspec.rb#L175. Need to double check that. The port fix is on the way: inspec/inspec#488 |
@mwrock do you have an idea? |
Yes we dealt with the |
Agreed. I'm unblocked for now but storing a username and password. |
I close this for now. If it stays an issue, please reopen |
I have the latest ChefDK installed and installed kitchen-inspec via "chef gem install kitchen-inspec".
When I run kitchen verify, I get the following error:
I'm running Test Kitchen on Windows 10 and the machine I am trying to test is Windows 2012 R2.
The text was updated successfully, but these errors were encountered: