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

Viacheslav Kabanovich (JIRA) issues at jboss.org
Mon Mar 21 10:01:00 EDT 2016


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

Viacheslav Kabanovich commented on JBIDE-21920:
-----------------------------------------------

We set in preferences property
{code}
IOpenShiftCoreConstants.OPENSHIFT_CLI_LOC = "openshift.cli.location"
{code}
Is it not renamed into 'openshift.restclient.oc.location'?

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



More information about the jbosstools-issues mailing list