[
https://issues.jboss.org/browse/JBIDE-26204?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-26204:
-------------------------------------
Description:
steps:
# ASSERT: use the code that in the
[
PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700
# ASSERT: make sure you have an app with a pod running in OpenShift
# EXEC: open OpenShift preferences and point it to an oc in a folder that contains spaces
(ex. "~/oc binaries/3.41/oc")
# EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..."
Result:
The "Console" view shows up but nothing happens, there's no output.
was:
steps:
# ASSERT: use the code that in the
[
PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700
# ASSERT: make sure you have an app with a pod running in OpenShift
# EXEC: open OpenShift preferences and point it to a file that exist but is either not
executable or simply not an oc binary
# EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..."
Result:
The "Console" view shows up but nothing happens, there's no output.
Pod Log: empty console shows up when you use an oc whose path
contains " "
--------------------------------------------------------------------------
Key: JBIDE-26204
URL:
https://issues.jboss.org/browse/JBIDE-26204
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.6.0.Final
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.9.0.AM1
steps:
# ASSERT: use the code that in the
[
PR|https://github.com/jbosstools/jbosstools-openshift/pull/1772] for JBIDE-25700
# ASSERT: make sure you have an app with a pod running in OpenShift
# EXEC: open OpenShift preferences and point it to an oc in a folder that contains spaces
(ex. "~/oc binaries/3.41/oc")
# EXEC: in OpenShift Explorer: select the pod and pick "Pod Log..."
Result:
The "Console" view shows up but nothing happens, there's no output.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)