[JBoss JIRA] (JBIDE-26251) Cannot start OpenShift server adapter in Debug
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26251?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-26251:
---------------------------------------
[~adietish] yes, it is not for respin, but we should look at it in AM2 sprint.
> Cannot start OpenShift server adapter in Debug
> ----------------------------------------------
>
> Key: JBIDE-26251
> URL: https://issues.jboss.org/browse/JBIDE-26251
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM1
> Environment: CDK
> F28
> oc client 3.11 alpha - build from master
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.9.0.AM2
>
>
> {code:java}
> eclipse.buildId=12.9.0.AM1-v20180726-1026-B3091
> java.version=1.8.0_181
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B3091_testing/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Mon Jul 30 12:53:55 CEST 2018
> Could not launch server eap-app (Service) at OpenShift 3 (192.168.42.218)
> com.openshift.restclient.OpenShiftException: 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).
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.checkProcessIsAlive(AbstractOpenShiftBinaryCapability.java:219)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.startProcess(AbstractOpenShiftBinaryCapability.java:182)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:176)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:112)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1$1.runOCBinary(PortForwardingUtils.java:148)
> at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:29)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:150)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:142)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:366)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:267)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:111)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:90)
> 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:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712)
> 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:60)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (JBIDE-26251) Cannot start OpenShift server adapter in Debug
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26251?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-26251 at 7/30/18 6:34 PM:
-------------------------------------------------------------------
[~jkopriva] this looks serious. But then, since 3.11 isn't released yet, I dont think that this would justify a respin of AM1. I'll therefore bump the fixVersion to AM2
was (Author: adietish):
[~jkopriva] this looks serious. But then, since 3.11 isn't released yet, I dont think that this would justify a respin of AM1.
> Cannot start OpenShift server adapter in Debug
> ----------------------------------------------
>
> Key: JBIDE-26251
> URL: https://issues.jboss.org/browse/JBIDE-26251
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM1
> Environment: CDK
> F28
> oc client 3.11 alpha - build from master
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.9.0.AM2
>
>
> {code:java}
> eclipse.buildId=12.9.0.AM1-v20180726-1026-B3091
> java.version=1.8.0_181
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B3091_testing/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Mon Jul 30 12:53:55 CEST 2018
> Could not launch server eap-app (Service) at OpenShift 3 (192.168.42.218)
> com.openshift.restclient.OpenShiftException: 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).
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.checkProcessIsAlive(AbstractOpenShiftBinaryCapability.java:219)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.startProcess(AbstractOpenShiftBinaryCapability.java:182)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:176)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:112)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1$1.runOCBinary(PortForwardingUtils.java:148)
> at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:29)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:150)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:142)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:366)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:267)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:111)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:90)
> 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:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712)
> 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:60)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (JBIDE-26251) Cannot start OpenShift server adapter in Debug
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26251?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26251:
-------------------------------------
Sprint: devex #153 August 2019
> Cannot start OpenShift server adapter in Debug
> ----------------------------------------------
>
> Key: JBIDE-26251
> URL: https://issues.jboss.org/browse/JBIDE-26251
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM1
> Environment: CDK
> F28
> oc client 3.11 alpha - build from master
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.9.0.AM2
>
>
> {code:java}
> eclipse.buildId=12.9.0.AM1-v20180726-1026-B3091
> java.version=1.8.0_181
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B3091_testing/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Mon Jul 30 12:53:55 CEST 2018
> Could not launch server eap-app (Service) at OpenShift 3 (192.168.42.218)
> com.openshift.restclient.OpenShiftException: 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).
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.checkProcessIsAlive(AbstractOpenShiftBinaryCapability.java:219)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.startProcess(AbstractOpenShiftBinaryCapability.java:182)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:176)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:112)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1$1.runOCBinary(PortForwardingUtils.java:148)
> at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:29)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:150)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:142)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:366)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:267)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:111)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:90)
> 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:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712)
> 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:60)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (JBIDE-26251) Cannot start OpenShift server adapter in Debug
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26251?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26251:
------------------------------------------
[~jkopriva] this looks serious. But then, since 3.11 isn't released yet, I dont think that this would justify a respin of AM1.
> Cannot start OpenShift server adapter in Debug
> ----------------------------------------------
>
> Key: JBIDE-26251
> URL: https://issues.jboss.org/browse/JBIDE-26251
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM1
> Environment: CDK
> F28
> oc client 3.11 alpha - build from master
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.9.0.AM2
>
>
> {code:java}
> eclipse.buildId=12.9.0.AM1-v20180726-1026-B3091
> java.version=1.8.0_181
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B3091_testing/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Mon Jul 30 12:53:55 CEST 2018
> Could not launch server eap-app (Service) at OpenShift 3 (192.168.42.218)
> com.openshift.restclient.OpenShiftException: 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).
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.checkProcessIsAlive(AbstractOpenShiftBinaryCapability.java:219)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.startProcess(AbstractOpenShiftBinaryCapability.java:182)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:176)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:112)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1$1.runOCBinary(PortForwardingUtils.java:148)
> at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:29)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:150)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:142)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:366)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:267)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:111)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:90)
> 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:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712)
> 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:60)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (JBIDE-26251) Cannot start OpenShift server adapter in Debug
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26251?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26251:
-------------------------------------
Fix Version/s: 4.9.0.AM2
(was: 4.9.0.AM1)
> Cannot start OpenShift server adapter in Debug
> ----------------------------------------------
>
> Key: JBIDE-26251
> URL: https://issues.jboss.org/browse/JBIDE-26251
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.AM1
> Environment: CDK
> F28
> oc client 3.11 alpha - build from master
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.9.0.AM2
>
>
> {code:java}
> eclipse.buildId=12.9.0.AM1-v20180726-1026-B3091
> java.version=1.8.0_181
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B3091_testing/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Mon Jul 30 12:53:55 CEST 2018
> Could not launch server eap-app (Service) at OpenShift 3 (192.168.42.218)
> com.openshift.restclient.OpenShiftException: 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).
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.checkProcessIsAlive(AbstractOpenShiftBinaryCapability.java:219)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.startProcess(AbstractOpenShiftBinaryCapability.java:182)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:176)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:112)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1$1.runOCBinary(PortForwardingUtils.java:148)
> at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:29)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:150)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:142)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:366)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:267)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:111)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:90)
> 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:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712)
> 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:60)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months