[jbosstools-issues] [JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work

[Jeff Cantrill (JIRA)]

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

Jeff Cantrill commented on JBIDE-22626:
---------------------------------------

I'm not certain the expectation here is properly framed.  I believe you are asking why the image does not get redeployed when a new image is available.  Based upon the sample provided:

{code}
from:
  kind: ImageStreamTag
  namespace: sample-project
  name: 'aloha:0.1'
{code}

A new deployment will only occur if you push a new image that has the tag 'aloha:0.1'.  It looks as though you are expecting that pushing a new tag (e.g. 0.2) will produce a new deployment.  This is not the case.  You will need to either update the name to be 'aloha:latest' and push a new image or edit the name to the desired tag


> Updating deployed docker image on OpenShift does not work
> ---------------------------------------------------------
>
>                 Key: JBIDE-22626
>                 URL: https://issues.jboss.org/browse/JBIDE-22626
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.0.Final
>            Reporter: Marián Labuda
>            Assignee: Dmitrii Bocharov
>            Priority: Critical
>              Labels: docker, openshift_v3
>             Fix For: 4.4.2.AM1
>
>         Attachments: ImageStreamTags.jpg
>
>
> In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok.
> But if user deploys image with tag e.g. :0.8 to OpenShift, resources are created for this specific tag. When I am trying to Deploy to OS image with tag :0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag :0.8 and thus new deployment is not done.
> Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it.
> In order to add this version tag after semicolon, right-click on the image -> Add tag -> Re-type namespace/imagename + add ":0.8" e.g.
> Tagging Images: https://docs.openshift.com/enterprise/latest/dev_guide/managing_images.html#tagging-images
> Image Change Trigger: https://docs.openshift.com/enterprise/latest/dev_guide/deployments.html#image-change-trigger



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