[jbosstools-issues] [JBoss JIRA] (JBIDE-26333) CDK server adapter: errror while creating Openshift connection after start of CDK 3.6 server adapter

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim edited comment on JBIDE-26333 at 9/4/18 9:59 AM:
------------------------------------------------------------------

https://192.168.64.53:8443/healthz/ready seems gone. https://docs.openshift.com/container-platform/3.9/day_two_guide/environment_health_checks.html is referring to /version and /healthz which both respond with *OK 200*, the former with a body, the latter without it.
It looks like we have to switch our health check in 
{code:title=com.openshift.internal.restclient.DefaultClient#getServerReadyStatus}
   @Override
    public String getServerReadyStatus() {
        try {
            Request request = new Request.Builder().url(new URL(this.baseUrl, "healthz/ready"))
                    .header(PROPERTY_ACCEPT, "*/*").build();
            try (Response response = client.newCall(request).execute()) {
                return response.body().string();
            }
        } catch (IOException e) {
            throw new OpenShiftException(e,
                    "Exception while trying to determine the health/ready response of the server");
        }
    }
{code}
to use the new url at */healthz*


was (Author: adietish):
[~jcantrill] do you know if OpenShift 3.10 still has a health url, https://192.168.64.53:8443/healthz/ready (that we used so far) seems gone?

> CDK server adapter: errror while creating Openshift connection after start of CDK 3.6 server adapter
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-26333
>                 URL: https://issues.jboss.org/browse/JBIDE-26333
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk, openshift
>    Affects Versions: 4.9.0.AM3
>            Reporter: Ondrej Dockal
>            Assignee: Andre Dietisheim
>              Labels: cdk_server_adapter
>             Fix For: 4.9.0.Final
>
>         Attachments: CDKStartupOSconnError.gif, screenshot-1.png
>
>
> I am watching error being thrown just after cdk server adapter is created and OS untrusted ssl cert. accepted. Also, this throws an Error dialog (making itests to fail). 
> {code}
> null
> org.jboss.tools.openshift.cdk.server
> Error
> Sun Sep 02 20:16:37 CEST 2018
> Error contacting OpenShift
> org.jboss.tools.openshift.internal.cdk.server.core.adapter.OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://192.168.42.235:8443. The VM may not have been registered successfully. Please check your console output for more information
> 	at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.checkOpenShiftHealth(MinishiftPoller.java:145)
> 	at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.checkOpenShiftHealth(MinishiftPoller.java:124)
> 	at org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.onePing(MinishiftPoller.java:79)
> 	at org.jboss.tools.openshift.internal.cdk.server.core.adapter.AbstractCDKPoller.onePingSafe(AbstractCDKPoller.java:90)
> 	at org.jboss.tools.openshift.internal.cdk.server.core.adapter.AbstractCDKPoller.getCurrentStateSynchronous(AbstractCDKPoller.java:78)
> 	at org.jboss.tools.openshift.internal.cdk.server.core.adapter.controllers.AbstractCDKLaunchController.handleProcessTerminated(AbstractCDKLaunchController.java:232)
> 	at org.jboss.tools.openshift.internal.cdk.server.core.adapter.controllers.AbstractCDKLaunchController$4.run(AbstractCDKLaunchController.java:188)
> {code}



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)