-
Notifications
You must be signed in to change notification settings - Fork 189
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
No way to set get the "guest" option set in the generated Vagrantfile #28
Comments
Looks resolved as #29 is merged. Thank you, nice add! |
Great news, thanks! |
How did you get test-kitchen to use vagrant-windows? I have been trying to get mine to connect via winrm but no matter what I do it tries ssh. I have included the kitchen.yml and the error log. It works fine when I use vagrant up. Here is my kitchen file:
Error_Log:
|
@tim95030, the last time I created a kitchen test for a windows guest, I was using test-kitchen 1.0.0.beta.3 and kitchen-vagrant 0.11.1. I just ran the tests that I had created against those versions to confirm that they still work, and they do. I then upgraded to test-kitchen 1.1.1 and kitchen-vagrant 0.14.0 and re-ran the tests. When I run my tests against the new versions, I also get an SSH error. So, it would appear something has changed. When I was originally trying to get this to work (using the beta), I specifically had to add the
It almost looks as if it's not using vagrant to do the provisioning, despite having the At some point I will end up investigating what changed. If I figure it out, I'll post here. However, if you beat me to it, I'd appreciate if you did the same. :) |
Just to follow up on my previous post, I did a bit of research and found that the use_vagrant_provision option was removed by this changeset. With that setting removed, test kitchen tries to do the provisioning itself by talking to the VM with SSH. So, it would appear that it's no longer possible to run tests against Windows VMs unfortunately. |
I wonder why after 4 months we are still not able to run Windows from test kitchen 4993a1b Any idea on how to do that? |
I'm on the same path! Just had a timeout error: I'm still trying this thing to work.. |
I am attempting to use test kitchen to bring up a windows guest. In order for the vagrant-windows plugin to be able to do its job, the "guest" option needs to be set to :windows in the Vagrantfile. For example:
I've successfully been able to get a windows VM to come up and for chef to successfully run a recipe that I want to test by hacking my installed copy of kitchen-vagrant to write the guest setting into the Vagrantfile. (I also used the existing use_vagrant_provision: true setting, just in case anyone else comes across this and wonders how I was able to get it to work). As far as I can tell so far, this one small issue is the only thing that would prevent people from being able to use test kitchen with windows guests.
The text was updated successfully, but these errors were encountered: