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

[Jeff MAURY (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289168#comment-13289168 ] 

Jeff MAURY commented on JBIDE-22725:
------------------------------------

I add also something weird: if after the first vagrant up I run vagrant destro, I have the following output:

C:\Apps\cdk2.1\components\rhel\rhel-ose>vagrant halt
The VirtualBox VM was created with a user that doesn't match the
current user running Vagrant. VirtualBox requires that the same user
be used to manage the VM that was created. Please re-run Vagrant with
that user. This is not a Vagrant issue.

The UID used to create the VM was: 0
Your UID is: 1001

The only way to get rid is to delete the VM using VirtualBox

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