[JBoss JIRA] (JBIDE-22201) Error contacting OpenShift after CDK is started

Wednesday, 20 April 2016

    [
https://issues.jboss.org/browse/JBIDE-22201?page=com.atlassian.jira.plugi...
] 

Hardy Ferentschik commented on JBIDE-22201:
-------------------------------------------

{quote}
You indicate that simply pasting the url into a browser shows the URL is available, so
maybe it's the case that it wasn't available when we first try to make the
connection?
{quote}
That would be my guess as well.

{quote}
As I understood it, /healthz should be 100% available once the vagrant up command
completes.
{quote}
That's not quite right. First of all, _vagrant up_ needs to complete without error. It
can also exit with an error code due to some provisioning steps not completing. In this
case OpenShift might not be up and neither is the health URL reachable. What can be said
though is, that if the health URL is reachable, OpenShift is up and running. In fact the
OpenShift service startup scripts in the CDK itself use the health URL to wait for
Opensift to successfully start.

So provided there is no bug in the service startup scripts and _vagrant up_ returns with
an exit code of 0, the health URL should indeed be reachable.

{quote}
 I was told that absolutely nothing done during vagrant up is asynchronous
{quote}
That's correct.

{quote}
or, /healthz did return but did not return "ok".
{quote}
BTW, technically I don't think it is the "ok" one should check, but the HTTP
return code. It needs to be 200, everything else should be considered an error.

...
 Error contacting OpenShift after CDK is started
 -----------------------------------------------

                 Key: JBIDE-22201
                 URL: https://issues.jboss.org/browse/JBIDE-22201
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: cdk, openshift
    Affects Versions: 4.3.1.Final
            Reporter: Martin Malina
            Assignee: Rob Stryker
            Priority: Blocker

 Today Marian and I started seeing this issue: When we start CDK, it will start and
everything seems to work, but an error pops up:
 {code}
 Error contacting OpenShift

org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller$OpenShiftNotReadyPollingException:
The CDK VM is up and running, but OpenShift is unreachable at url
https://10.1.2.2:8443/healthz/ready
 	at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:209)
 	at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:186)
 	at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:170)
 	at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:150)
 	at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:129)
 	at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:248)
 	at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:240)
 	at
org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:233)
 {code}
 When you actually copy&paste that url into a browser, you will get "ok".
 This happens to me on OS X with CDK 2.0 CR3 (the latest build). Marian is on Linux
(Fedora 22). 

--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006