There are a number of provisioning steps performed when Vagrant launches a virtual machine. These may come from plugins, such as the Vagrant Registration plugin for Red Hat, or from steps that are included in the Vagrantfile for provisioning the box on startup. Vagrant runs these commands by using SSH.
In many cases, errors during the provisioning step are not fatal, so the Vagrant box will still be running. Use the
vagrant statuscommand to see what the state of your box is. You can stop the Vagrant box with the
vagrant haltcommand. If the machine is running, you should be able to log into it using the
vagrant sshcommand to examine the VM and see what went wrong.
While the box is running, you can rerun the provisioning steps by running the
Note that you need to be in the same directory where your Vagrantfile is. If you have lost track of where your Vagrantfile is, use the
vagrant global-statuscommand to list the boxes that you have started and the directory where the Vagrantfile and state is stored.
Are you using Vagrant version 1.5.0 as it is a known issue in that version of Vagrant. Please use Vagrant version mentioned in the "Vagrant compatibility matrix" in CDK documentation.