<div dir="ltr"><div>Well, just by looking at the trace included in this thread, it's obvious we're running vagrant service-manager, and we're getting output, but then we're getting a timeout. I can only conclude that somehow the process isn't terminating. I could probably clean up my error handling a bit to *try* to recover from this, ie, in the event of a timeout, see if we have any response text at all, and see what we can do about it. But I'm not even sure that would be the correct solution. <br><br></div><div>I believe Jeff Murray was referencing <a href="https://issues.jboss.org/browse/JBIDE-22664">https://issues.jboss.org/browse/JBIDE-22664</a> but this issue isn't about the registration but rather during vagrant service-manager calls. So it'd be the same location in the code (or similar / nearby at least). But the fact that it's a timeout exception rather than a parse exception means the error isn't caused by the color codes. It's caused by the call to vagrant service-manager not completing in a timely fashion. <br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 25, 2016 at 7:38 PM, Alexey Kazakov <span dir="ltr"><<a href="mailto:alkazako@redhat.com" target="_blank">alkazako@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Rob, you mean this exception is caused by the issue similar to the
issue we had with vagrant-sshfs:
<a href="https://issues.jboss.org/browse/JBIDE-22604m" target="_blank">https://issues.jboss.org/browse/JBIDE-22604m</a> ?<br>
<br>
And what is the JIRA for the bug with vagrant-registration being
corrupted by escape characters mentioned by Jeff?<div><div class="h5"><br>
<br>
<div>On 07/25/2016 11:12 AM, Robert Stryker
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>The exception listed doesn't seem related to the color
characters at all. Rather, it seems reminiscent of the
service-manager call never completing. It seems we fetch all
the output but we never get an exit status for the
service-manager process we launched, and so we throw a timeout
exception. <br>
<br>
</div>
Does anyone remember this issue cropping up before? Anyone
remember a jira id for it? <br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Jul 22, 2016 at 8:37 AM, Todd
Mancini <span dir="ltr"><<a href="mailto:tmancini@redhat.com" target="_blank">tmancini@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">When you document it, please leave out the
"and reboot" part, as that's a very dramatic solution to a
much easier problem. The user simply needs to get the
updated environment into their current context. I can help
with the wording/instructions relative to that.</div>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Jul 22, 2016 at 8:27
AM, Rick Wagner <span dir="ltr"><<a href="mailto:rwagner@redhat.com" target="_blank"></a><a href="mailto:rwagner@redhat.com" target="_blank">rwagner@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>Many thanks, Jeff.<br>
<br>
</div>
We'll ask our customer to try this
workaround. (We'll document it in KCS for
later usage, also.)<span><font color="#888888"><br>
<br>
</font></span></div>
<span><font color="#888888">Rick<br>
</font></span></div>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Jul 22,
2016 at 2:46 AM, Jean-Francois Maury <span dir="ltr"><<a href="mailto:jmaury@redhat.com" target="_blank">jmaury@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Rick,
<div><br>
</div>
<div>we have found an issue regarding
the output of vagrant-registration
being corrupted by escape
characters. We've fixed and it will
be included in this Sprint bits of
DevStudio.</div>
<div>There is a possible workaround:
define the env variable (on Windows
using the Control
Panel) VAGRANT_NO_COLOR and set the
value to 1. I would suggest
rebooting your machine and launch
DevStudio again.</div>
<div><br>
</div>
<div>Jeff</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div>On Thu, Jul 21, 2016 at 9:54
PM, Rick Wagner <span dir="ltr"><<a href="mailto:rwagner@redhat.com" target="_blank"></a><a href="mailto:rwagner@redhat.com" target="_blank">rwagner@redhat.com</a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>
<div dir="ltr">
<div>
<div>
<div>
<div>Hello CDK SMEs,<br>
<br>
</div>
We have a support case
where the user is
unable to use the
CDK. They have
installed via
Development Suite
installer and offer
the following:<br>
<br>
-------------------------------------------------<br>
I installed the Suite
and tried to start the
server Container
Development
Environment and it
seems it started
successfully (i
attached log on file
vagrant_up.txt). But I
received this error
after server started:
"Unable to configure
docker and openshift.
Calls to vagrant
service-manager are
returning empty
environments."<br>
--------------------------------------------------<br>
<br>
<br>
</div>
We've compared the
vagrant log to a lab
machine known to work,
we see a difference
starting with
vagrant-registration's
actions. (See
screenshot below.)<br>
<br>
</div>
A comparison of the
vagrant plug-ins shows the
user has the same versions
the lab box has.<br>
<br>
</div>
The Eclipse log offers us
the following. Note
especially the curious
phrase "Calls to vagrant
service-manager are
returning empty
environments.".<br>
<br>
------------------------------------------------------<br>
!ENTRY
org.jboss.tools.openshift.cdk.server
4 0 2016-07-21 09:48:26.869<br>
!MESSAGE Unable to
successfully complete a call
to vagrant service-manager.<br>
!STACK 0<br>
java.util.concurrent.TimeoutException:
Process output:<br>
^[[0m # docker
env:^[[0m # Set the
following environment
variables to enable access
to the # docker daemon
running inside of the
vagrant virtual machine:
export DOCKER_HOST=tcp://<a href="http://10.1.2.2:2376" target="_blank">10.1.2.2:2376</a>
export
DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\'
export DOCKER_TLS_VERIFY=1
export
DOCKER_API_VERSION=1.21
^[[0m^[[0m ^[[0m #
openshift env:^[[0m ^[[0m#
You can access the OpenShift
console on: <a href="https://10.1.2.2:8443/console" target="_blank"></a><a href="https://10.1.2.2:8443/console" target="_blank">https://10.1.2.2:8443/console</a>
# To use OpenShift CLI, run:
oc login <a href="https://10.1.2.2:8443" target="_blank"></a><a href="https://10.1.2.2:8443" target="_blank">https://10.1.2.2:8443</a>
export OPENSHIFT_URL=<a href="https://10.1.2.2:8443" target="_blank"></a><a href="https://10.1.2.2:8443" target="_blank">https://10.1.2.2:8443</a>
export
OPENSHIFT_WEB_CONSOLE=<a href="https://10.1.2.2:8443/console" target="_blank"></a><a href="https://10.1.2.2:8443/console" target="_blank">https://10.1.2.2:8443/console</a>
export DOCKER_REGISTRY=<a href="http://hub.openshift.rhel-cdk.10.1.2.2.xip.io" target="_blank">hub.openshift.rhel-cdk.10.1.2.2.xip.io</a>^[[0m
^[[0m # run following
command to configure your
shell: # eval
"$(VAGRANT_NO_COLOR=1
vagrant service-manager env
| tr -d '\r')"^[[0m<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:185)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:174)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:154)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:133)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:250)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:242)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:235)<br>
<br>
!ENTRY
org.jboss.tools.openshift.cdk.server
4 0 2016-07-21 09:49:07.139<br>
!MESSAGE Unable to
successfully complete a call
to vagrant service-manager.<br>
!STACK 0<br>
java.util.concurrent.TimeoutException:
Process output:<br>
^[[0m # docker
env:^[[0m # Set the
following environment
variables to enable access
to the # docker daemon
running inside of the
vagrant virtual machine:
export DOCKER_HOST=tcp://<a href="http://10.1.2.2:2376" target="_blank">10.1.2.2:2376</a>
export
DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\'
export DOCKER_TLS_VERIFY=1
export
DOCKER_API_VERSION=1.21
^[[0m^[[0m ^[[0m #
openshift env:^[[0m ^[[0m#
You can access the OpenShift
console on: <a href="https://10.1.2.2:8443/console" target="_blank"></a><a href="https://10.1.2.2:8443/console" target="_blank">https://10.1.2.2:8443/console</a>
# To use OpenShift CLI, run:
oc login <a href="https://10.1.2.2:8443" target="_blank"></a><a href="https://10.1.2.2:8443" target="_blank">https://10.1.2.2:8443</a>
export OPENSHIFT_URL=<a href="https://10.1.2.2:8443" target="_blank"></a><a href="https://10.1.2.2:8443" target="_blank">https://10.1.2.2:8443</a>
export
OPENSHIFT_WEB_CONSOLE=<a href="https://10.1.2.2:8443/console" target="_blank"></a><a href="https://10.1.2.2:8443/console" target="_blank">https://10.1.2.2:8443/console</a>
export DOCKER_REGISTRY=<a href="http://hub.openshift.rhel-cdk.10.1.2.2.xip.io" target="_blank">hub.openshift.rhel-cdk.10.1.2.2.xip.io</a>^[[0m
^[[0m # run following
command to configure your
shell: # eval
"$(VAGRANT_NO_COLOR=1
vagrant service-manager env
| tr -d '\r')"^[[0m<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:53)<br>
at
org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:43)<br>
at
org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)<br>
<br>
!ENTRY
org.jboss.tools.openshift.cdk.server.core
4 0 2016-07-21 09:49:07.142<br>
!MESSAGE Unable to configure
docker and openshift. Calls
to vagrant service-manager
are returning empty
environments.<br>
<br>
--------------------------------------------------------------------------------------<br>
<div>
<div>
<div>
<div>
<div><br>
<br>
<br>
<br>
</div>
<div>Any suggestions
are greatly
appreciated.<br>
<br>
</div>
<div>Thanks,<br>
<br>
</div>
<div>Rick<br>
</div>
<div><br>
<br>
<br>
<br>
<br>
<br>
<img style="margin-right:0px" alt="Inline
image 2" src="cid:part17.08020706.03080406@redhat.com" height="510" width="1128"><br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
_______________________________________________<br>
Devtools mailing list<br>
<a href="mailto:Devtools@redhat.com" target="_blank">Devtools@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/devtools" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/devtools</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Devtools mailing list<br>
<a href="mailto:Devtools@redhat.com" target="_blank">Devtools@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/devtools" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/devtools</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Devtools mailing list<br>
<a href="mailto:Devtools@redhat.com" target="_blank">Devtools@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/devtools" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/devtools</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Devtools mailing list
<a href="mailto:Devtools@redhat.com" target="_blank">Devtools@redhat.com</a>
<a href="https://www.redhat.com/mailman/listinfo/devtools" target="_blank">https://www.redhat.com/mailman/listinfo/devtools</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Devtools mailing list<br>
<a href="mailto:Devtools@redhat.com">Devtools@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/devtools" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/devtools</a><br>
<br></blockquote></div><br></div>