[
https://issues.jboss.org/browse/JBIDE-22609?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-22609:
-------------------------------------
You could at least use the return code?
Unfortunately, here, if I use the return code and set the server to stopped, it will then
conflict with the underlying vagrant status, which says the vm is "running".
So if we have our status as server is 'stopped' while vagrant says
'running', the next attempt to start the cdk will simply set it to started
immediately or fail with the same error (that openshift is unreachable).
I can work on changing the error message, but that's about it.
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)