This repository has been archived by the owner on Dec 13, 2019. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 122
ansible up
== default: Warning: Connection timeout. Retrying...
#21
Comments
When I use
|
Also same issue with 1.1.6
|
1.1.0 does appear to work though
|
1.1.3 and 1.1.5 work as well. |
Odd, I had updated Vagrant to 1.9.1 to get the option to init a certain version of a box. Now 1.1.7 just hangs at |
I checked out the repo and tried to do a diff but the tags/releases don't match the published boxes. |
@ElijahLynn - Yeah, unfortunately it's been difficult to keep the tags and box versions in sync as I never was too strict about tags when VirtualBox guest additions were updated :/ |
Closing as all development work for my packer boxes is moving into a central repository, see: geerlingguy/packer-boxes#45 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Moved from geerlingguy/ansible-for-devops#54
Host Ubuntu 14.04, ansible 2.2.0.0, vboxmanage 4.3.36_Ubuntur105129
When doing an
ansible up
I get aThis answer to use the GUI prompt to choose default|safe mode does get me past that stage. http://stackoverflow.com/a/22575302/292408.
In addition
vagrant ssh
doesn't appear to work, not sure if it is related or not.The text was updated successfully, but these errors were encountered: