[jbosstools-issues] [JBoss JIRA] (JBIDE-25611) Server adapter: timeouts when starting into "Debug" on OpenShift Online
Andre Dietisheim (JIRA)
issues at jboss.org
Thu Jan 25 13:02:00 EST 2018
[ https://issues.jboss.org/browse/JBIDE-25611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13523413#comment-13523413 ]
Andre Dietisheim edited comment on JBIDE-25611 at 1/25/18 1:01 PM:
-------------------------------------------------------------------
[~jeffmaury] the port should be exposed in the (new) pod (not the deployment config) once you set the dc in "debug" mode via the 2 env vars (dev_mode and debug_port).
!image-2018-01-25-10-49-09-369.png!
I now switched to CDK 3.3 (from 3.2) and it behaves fine for me, exposes the debug port once the dc is in "debug" mode.
To sum up the current situtation:
|| product || versions || Status ||
| cdk 3.2 | minishift v1.7.0+204ce19, CDK v3.2.0-1 | {color:green}OK{color} |
| cdk 3.3 | OpenShift Master: v3.7.14 Kubernetes
Master: v1.7.6+a08f5eeb62 | {color:green}OK{color} |
| OpenShift Online | OpenShift Master: v3.7.23 (online version 3.6.0.32.1)
Kubernetes Master: v1.7.6+a08f5eeb62 | {color:red}NOT OK{color} |
| open.pass.redhat.com | OpenShift Master: v3.6.173.0.83
Kubernetes Master: v1.6.1+5115d708d7 | {color:green}OK{color} |
| origin 3.7.1 | openshift v3.7.1+ab0f056
kubernetes v1.7.6+a08f5eeb62 | {color:green}OK{color} |
was (Author: adietish):
[~jeffmaury] the port should be exposed in the (new) pod (not the deployment config) once you set the dc in "debug" mode via the 2 env vars (dev_mode and debug_port).
!image-2018-01-25-10-49-09-369.png!
I now switched to CDK 3.3 (from 3.2) and it behaves fine for me, exposes the debug port once the dc is in "debug" mode.
To sum up the current situtation:
|| product || versions || Status ||
| cdk 3.2 | minishift v1.7.0+204ce19, CDK v3.2.0-1 | {color:green}OK{color} |
| cdk 3.3 | OpenShift Master: v3.7.14 Kubernetes
Master: v1.7.6+a08f5eeb62 | {color:green}OK{color} |
| OpenShift Online | OpenShift Master: v3.7.23 (online version 3.6.0.32.1)
Kubernetes Master: v1.7.6+a08f5eeb62 | {color:red}NOT OK{color} |
| open.pass.redhat.com | OpenShift Master: v3.6.173.0.83
Kubernetes Master: v1.6.1+5115d708d7 | {color:green}OK{color} |
| origin 3.7.1 | openshift v3.7.1+ab0f056
kubernetes v1.7.6+a08f5eeb62 | {color:green}OK{color}
> Server adapter: timeouts when starting into "Debug" on OpenShift Online
> -----------------------------------------------------------------------
>
> Key: JBIDE-25611
> URL: https://issues.jboss.org/browse/JBIDE-25611
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.3.AM1
>
> Attachments: error-waiting-for-new-pod.png, image-2018-01-24-18-58-29-159.png, image-2018-01-25-10-49-09-369.png, pod-ports-cdk.png, pod-ports-online.png, port-missing.png
>
>
> # ASSERT: have an account on OpenShift Online
> # EXEC: create a new application via template nodejs-mongo-persistent
> # EXEC: have the project imported into the workspace and the server adapter for it created
> # ASSERT: you have a new server adapter for your app in state [stopped]
> # EXEC: start the adapter into "Debug"
> Result:
> The adapter takes a lot of time to start but wont succeed eventually. You get the following error dialog:
> !error-waiting-for-new-pod.png!
> In the Eclipse log you'll find the following:
> {code}
> org.eclipse.core.runtime.CoreException: Failed to detect new deployed Pod for nodejs-mongo-persistent
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitFor(OpenShiftDebugMode.java:403)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitForNewPod(OpenShiftDebugMode.java:395)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.getPod(OpenShiftDebugMode.java:226)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:170)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jbosstools-issues
mailing list