If you entered in the code correctly so far, the output of
kitchen converge should resemble the following
If the process of configuration the VM fails because kitchen is unable to enter the Vagrant machine with its private key after the relatively new change of keys that Vagrant does, it is possible, as a workaround, to change ~/.vagrant.d/Vagrantfile to disable the change of keys
Vagrant.configure("2") do |config|
config.ssh.insert_key = false
If the process is done behind a proxy, it could be interesting to install the plugin vagrant-proxyconf (vagrant plugin install vagrant-proxyconf) and add the configuration of proxy to the Vagrant default file:
config.proxy.http = "http:<user>:<password>@<proxy address>:<proxy port>" config.proxy.https = ... conf...
Share this highlighthttp://www.safaribooksonline.com/a/learning-chef/3460247/