[jbosstools-issues] [JBoss JIRA] (JBIDE-22725) Provided wrong credentials, CDK adapter creates openshift connection with a strange IP

[Martin Malina (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-22725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina closed JBIDE-22725.
---------------------------------


I think most importantly this was related to vagrant, hence cdk 2, so it's outdated. I have seen something similar with cdk 3 where cdk didn't start correctly and there was a strange ip address used for the openshift connection (and it didn't work), but it seemed to be an odd one-off failure - I don't know how to reproduce. Closing this issue.

> Provided wrong credentials, CDK adapter creates openshift connection with a strange IP
> --------------------------------------------------------------------------------------
>
>                 Key: JBIDE-22725
>                 URL: https://issues.jboss.org/browse/JBIDE-22725
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk, upstream
>    Affects Versions: 4.4.1.AM1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.5.3.Final
>
>
> When you start CDK with wrong credentials, service manager will return this strange IP:
> {code}
> # docker env:
> # Copying TLS certificates to /Users/rasp/jbossqa/cdk2.1/cdk2.1.rc5/components/rhel/misc/shared_folder/rhel-ose/.vagrant/machines/default/virtualbox/docker
> # Set the following environment variables to enable access to the docker daemon running inside of the vagrant virtual machine:
> export DOCKER_HOST=tcp://10.0.2.15:2376
> export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk2.1/cdk2.1.rc5/components/rhel/misc/shared_folder/rhel-ose/.vagrant/machines/default/virtualbox/docker
> export DOCKER_TLS_VERIFY=1
> export DOCKER_API_VERSION=1.21
> # run following command to configure your shell:
> # eval "$(vagrant service-manager env)"
> {code}
> This has been reported upstream here:
> https://github.com/projectatomic/vagrant-service-manager/issues/299
> Let's use this JIRA to track the upstream issue.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)