[
https://issues.jboss.org/browse/JBIDE-22725?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-22725.
---------------------------------
Resolution: Won't Fix
The upstream issue indicates that the IP is correct, its just that the cdk did not
properly expose the IP due to registration failure.
No work has been done on the issue specifically, nor on
https://github.com/projectatomic/adb-vagrant-registration generally, in about a year to a
year and a half. I do not expect this to be fixed. Closing.
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)