[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) issues at jboss.org
Wed Sep 5 03:29:00 EDT 2018


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

Andre Dietisheim commented on JBIDE-26333:
------------------------------------------

[~rob.stryker] no doubt about that: we dont wan't to bundle several versions of the client library (already for the cost of the additional infrastructure that we'd need for that).
As far as I can see the "new" url for the health check was present since at least cdk 3.5 and the breaking change in cdk is that the url that we use(d) was deprecated/removed.
See https://github.com/openshift/openshift-restclient-java/issues/345

> 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)


More information about the jbosstools-issues mailing list