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