[jbosstools-issues] [JBoss JIRA] (JBIDE-21920) Cannot use features which are using oc binary

[Marián Labuda (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179824#comment-13179824 ] 

Marián Labuda commented on JBIDE-21920:
---------------------------------------

I am running latest nightly build of JBT (B240).
ASSERT: Have an OpenShift 3 connection in OpenShift explorer view.
EXEC: Create a new application on the connection.
ASSERT: Application is running and there is application pod.
EXEC: Set path to oc binary in OpenShift 3 preference page.
EXEC: Try to open application pod logs via context menu of application pod in OpenShift Explorer view.

RESULT: Error message is shown in console and no pod log is displayed.
EXPECTED RESULT: Pod log is shown in console.

> Cannot use features which are using oc binary
> ---------------------------------------------
>
>                 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
>            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) 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.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)