[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:comment-tabpanel&focusedCommentId=13288989#comment-13288989 ] 

Martin Malina commented on JBIDE-22725:
---------------------------------------

I can still reproduce it. But for that I needed to do a vagrant destroy first. When I had an existing box that was previously registered, starting without registering still resulted in correct output of service manager. But when I then did "vagrant destroy" and started again, it failed, i.e. vagrant service-manager env returned this:
{code}
$ vagrant service-manager env

# docker env:
# Copying TLS certificates to /Users/rasp/jbossqa/cdk2.2.rc3/cdk/components/rhel/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.2.rc3/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
export DOCKER_TLS_VERIFY=1
export DOCKER_API_VERSION=1.22

# run following command to configure your shell:
# eval "$(vagrant service-manager env)"
{code}
[~jeffmaury], can you try to do "vagrant destroy" first and then set wrong credentials using SUB_USERNAME and SUB_PASSWORD and then vagrant up.

> 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
>             Fix For: 4.4.x
>
>
> 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
(v6.4.11#64026)