[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)
5 years, 9 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)
5 years, 9 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)
5 years, 9 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)
5 years, 9 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)
5 years, 9 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 updated JBIDE-26324:
-------------------------------------
Fix Version/s: 4.9.0.AM3
> 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
> 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)
5 years, 9 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 resolved JBIDE-26324.
--------------------------------------
Assignee: Andre Dietisheim
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
> 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)
5 years, 9 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 updated JBIDE-26324:
-------------------------------------
Labels: debugging port_forwarding server_adapter (was: )
> 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)
5 years, 9 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 commented on JBIDE-26324:
------------------------------------------
[~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
> 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)
5 years, 9 months
[JBoss JIRA] (JBIDE-26323) Add JBoss Tools 4.9.0.AM1 to list of releases on tools.jboss.org
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26323?page=com.atlassian.jira.plugi... ]
Jeff MAURY edited comment on JBIDE-26323 at 8/29/18 7:04 AM:
-------------------------------------------------------------
My only concern is to remove the wrong message 4.9.0.AM1 Coming soon. So I created a new entry for 4.9.0.AM1 but without downloadable files so that the message is now removed. See my PR
was (Author: jeffmaury):
My only concern is to remove the wrong message 4.9.0.AM1 Coming soon. So I created a new entry for 4.9.0.AM1 but without downloadable files so that the message is not removed. See my PR
> Add JBoss Tools 4.9.0.AM1 to list of releases on tools.jboss.org
> ----------------------------------------------------------------
>
> Key: JBIDE-26323
> URL: https://issues.jboss.org/browse/JBIDE-26323
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: website
> Affects Versions: 4.9.0.AM1
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Fix For: 4.9.0.AM3
>
> Attachments: screenshot-1.png
>
>
> I noticed 4.9.0.AM1 was not defined in website causing this release to appear as 'Coming soon' even after 4.9.0.AM2 is out.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 9 months