-
Notifications
You must be signed in to change notification settings - Fork 552
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
Bootstrap fails on Ubuntu 14.04 via Vagrant provisioner #648
Comments
Have you tried starting the minion by hand on that vagrant box? What's on the minion's log file? |
After a clean provision:
Since it is missing the configuration it is communicating with the production-master instead. Or at least trying to.. Perhaps this is more of a Salt-Vagrant provisioning issue rather than one for the Bootstrap although it was working fine before earlier and only started whenever the Having just the
|
+1 on having this issue; sucky; breaks my vagrant/serverspec testing of salt; i'm sad :( (going to try workaround) |
Moved to saltstack/salt#26731. |
This appears to be yet another regression of #370 |
This error also happens to me with centos 6.6, same error. |
Experienced this also, I needed to use the following (which requires Vagrant >= 1.7.4)
|
When #674 is merged, bootstrap should no longer need |
#674 was merged. Closing. Please re-open if necessary. |
thanks for fixing! |
With recent changes it is required to add the following to the Vagrantfile:
Pretty annoying to have this, since we have a large number of boxes and fresh installs are causing issues.
However, even with the
-P
flag it isn't properly provisioning either:The second run of
vagrant provision
results in:Since we use Salt (with Vagrant) on a daily basis this is causing quite a bit of trouble.
This particular box uses the following Vagrantfile:
The text was updated successfully, but these errors were encountered: