-
Bug
-
Resolution: Won't Do
-
Major
-
4.4.1.AM1
-
None
When you start CDK with wrong credentials, service manager will return this strange IP:
# 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)"
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.
- relates to
-
JBIDE-22609 Provided wrong credentials, CDK server adapter says "started" even though it is not.
- Closed