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

[Marián Labuda (JIRA)]

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

Marián Labuda commented on JBIDE-22626:
---------------------------------------

I think it would be nice to have supported following use case:
1. There is a docker image aloha:1.0
2. Deploy image to OpenShift and push it to registry (check the checkbox in Deploy Image to OpenShift wizard)
3. Resource are created (DC, RC, IS, pods, service, route)
4. I perform change changes to docker file of aloha image, tag it as version 2.0
5. Deploy image aloha:2.0 via the Deploy image.
to this point everything is ok. Now I would just modify DC to replace old tag with the new one. Entries in IS are correct (there is a new tag for 2.0 image). 


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