This repository has been archived by the owner on Dec 8, 2020. It is now read-only.
vagrant up Issue - SSH is not ready and timeouts, provisioning fails. #56
Comments
StefanScherer
added a commit
to StefanScherer/vagrant-vcloud
that referenced
this issue
May 16, 2014
* upstream/develop: Fixes frapposelli#31 - Initial implementation for vagrant share commands, needs improvement Changed a bit the debug look, and added timestamp to calculate request time for each SEND/RECV request Fixes frapposelli#56 - Temporary fix, needs to be re-implemented
|
Tested with a very slow box start (intentional box with sleep 300 = 5min for sshd service)
|
|
Current fix doesn't handle "host is down" situations, re-implementing it with vagrant core builtins. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using
vcloud.network_bridge = falsewhere less network related tasks occur and/or depending on the vagrant box used, you can get into a situation where the vagrant-vcloud provider tries to connect to the machine through SSH and would timeout as it would not be ready.This can be verified by trying a
vagrant sshsometime after the failure, it works as the machine finished the customization process and all according services are started.The text was updated successfully, but these errors were encountered: