-
Notifications
You must be signed in to change notification settings - Fork 37
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
Second machine fails to import after vagrant up #12
Comments
Steps to reproduce:
These steps will generate the following configuration: Vagrantfile
config/boxes.yaml
config/pe_build.yaml
config/roles.yaml
config/vms.yaml
|
Looks like this is caused by hashicorp/vagrant#2154, and is fixed in Vagrant 1.3.1 |
Awesome will try it when i get to work, will confirm and close it if it does! |
Thanks supercow! this solved the issue for me |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After initializing 2 boxes and running a vagrant up the first box (the master) comes up successfully and the agent (first) fails to import.
In the /Users//Workspace/test/.vagrant/machines/ folder the master folder is created but the first folder is missing causing the stack trace (i think).
The text was updated successfully, but these errors were encountered: