-
Bug
-
Resolution: Done
-
Major
-
4.4.1.AM3
-
None
-
devex #119 August 2016
-
4
In Windows, I was experiencing an error where the call to vagrant service-manager was not completing. This wasn't due to the output being unavailable, but rather the process not terminating. The current code throws a TimeoutException, but makes no attempt to check if the output is enough to still create the docker / openshift connections.
The code should attempt to survive the error and continue along.
- is related to
-
JBIDE-22818 vagrant service-manager call experiences timeout after output
- Closed