[
https://issues.jboss.org/browse/JBIDE-26333?page=com.atlassian.jira.plugi...
]
Ondrej Dockal commented on JBIDE-26333:
---------------------------------------
[~adietish] [~lalatendum] [~agajdosi] I do agree with andre that this should not be
offered to user this way, either catch and consume exception from underlying binaries
(like oc) and offer proper explanation in own exception messages or keep context of
errors/exceptions in form of minishift error messages like "MinishiftOcException: oc
cluster up command throws an exception: 'blabla - try flag insecure-x-x blabla'
", or something like that, just my 2 cents, wdyt?
[~adietish] I can still get an excetption/error after cdk is started and functional in
devstudio (most likely as I did not tried create apps form templates in OS connection,
etc. this should be verified by at least smoke openshift itests, @jkopriva wdyt?).
As of question whether it is an Eclipse tooling problem or not I am not fully decided. It
needs to be debugged and verified if it is our problem or not, we might just need to
extend timeout? Do not know. I can also think of change in api of new version of oc...
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)