Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-21428

Server adapter: cannot publish, cannot find "oc" executable

XMLWordPrintable

    • Hide
      1. ASSERT: make sure that you have an oc executable set in your preferences:
      2. ASSERT: make sure that you have a server adapter for an OpenShift 3 service
      3. EXEC: in Servers view: select "Publish" in the context menu of your server adapter

      Result:
      It wont publish, it errors because of a missing "oc" executable (even though you see it being set in the preferences).

      In the Eclipse log you can spot the following error:

      !ENTRY org.jboss.tools.openshift.core 4 0 2016-01-07 17:30:03.010
      !MESSAGE Could not sync /home/adietish/git/jboss-eap-quickstarts/kitchensink to all pods running the service docker-registry
      !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2016-01-07 17:30:03.010
      !MESSAGE The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
      
      Show
      ASSERT: make sure that you have an oc executable set in your preferences: ASSERT: make sure that you have a server adapter for an OpenShift 3 service EXEC: in Servers view: select "Publish" in the context menu of your server adapter Result: It wont publish, it errors because of a missing "oc" executable (even though you see it being set in the preferences). In the Eclipse log you can spot the following error: !ENTRY org.jboss.tools.openshift.core 4 0 2016-01-07 17:30:03.010 !MESSAGE Could not sync /home/adietish/git/jboss-eap-quickstarts/kitchensink to all pods running the service docker-registry !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2016-01-07 17:30:03.010 !MESSAGE The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location

            adietish@redhat.com André Dietisheim
            adietish@redhat.com André Dietisheim
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: