[JBoss JIRA] (JBIDE-26327) Server adapter: NPE when stopping a server adapter whose workspace project was deleted
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26327?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-26327:
----------------------------------------
Assignee: (was: Andre Dietisheim)
> Server adapter: NPE when stopping a server adapter whose workspace project was deleted
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-26327
> URL: https://issues.jboss.org/browse/JBIDE-26327
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM2
> Reporter: Andre Dietisheim
> Labels: server_adapter
> Fix For: 4.9.0.Final
>
> Attachments: image-2018-08-29-15-09-38-939.png
>
>
> steps:
> # ASSERT: have a workspace project, a running OpenShift application and a server adapter started for the 2
> # EXEC: delete the workspace project
> # EXEC: delete the server adapter, making sure that you have the checkbox for stopping the adapter beforehand checked
> Result:
> An NPE occurrs
> !image-2018-08-29-15-09-38-939.png!
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftShutdownController.updateProject(OpenShiftShutdownController.java:71)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftShutdownController.stop(OpenShiftShutdownController.java:58)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:255)
> at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3698)
> at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3655)
> at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:413)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26327) Server adapter: NPE when stopping a server adapter whose workspace project was deleted
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26327?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26327:
-------------------------------------
Labels: server_adapter (was: )
> Server adapter: NPE when stopping a server adapter whose workspace project was deleted
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-26327
> URL: https://issues.jboss.org/browse/JBIDE-26327
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM2
> Reporter: Andre Dietisheim
> Labels: server_adapter
> Fix For: 4.9.0.Final
>
> Attachments: image-2018-08-29-15-09-38-939.png
>
>
> steps:
> # ASSERT: have a workspace project, a running OpenShift application and a server adapter started for the 2
> # EXEC: delete the workspace project
> # EXEC: delete the server adapter, making sure that you have the checkbox for stopping the adapter beforehand checked
> Result:
> An NPE occurrs
> !image-2018-08-29-15-09-38-939.png!
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftShutdownController.updateProject(OpenShiftShutdownController.java:71)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftShutdownController.stop(OpenShiftShutdownController.java:58)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:255)
> at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3698)
> at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3655)
> at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:413)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26326) Server adapter: Show In > Console does nothing
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-26326:
----------------------------------------
Summary: Server adapter: Show In > Console does nothing
Key: JBIDE-26326
URL: https://issues.jboss.org/browse/JBIDE-26326
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.9.0.AM2
Reporter: Andre Dietisheim
Fix For: 4.9.x
steps:
# ASSERT: have an OpenShift server adapter started
# EXEC: in the ctx menu for your adapter: pick Show In > Console
Result:
Nothing happens
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-23567) Integration tests global refactoring
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23567?page=com.atlassian.jira.plugi... ]
Pavol Srna reassigned JBIDE-23567:
----------------------------------
Assignee: Pavol Srna (was: Jeff MAURY)
> Integration tests global refactoring
> ------------------------------------
>
> Key: JBIDE-23567
> URL: https://issues.jboss.org/browse/JBIDE-23567
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests
> Reporter: Jeff MAURY
> Assignee: Pavol Srna
> Labels: integration-test, integration_tests
> Fix For: 4.9.x
>
>
> We should done some work on integration tests so that we can rely on them to improve our code quality and reduce the technical debt.
> A sprint will be dedicated.
> Here are the tasks we should work on:
> * run tests from Maven and document how to run them if specific steps are required
> * If failure, fix the failed tests
> * Refactor / move tests to the components repository
> * Fix/make sure tests are run in PR check
> This huge task should be done component per component. Sub-tasks JIRA will be created for each component.
> You can use this document as a starting point:[https://docs.google.com/document/d/1bl8pJ2aW65UpyGpr3qxoAUREDWL26N...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26324) Port forwarding failed for JBoss Tools 4.6.0.Final
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26324?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-26324.
------------------------------------
Resolution: Duplicate Issue
> Port forwarding failed for JBoss Tools 4.6.0.Final
> --------------------------------------------------
>
> Key: JBIDE-26324
> URL: https://issues.jboss.org/browse/JBIDE-26324
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.Final
> Environment: JBoss Tools 4.6.0.Final
> $ oc version
> oc v3.11.0-0.24.0
> kubernetes v1.11.0+d4cacc0
> features: Basic-Auth GSSAPI Kerberos SPNEGO
> Reporter: Junqi Zhao
> Assignee: Andre Dietisheim
> Labels: debugging, port_forwarding, server_adapter
> Fix For: 4.9.0.AM3
>
> Attachments: port_forward.png
>
>
> Port forwarding failed for JBoss Tools 4.6.0.Final
> error is in the followings, the failed reason is flag "-p" is deprecated
> An internal error occurred during: "Starting port forwarding...".
> OpenShiftBinaryCapability process exited: Error: unknown shorthand flag: 'p' in -p
> Usage:
> oc port-forward TYPE/NAME [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags]
> Examples:
> # Listens on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod
> oc port-forward mypod 5000 6000
>
> # Listens on port 8888 locally, forwarding to 5000 in the pod
> oc port-forward mypod 8888:5000
>
> # Listens on a random port locally, forwarding to 5000 in the pod
> oc port-forward mypod :5000
>
> # Listens on a random port locally, forwarding to 5000 in the pod
> oc port-forward mypod 0:5000
> Options:
> --pod-running-timeout=1m0s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running
> Use "oc options" for a list of global command-line options (applies to all commands).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26324) Port forwarding failed for JBoss Tools 4.6.0.Final
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26324?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-26324 at 8/29/18 8:30 AM:
-------------------------------------------------------------------
[~juzhao] thx for reporting. This is a known issue when using oc >= 3.11. We discovered this in JBIDE-26251 and fixed this in JBoss Tools 4.9.0.AM2.
You can avoid this bug by using
* oc < 3.11
* JBoss Tools 4.9.0.AM2
Please feel free to reopen this issue the above doesn't work for you.
was (Author: adietish):
[~juzhao] thx for reporting. This is a known issue when using oc >= 3.11. We discovered this in JBIDE-26251 and fixed this in JBoss Tools 4.9.0.AM2.
You can avoid this bug by using
* oc < 3.11
* JBoss Tools 4.9.0.AM2
Please feel free to reopen this issue the above doesn't work for you.
> Port forwarding failed for JBoss Tools 4.6.0.Final
> --------------------------------------------------
>
> Key: JBIDE-26324
> URL: https://issues.jboss.org/browse/JBIDE-26324
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.Final
> Environment: JBoss Tools 4.6.0.Final
> $ oc version
> oc v3.11.0-0.24.0
> kubernetes v1.11.0+d4cacc0
> features: Basic-Auth GSSAPI Kerberos SPNEGO
> Reporter: Junqi Zhao
> Assignee: Andre Dietisheim
> Labels: debugging, port_forwarding, server_adapter
> Fix For: 4.9.0.AM3
>
> Attachments: port_forward.png
>
>
> Port forwarding failed for JBoss Tools 4.6.0.Final
> error is in the followings, the failed reason is flag "-p" is deprecated
> An internal error occurred during: "Starting port forwarding...".
> OpenShiftBinaryCapability process exited: Error: unknown shorthand flag: 'p' in -p
> Usage:
> oc port-forward TYPE/NAME [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags]
> Examples:
> # Listens on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod
> oc port-forward mypod 5000 6000
>
> # Listens on port 8888 locally, forwarding to 5000 in the pod
> oc port-forward mypod 8888:5000
>
> # Listens on a random port locally, forwarding to 5000 in the pod
> oc port-forward mypod :5000
>
> # Listens on a random port locally, forwarding to 5000 in the pod
> oc port-forward mypod 0:5000
> Options:
> --pod-running-timeout=1m0s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running
> Use "oc options" for a list of global command-line options (applies to all commands).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26324) Port forwarding failed for JBoss Tools 4.6.0.Final
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26324?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-26324.
------------------------------------
Resolution: Done
> Port forwarding failed for JBoss Tools 4.6.0.Final
> --------------------------------------------------
>
> Key: JBIDE-26324
> URL: https://issues.jboss.org/browse/JBIDE-26324
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.Final
> Environment: JBoss Tools 4.6.0.Final
> $ oc version
> oc v3.11.0-0.24.0
> kubernetes v1.11.0+d4cacc0
> features: Basic-Auth GSSAPI Kerberos SPNEGO
> Reporter: Junqi Zhao
> Assignee: Andre Dietisheim
> Labels: debugging, port_forwarding, server_adapter
> Fix For: 4.9.0.AM3
>
> Attachments: port_forward.png
>
>
> Port forwarding failed for JBoss Tools 4.6.0.Final
> error is in the followings, the failed reason is flag "-p" is deprecated
> An internal error occurred during: "Starting port forwarding...".
> OpenShiftBinaryCapability process exited: Error: unknown shorthand flag: 'p' in -p
> Usage:
> oc port-forward TYPE/NAME [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags]
> Examples:
> # Listens on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod
> oc port-forward mypod 5000 6000
>
> # Listens on port 8888 locally, forwarding to 5000 in the pod
> oc port-forward mypod 8888:5000
>
> # Listens on a random port locally, forwarding to 5000 in the pod
> oc port-forward mypod :5000
>
> # Listens on a random port locally, forwarding to 5000 in the pod
> oc port-forward mypod 0:5000
> Options:
> --pod-running-timeout=1m0s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running
> Use "oc options" for a list of global command-line options (applies to all commands).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26324) Port forwarding failed for JBoss Tools 4.6.0.Final
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26324?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-26324 at 8/29/18 8:30 AM:
-------------------------------------------------------------------
[~juzhao] thx for reporting. This is a known issue when using oc >= 3.11. We discovered this in JBIDE-26251 and fixed this in JBoss Tools 4.9.0.AM2.
You can avoid this bug by using
* oc < 3.11
* JBoss Tools 4.9.0.AM2
Please feel free to reopen this issue the above doesn't work for you.
was (Author: adietish):
[~juzhao] thx for reporting. This is a known issue when using oc >= 3.11. We discovered this in JBIDE-26251 and fixed this in JBoss Tools 4.9.0.AM2.
Please feel free to reopen this issue if it still doesn't work for you in JBoss Tools 4.9.0.AM2.
> Port forwarding failed for JBoss Tools 4.6.0.Final
> --------------------------------------------------
>
> Key: JBIDE-26324
> URL: https://issues.jboss.org/browse/JBIDE-26324
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.Final
> Environment: JBoss Tools 4.6.0.Final
> $ oc version
> oc v3.11.0-0.24.0
> kubernetes v1.11.0+d4cacc0
> features: Basic-Auth GSSAPI Kerberos SPNEGO
> Reporter: Junqi Zhao
> Assignee: Andre Dietisheim
> Labels: debugging, port_forwarding, server_adapter
> Fix For: 4.9.0.AM3
>
> Attachments: port_forward.png
>
>
> Port forwarding failed for JBoss Tools 4.6.0.Final
> error is in the followings, the failed reason is flag "-p" is deprecated
> An internal error occurred during: "Starting port forwarding...".
> OpenShiftBinaryCapability process exited: Error: unknown shorthand flag: 'p' in -p
> Usage:
> oc port-forward TYPE/NAME [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags]
> Examples:
> # Listens on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod
> oc port-forward mypod 5000 6000
>
> # Listens on port 8888 locally, forwarding to 5000 in the pod
> oc port-forward mypod 8888:5000
>
> # Listens on a random port locally, forwarding to 5000 in the pod
> oc port-forward mypod :5000
>
> # Listens on a random port locally, forwarding to 5000 in the pod
> oc port-forward mypod 0:5000
> Options:
> --pod-running-timeout=1m0s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running
> Use "oc options" for a list of global command-line options (applies to all commands).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months
[JBoss JIRA] (JBIDE-26324) Port forwarding failed for JBoss Tools 4.6.0.Final
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26324?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-26324.
------------------------------------
> Port forwarding failed for JBoss Tools 4.6.0.Final
> --------------------------------------------------
>
> Key: JBIDE-26324
> URL: https://issues.jboss.org/browse/JBIDE-26324
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.Final
> Environment: JBoss Tools 4.6.0.Final
> $ oc version
> oc v3.11.0-0.24.0
> kubernetes v1.11.0+d4cacc0
> features: Basic-Auth GSSAPI Kerberos SPNEGO
> Reporter: Junqi Zhao
> Assignee: Andre Dietisheim
> Labels: debugging, port_forwarding, server_adapter
> Fix For: 4.9.0.AM3
>
> Attachments: port_forward.png
>
>
> Port forwarding failed for JBoss Tools 4.6.0.Final
> error is in the followings, the failed reason is flag "-p" is deprecated
> An internal error occurred during: "Starting port forwarding...".
> OpenShiftBinaryCapability process exited: Error: unknown shorthand flag: 'p' in -p
> Usage:
> oc port-forward TYPE/NAME [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags]
> Examples:
> # Listens on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod
> oc port-forward mypod 5000 6000
>
> # Listens on port 8888 locally, forwarding to 5000 in the pod
> oc port-forward mypod 8888:5000
>
> # Listens on a random port locally, forwarding to 5000 in the pod
> oc port-forward mypod :5000
>
> # Listens on a random port locally, forwarding to 5000 in the pod
> oc port-forward mypod 0:5000
> Options:
> --pod-running-timeout=1m0s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running
> Use "oc options" for a list of global command-line options (applies to all commands).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 4 months