[jbosstools-issues] [JBoss JIRA] (JBIDE-21626) Pod is not created when docker image is deployed to OpenShift

[Jeff Cantrill (JIRA)]

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

Jeff Cantrill commented on JBIDE-21626:
---------------------------------------

[~fbricon] [~adietish][~maxandersen] These changes I think smooth out the experience.  It allows for

* Creating resources even when we are unable to access the metadata. User must provide at least a service port
* The repo/username/image will be referenced in the ImageStream

There are no guarantees you will see a pod spin up for this deployment. This will ONLY happen if the server can pull the image.  If the repo is not defined, normal docker semantics apply which is it tries dockerhub.  The only variance to this is if the server docker registry is configured to default someplace else.

> Pod is not created when docker image is deployed to OpenShift
> -------------------------------------------------------------
>
>                 Key: JBIDE-21626
>                 URL: https://issues.jboss.org/browse/JBIDE-21626
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.1.CR1
>            Reporter: Marián Labuda
>            Assignee: Jeff Cantrill
>            Priority: Critical
>              Labels: openshift_v3
>             Fix For: 4.3.1.CR1
>
>
> When deploying a docker image to OpenShift via oc binary, pod where the image is supposed to run is created, together with service and router. But when deploying a docker image to OpenShift via OpenShift tools, no pod is created, only service and router. When using cli, pod is created later (what I noticed, there is different pull policy between creating from cli with "oc new-app docker-image" and creating from IDE).



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