[
https://issues.jboss.org/browse/JBIDE-22604?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-22604:
---------------------------------------
[~adietish] said:
{quote}
I suspect if adapter is not detecting status correctly, the issue must be in
VagrantPoller#parseOutput
{quote}
Alexey said we now use simply vagrant service-manager env.
This is the output after cdk launch in CDK 2.1 rc2 (where detection fails in devstudio):
{code}
$ vagrant service-manager env
# docker env:
# 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=/Users/rasp/jbossqa/cdk2.1.rc2/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
export DOCKER_TLS_VERIFY=1
export DOCKER_API_VERSION=1.21
# openshift env:
# 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
# run following command to configure your shell:
# eval "$(vagrant service-manager env)"
{code}
This is where it works (cdk 2.1.rc1):
{code}
$ vagrant service-manager env
# docker env:
# 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=/Users/rasp/jbossqa/cdk2.1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
export DOCKER_TLS_VERIFY=1
export DOCKER_API_VERSION=1.21
# openshift env:
# 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
# run following command to configure your shell:
# eval "$(vagrant service-manager env)"
{code}
Seems exactly the same, so it must be something else...
CDK server adapter stuck at starting
------------------------------------
Key: JBIDE-22604
URL:
https://issues.jboss.org/browse/JBIDE-22604
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.4.0.Final
Environment: development-suite-1.0.0-GA-20160615-188-bundle-installer.exe
devstudio 10.0.0.GA-a
CDK 2.1.RC3
Reporter: Jan Richter
Assignee: Rob Stryker
Priority: Blocker
I have installed the development suite using the all-in-1 installer (on 3 different
windows machines now). Every time I try to start CDK using the server adapter it gets
stuck on 'starting'.
In fact the CDK does start up, openshift is running, but no connection is created + the
server adapter is marked as starting and the job (starting CDK) is spinning until it hits
the timeout.
Strange thing is - stopping the job/server adapter at this point will first create the
desired openshift connection and then CDK wil stop.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)