[
https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugi...
]
Marián Labuda updated JBIDE-21920:
----------------------------------
Description:
After latest update of nightly JBT I am not able to get logs from pods(/builds). Because
there is something wrong with setting oc path. When I set path on OpenShift 3 preference
page to be pointing to correct oc binary, following e.g. getting log from pod results in
showing following message in console
{code}
The OpenShift 'oc' binary location was not specified. Set the property
openshift.restclient.oc.location
{code}
There is no stack trace available for this error in error log.
was:
After latest update of nightly JBT I am not able to get logs from pods(/builds) or work
with server adapter, because there is something wrong with setting oc path. When I set
path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g.
getting log from pod results in showing following message in console
{code}
The OpenShift 'oc' binary location was not specified. Set the property
openshift.restclient.oc.location
{code}
There is no stack trace available for this error in error log.
Cannot show logs from pods
--------------------------
Key: JBIDE-21920
URL:
https://issues.jboss.org/browse/JBIDE-21920
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Assignee: Fred Bricon
Priority: Blocker
Labels: openshift_v3
Fix For: 4.3.1.CR1
After latest update of nightly JBT I am not able to get logs from pods(/builds). Because
there is something wrong with setting oc path. When I set path on OpenShift 3 preference
page to be pointing to correct oc binary, following e.g. getting log from pod results in
showing following message in console
{code}
The OpenShift 'oc' binary location was not specified. Set the property
openshift.restclient.oc.location
{code}
There is no stack trace available for this error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)