[jbosstools-issues] [JBoss JIRA] (JBIDE-22818) vagrant service-manager call experiences timeout after output

[Rob Stryker (JIRA)]

Rob Stryker created JBIDE-22818:
-----------------------------------

             Summary:  vagrant service-manager call experiences timeout after output
                 Key: JBIDE-22818
                 URL: https://issues.jboss.org/browse/JBIDE-22818
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: cdk
    Affects Versions: 4.4.1.AM2
            Reporter: Rob Stryker



!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)




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)