[
https://issues.jboss.org/browse/JBIDE-22609?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-22609:
-------------------------------------
Unfortunately, we have no real way to recognize that the credentials are wrong. Once the
vagrant up process completes, we do a vagrant status. vagrant status tells us the VM is
"running".
As far as I can tell, this is functioning as intended. It properly displays an error as
expected, warns them that the openshift is unreachable, etc.
The only thing I could reasonably see here is to change the error message in the dialog?
Provided wrong credentials, CDK server adapter says
"started" even though it is not.
------------------------------------------------------------------------------------
Key: JBIDE-22609
URL:
https://issues.jboss.org/browse/JBIDE-22609
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.4.0.Final
Environment: Devstudio 10.0.0.GA (B33), CDK 2.1.RC4, Windows 10
Reporter: Radim Hopp
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.4.x
When CDK startup fails when it is provided wrong credentials (it fails on
vagrant-registration), CDK server adapter sets its state to "started" and OS3
connection is created (even though OS3 is not running in vagrant) with some weird IP
(10.0.2.15). Also error pops up saying "The CDK VM is up and running, but OpenShift
is unreachable at url
https://10.0.2.15:8443/healthz/ready". I really don't know
where this IP comes from. I was able to reproduce it on Fedora using libvirt box and the
IP was something like (192.168.x.x)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)