[Devtools] C/O CDK SMEs: Windows user going off the rails somewhere along the line
Robert Stryker
rstryker at redhat.com
Tue Jul 26 04:32:15 UTC 2016
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.
I believe Jeff Murray was referencing
https://issues.jboss.org/browse/JBIDE-22664 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.
On Mon, Jul 25, 2016 at 7:38 PM, Alexey Kazakov <alkazako at redhat.com> wrote:
> Rob, you mean this exception is caused by the issue similar to the issue
> we had with vagrant-sshfs: https://issues.jboss.org/browse/JBIDE-22604m ?
>
> And what is the JIRA for the bug with vagrant-registration being corrupted
> by escape characters mentioned by Jeff?
>
>
> On 07/25/2016 11:12 AM, Robert Stryker wrote:
>
> 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.
>
> Does anyone remember this issue cropping up before? Anyone remember a
> jira id for it?
>
> On Fri, Jul 22, 2016 at 8:37 AM, Todd Mancini <tmancini at redhat.com> wrote:
>
>> 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.
>>
>> On Fri, Jul 22, 2016 at 8:27 AM, Rick Wagner < <rwagner at redhat.com>
>> rwagner at redhat.com> wrote:
>>
>>> Many thanks, Jeff.
>>>
>>> We'll ask our customer to try this workaround. (We'll document it in
>>> KCS for later usage, also.)
>>>
>>> Rick
>>>
>>> On Fri, Jul 22, 2016 at 2:46 AM, Jean-Francois Maury <jmaury at redhat.com>
>>> wrote:
>>>
>>>> Rick,
>>>>
>>>> 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.
>>>> 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.
>>>>
>>>> Jeff
>>>>
>>>> On Thu, Jul 21, 2016 at 9:54 PM, Rick Wagner < <rwagner at redhat.com>
>>>> rwagner at redhat.com> wrote:
>>>>
>>>>> Hello CDK SMEs,
>>>>>
>>>>> 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:
>>>>>
>>>>> -------------------------------------------------
>>>>> 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."
>>>>> --------------------------------------------------
>>>>>
>>>>>
>>>>> 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.)
>>>>>
>>>>> A comparison of the vagrant plug-ins shows the user has the same
>>>>> versions the lab box has.
>>>>>
>>>>> The Eclipse log offers us the following. Note especially the curious
>>>>> phrase "Calls to vagrant service-manager are returning empty environments.".
>>>>>
>>>>> ------------------------------------------------------
>>>>> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:48:26.869
>>>>> !MESSAGE Unable to successfully complete a call to vagrant
>>>>> service-manager.
>>>>> !STACK 0
>>>>> java.util.concurrent.TimeoutException: Process output:
>>>>> ^[[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://10.1.2.2:2376
>>>>> 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: <https://10.1.2.2:8443/console>https://10.1.2.2:8443/console #
>>>>> To use OpenShift CLI, run: oc login <https://10.1.2.2:8443>
>>>>> https://10.1.2.2:8443 export OPENSHIFT_URL= <https://10.1.2.2:8443>
>>>>> https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=
>>>>> <https://10.1.2.2:8443/console>https://10.1.2.2:8443/console export
>>>>> DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m
>>>>> # run following command to configure your shell: # eval
>>>>> "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:185)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:174)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:154)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:133)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:250)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:242)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:235)
>>>>>
>>>>> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:49:07.139
>>>>> !MESSAGE Unable to successfully complete a call to vagrant
>>>>> service-manager.
>>>>> !STACK 0
>>>>> java.util.concurrent.TimeoutException: Process output:
>>>>> ^[[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://10.1.2.2:2376
>>>>> 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: <https://10.1.2.2:8443/console>https://10.1.2.2:8443/console #
>>>>> To use OpenShift CLI, run: oc login <https://10.1.2.2:8443>
>>>>> https://10.1.2.2:8443 export OPENSHIFT_URL= <https://10.1.2.2:8443>
>>>>> https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=
>>>>> <https://10.1.2.2:8443/console>https://10.1.2.2:8443/console export
>>>>> DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m
>>>>> # run following command to configure your shell: # eval
>>>>> "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:53)
>>>>> at
>>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:43)
>>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>>>>
>>>>> !ENTRY org.jboss.tools.openshift.cdk.server.core 4 0 2016-07-21
>>>>> 09:49:07.142
>>>>> !MESSAGE Unable to configure docker and openshift. Calls to vagrant
>>>>> service-manager are returning empty environments.
>>>>>
>>>>>
>>>>> --------------------------------------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Any suggestions are greatly appreciated.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Rick
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> [image: Inline image 2]
>>>>>
>>>>> _______________________________________________
>>>>> Devtools mailing list
>>>>> Devtools at redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/devtools
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> Devtools mailing list
>>> Devtools at redhat.com
>>> https://www.redhat.com/mailman/listinfo/devtools
>>>
>>>
>>
>> _______________________________________________
>> Devtools mailing list
>> Devtools at redhat.com
>> https://www.redhat.com/mailman/listinfo/devtools
>>
>>
>
>
> _______________________________________________
> Devtools mailing listDevtools at redhat.comhttps://www.redhat.com/mailman/listinfo/devtools
>
>
>
> _______________________________________________
> Devtools mailing list
> Devtools at redhat.com
> https://www.redhat.com/mailman/listinfo/devtools
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/devtools/attachments/20160726/15b5c0da/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 246410 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/devtools/attachments/20160726/15b5c0da/attachment.png>
More information about the Devtools
mailing list