[jbosstools-issues] [JBoss JIRA] (JBIDE-22515) Deploying/Pushing an updated docker image causes an error because of conflicting resources

[Fred Bricon (JIRA)]

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

Fred Bricon updated JBIDE-22515:
--------------------------------
    Steps to Reproduce: 
0a - clone and import https://github.com/redhat-helloworld-msa/aloha
0b- once built, go in openshift explorer, create a new  redhat-helloworld-msa project


1- perform a maven CLI build
2- right click on the DockerFile, Run As Docker Image Build, select CDK docker connection, repo name as foo/aloha
3- right click on redhat-helloworld-msa, Deploy Docker Image... 
4- select push image to registry, go next and finish
5- image is pushed, 3 resources are created eventually.
6- app is deployed and accessible online

Docker update:
7- change some response in AlohaVerticle
8- repeat all steps from #1
=> image is pushed but there's an error message popping up about resource conflicts
=> app is still updated properly on openshift

  was:
0 - clone and import https://github.com/redhat-helloworld-msa/aloha


1- perform a maven CLI build
2- right click on the DockerFile, Run As Docker Image Build, select CDK docker connection, repo name as foo/aloha
3- once built, go in openshift explorer, create a new  redhat-helloworld-msa project
4- right click on redhat-helloworld-msa, Deploy Docker Image... 
5- select push image to registry, go next and finish
6- image is pushed, 3 resources are created eventually.
7- app is deployed and accessible online

Docker update:
8- change some response in AlohaVerticle
9- repeat all steps from #1
=> image is pushed but there's an error message popping up about resource conflicts
=> app is still updated properly on openshift



> Deploying/Pushing an updated docker image causes an error because of conflicting resources
> ------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-22515
>                 URL: https://issues.jboss.org/browse/JBIDE-22515
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>            Reporter: Fred Bricon
>            Assignee: Jeff Cantrill
>              Labels: respin-a
>             Fix For: 4.4.0.Final
>
>
> After a docker image has been successfully deployed to OpenShift, if the image has been updated to a new version in the daemon, performing a second Deploy to OpenShift command will effectively update the image but an error will popup about resources already existing.
> I believe that, when we're about to create the openshift resources, we should
> - detect if there's already a matching deployment config for the same project/resource name)
> - if the deployment config links to an imagestream matching the docker image being deployed, then it's an update, then bail without creating any resources, else resource conflict checks should happen.
> Ideally, this should probably happen at the wizard level, so we don't need to show the resource pages and go straight to finish, but that can be implemented later



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