]
Hardy Ferentschik commented on JBIDE-22201:
-------------------------------------------
{quote}
FYI, I was able to fix this by removing .vagrant in the Vagrantfile directory.
{quote}
Hmm, that does not sounds like a fix. The _.vagrant_ directory contains metadata of the
running VM. Among other things it also contains the Docker certs to connect to the Docker
daemon. Removing it while the VM is running does not sounds like a good idea to me.
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).