[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:all-tabpanel ]

Marián Labuda updated JBIDE-21920:
----------------------------------
    Description: 
After latest update of nightly JBT I am not able to get logs from pods(/builds) or use port forwarding . 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.

But when using port forwading, there is an error with following stack
{code}
com.openshift.restclient.capability.resources.LocationNotFoundException: The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
	at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.getOpenShiftBinaryLocation(AbstractOpenShiftBinaryCapability.java:189)
	at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:123)
	at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:66)
	at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:128)
	at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
	at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91)
	at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:124)
	at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardModel.startPortForwarding(PortForwardingWizardModel.java:110)
	at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardPage$3$1.run(PortForwardingWizardPage.java:157)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

{code}

  was:
After latest update of nightly JBT I am not able to get logs from pods(/builds) or use port forwarding (wizard is opened but starting throws an error with message as seen below). 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 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
>            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) or use port forwarding . 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.
> But when using port forwading, there is an error with following stack
> {code}
> com.openshift.restclient.capability.resources.LocationNotFoundException: The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
> 	at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.getOpenShiftBinaryLocation(AbstractOpenShiftBinaryCapability.java:189)
> 	at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:123)
> 	at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:66)
> 	at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:128)
> 	at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
> 	at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91)
> 	at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:124)
> 	at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardModel.startPortForwarding(PortForwardingWizardModel.java:110)
> 	at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardPage$3$1.run(PortForwardingWizardPage.java:157)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}



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