[jbosstools-issues] [JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod
Nick Boldt (JIRA)
issues at jboss.org
Tue Aug 21 18:49:02 EDT 2018
[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622335#comment-13622335 ]
Nick Boldt commented on JBIDE-26160:
------------------------------------
[checkUnresolvedIssues.py] Slip to fixversion = *4.9.x*
> Server Adapter: erroneously stays in [Debugging] when you kill the pod
> ----------------------------------------------------------------------
>
> Key: JBIDE-26160
> URL: https://issues.jboss.org/browse/JBIDE-26160
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: server_adapter
> Fix For: 4.9.x
>
>
> steps:
> # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it
> # ASSERT: server adapter is created
> # EXEC: start the server adapter in Debugging
> # ASSERT: sever adapter is in *[Debugging, Synchronized]* state
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped
> Result:
> The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode.
> Expected result:
> Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jbosstools-issues
mailing list