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

[Andreas Gajdosik (JIRA)]

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

Andreas Gajdosik commented on JBIDE-26333:
------------------------------------------


{noformat}
error: The server uses a certificate signed by unknown authority. You may need to use the --certificate-authority flag to provide the path to a certificate file for the certificate authority, or --insecure-skip-tls-verify to bypass the certificate check and use insecure connections.

Could not set oc CLI context for 'minishift' profile: Error during setting 'minishift' as active profile: Unable to login to cluster
{noformat}


[~lalatendum] maybe we should be more explicit when printing out oc/docker errors. Here it is really unclear whether it is reported by Minishift/CDK and thus --insecure-skip-tls-verify should be used, or whether it goes from oc or docker? WDYT?


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