[jbosstools-issues] [JBoss JIRA] (JBIDE-26562) debugging does not work for eap-cd-basic-s2i template from CRC
Andreas Gajdosik (Jira)
issues at jboss.org
Thu Feb 28 09:08:15 EST 2019
[ https://issues.jboss.org/browse/JBIDE-26562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702013#comment-13702013 ]
Andreas Gajdosik edited comment on JBIDE-26562 at 2/28/19 9:08 AM:
-------------------------------------------------------------------
[~adietish] If you mean something like this:
{code}
I0207 09:15:48.086798 8399 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
E0207 09:20:48.093349 8399 run_self_hosted.go:571] API server error: Get https://192.168.99.100:8443/healthz?timeout=32s: dial tcp 192.168.99.100:8443: connect: connection refused ()
Error: timed out waiting for the condition
{code}
then yes, this is a known issue. You can comment here: https://issues.jboss.org/browse/CDK-389 that it also affects you on Mac. However it originates from OpenShift -Origin- OKD https://github.com/openshift/origin/issues/20617 (you can also comment there to draw some attention, but I lost hope). This issue with cluster-up was reported by me on 13 Aug 2018, it has 25 participants, however it was ignored by OKD team for months and then closed with non-working fix. As karma bumerang it comes back and affects cluster-up and whole CDK, rendering it unusable for some devs.
was (Author: agajdosi):
[~adietish] If you mean something like this:
{code}
I0207 09:15:48.086798 8399 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
E0207 09:20:48.093349 8399 run_self_hosted.go:571] API server error: Get https://192.168.99.100:8443/healthz?timeout=32s: dial tcp 192.168.99.100:8443: connect: connection refused ()
Error: timed out waiting for the condition
{code}
then yes, this is a known issue. You can comment here: https://issues.jboss.org/browse/CDK-389 that it also affects you on Mac. However it originates from OpenShift -Origin- OKD https://github.com/openshift/origin/issues/20617 (you can also comment there to draw some attention, but I lost hope). This issue with cluster-up was reported by me on 13 Aug 2018, it has 25 participants, however it was ignored by OKD team for months and then closed with non-working fix. As karma bumerang it comes back and affects cluster-up and whole CDK, renders it unusable for some devs.
> debugging does not work for eap-cd-basic-s2i template from CRC
> --------------------------------------------------------------
>
> Key: JBIDE-26562
> URL: https://issues.jboss.org/browse/JBIDE-26562
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift, server
> Affects Versions: 4.11.0.AM1
> Environment: F29, devstudio AM1-v20190221-1020-B4114, CDK v3.8.0-alpha.1-1
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.11.0.Final
>
> Attachments: image-2019-02-26-10-19-19-366.png
>
>
> Restarting server adapter in debug for openshift application results in not responding job *Enabling "openshift maven profile"*: !image-2019-02-26-10-19-19-366.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jbosstools-issues
mailing list