[Devtools] C/O CDK SMEs: Windows user going off the rails somewhere along the line
Jean-Francois Maury
jmaury at redhat.com
Fri Jul 22 07:46:08 UTC 2016
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> 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 # To use OpenShift CLI, run: oc login
> https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443
> export OPENSHIFT_WEB_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 # To use OpenShift CLI, run: oc login
> https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443
> export OPENSHIFT_WEB_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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/devtools/attachments/20160722/895ff98b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 246410 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/devtools/attachments/20160722/895ff98b/attachment.png>
More information about the Devtools
mailing list