[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=13290838#comment-13290838 ] 

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

First comment is that you can not change from 'refresh' to 'updateResource' unless you are in fact 'updating'.  Without looking at the code more in depth, I presume the path that is 'refresh'ing would return the latest version of the resource to later be updated.

DC's with configchange triggers will basically over-write the value in the container block based on what the trigger says; the container.image field is essentially ignored.  I think you should be updating this: https://gist.github.com/bdshadow/49acf54196091bb772f2a368fd57348b#file-request-to-update-L44

I'm curious how you got a second container in the spec which essentially is a duplicate.  This could be an issue in the rest-client we need to address.

If any of these changes are difficult because of the restclient, that means we need to update the restclient. 

> 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.1.Final
>
>
> 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.



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