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

[Dmitrii Bocharov (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitrii Bocharov updated JBIDE-22626:
-------------------------------------
    Attachment: ImageStreamTags.jpg


[~jeffmaury][~jcantrill] i've started to investigate this problem from scratch after reading OS documentation about working with Dokcer images in OS. I've reset all my changes and tested master.
1) I 'mvn clean install' aloha project
2) Built a docker image for cdk docker connection
3) add a 0.1 tag to the image
4) Deployed image to OS with pushing to registry
DC and Image stream were created. Image stream has 0.1 tag. DC has:
{code:json}
triggers:
    - 
      type: "ConfigChange"
    -
      type: ImageChange
      imageChangeParams:
        automatic: true
        containerNames:
          - aloha
        from:
          kind: ImageStreamTag
          namespace: sample-project
          name: 'aloha:0.1'
        lastTriggeredImage: '172.30.74.175:5000/sample-project/aloha at sha256:964d13ef4d3cd1ccc548f48a1e60a388a0fa99cba54c735c95cd5b79d08fbc31'
{code}

5) i changed a bit the sources of aloha and repeated all previous steps but not added tag 0.2, which is now the :latest
Image stream has now 2 tags and that's right. However DC didn't change, as it is stated in this JIRA description.
However, [here it is said|https://docs.openshift.com/enterprise/latest/dev_guide/deployments.html#image-change-trigger], that
{panel:title=Image Change Trigger}
With the above example, when the latest tag value of the origin-ruby-sample image stream changes and the new image value differs from the current image specified in the deployment configuration’s helloworld container, a new deployment is created using the new image for the helloworld container.
{panel}
The tag in the Image Stream changed, image value is different (it can be see from web console, when viewing image stream tags [^ImageStreamTags.jpg]). [~jcantrill] do you have any guesses why wasn't it trigerred?


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