Description of problem:
Created a jboss EAP deployment using template in web console. Subsequently attempted to destroy all resources associated with that deployment by deleting the deployment config.
Deletion of the DC did not cascade -- leaving behind a Deployment, RC, pods, etc. There appeared to be no way to clean up these artifacts through the GUI since the deployment had "Delete" grayed out. It was not intuitive that the GUI needed me to scale the pods to 0 before deletion would be allowed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add to project: jboss-eap64-openshift 1.2
2. Used "Try it" quickstart
3. Allow deploy to complete
4. Delete DC or Service without scaling down pods
Deployment/RC/Pods remain and (seemingly) cannot be deleted. The GUI warns you that the DC associated with the Deployment is gone, but "Delete" is grayed out for the deployment #.
The layout of the GUI overview page communicates two things visually.
(1) The Deployment is the primary artifact of the action I took when I created the application (based on visual size / detail / ability to delve into pod info/etc).
(2) The Service groups everything together (based on its box visually encompassing the deployment).
As a new user to the system, I would anticipate that deleting either DC or Service would delete all application resources (deployment/rc/pods/routes/service). At a minimum, I would expect the GUI to inform me why Delete was being grayed out in my deployment# so that I would know to scale down my pods.
As far as good cascading deletion we are already tracking that https://trello.com/c/mZuAqafi
The console requiring someone to scale down before they can delete is temporary until we can actually do cascading deletion properly on the backend. Agreed its not clear that is why Delete is grayed out.
This has been merged into ose and is in OSE v184.108.40.206 or newer.
Now when deleting DC/BC, you will get a warning dialog saying when we can't cascade delete on web console, you could run CLI command to delete deployment config/build config and all of its deployments/builds
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.