]
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).