[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21895 at 2/2/17 3:39 PM: ------------------------------------------------------------------ [~psrna] In the above steps, when you say "Delete the application", you're deleting the 1st child of the project in OpenShift explorer (the item in the tree, that has a circle with 2 arrows as icon)? !1st-child-of-project.png! If this is then case, then you're actually deleting the service. You're leaving behind all the other resources that are used to build, deploy and oversee the lifecycle of your application (image stream, deployment config, build config, replication controller, route etc.). All these resources are still in place. The OpenShift explorer just only shows you the service and wont the other resources. The properties view though shows you that there are plenty more resources for the selected project. When the template wants to create new ones with identical names, you get name clashes. See your screenshot which explicitly omits the service resource but lists all the other resources: !Screen%20Shot%202016-03-17%20at%2016.19.05.png! That's very much expected and there isnt much that we can do about it beside better informing and guiding users. Maybe the application wizard should inform of possible name clashes once you selected the template? The only way to prevent name clashes is to delete the *project* (not just the *service*). And that's very much also the expected workflow, since a project is expected to hold all the resources that are related to an application. was (Author: adietish): [~psrna] In the above steps, when you say "Delete the application", you're deleting the 1st child of the project in OpenShift explorer (the item in the tree, that has a circle with 2 arrows as icon)? !1st-child-of-project.png! If this is then case, then you're actually deleting the service. You're leaving behind all the other resources that are used to build, deploy and oversee the lifecycle of your application (deployment config, build config, recplication controller, etc.). All these resources are still in place and when the template wants to create new ones with identical names, you get name clashes. That's very much expected and there isnt much that we can do about it beside better informing and guiding users. Maybe the application wizard should inform of possible name clashes once you selected the template? -- This message was sent by Atlassian JIRA (v7.2.3#72005)