[jbosstools-issues] [JBoss JIRA] (JBIDE-26333) Error is thrown while creating Openshift Connection after start up of CDK server adapter
Ondrej Dockal (JIRA)
issues at jboss.org
Mon Sep 3 18:26:00 EDT 2018
[ https://issues.jboss.org/browse/JBIDE-26333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628022#comment-13628022 ]
Ondrej Dockal commented on JBIDE-26333:
---------------------------------------
Why is there a message like this "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" I have no idea. When taking a look at stack trace, it comes from cdk tooling part of openshift tools, but it originates in DefaultClient from openshift-rest-client repo as linked in above comment.
> Error is thrown while creating Openshift Connection after start up of CDK 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
> 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)
More information about the jbosstools-issues
mailing list