Bug 2083087

Summary:	"Delete dependent objects of this resource" might cause confusions
Product:	OpenShift Container Platform	Reporter:	Chen <cchen>
Component:	Dev Console	Assignee:	divgupta
Status:	CLOSED ERRATA	QA Contact:	spathak <spathak>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.8	CC:	cjerolim, divgupta, jakumar, nmukherj, sdoyle, viraj
Target Milestone:	---
Target Release:	4.13.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The web console shows a pre-selected "Delete dependent objects of this resource" checkbox when deleting a Deployment, or many other resources. Users expected that deleting a Deployment removes all resources that the web console created when using the "Import from Git" or "Import image container" flow. But other resources like the created ImageStream, Route, Service and Secrets wasn't deleted. The checkbox only deletes resources that are linked with metadata.ownerReferences field. See https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/ Consequence: Users are confused that the web console doesn't delete everything. And a new import via "Import from Git" or "Import image container" (with the same name) fails because of these leftover resources with an error "ImageStream with that name already exists". Fix: When deleting a Deployment the web console now shows a second pre-selected option "Delete other resources created by console". If the user kept this checkbox enabled all mentioned resources above are automatically deleted. Result: The web console now cleanup resources it creates and allows the user to reimport the same application with the same name again.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-17 22:46:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chen 2022-05-09 09:27:48 UTC

Description of problem:

"Delete dependent objects of this resource" is a bit of confusing for some users because when creating the Application in Dev console not only the deployment but also IS, route, svc, secret objects will be created as well. When deleting the Application (in fact it is deployment), there is an option called "Delete dependent objects of this resource" and some users might think this means the IS, route, svc and any other objects which are created alongside with the deployment will be deleted as well

Version-Release number of selected component (if applicable):

4.8

How reproducible:

100%

Steps to Reproduce:
1. Create Application in Dev console
2. Delete the deployment
3. Check "Delete dependent objects of this resource"

Actual results:

Only deployment will be deleted and IS, svc, route will not be deleted

Expected results:

We either change the description of this option, or we really delete IS, svc, route and any other objects created under this Application.

Additional info:

Comment 3 divgupta 2022-12-13 14:42:02 UTC

The checkbox is used to start the garbage collection which means any resources linked with deployment pods via owner references will be deleted. It does not delete all the resources created via ODC app creation forms.

@cjerolim @jakumar @sdoyle IMO since here we are just deleting a deployment it makes sense to update the text to prevent confusion instead of deleting all created resources in the background as this already happens once the user deletes the application group.

Comment 9 errata-xmlrpc 2023-05-17 22:46:32 UTC

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 (Important: OpenShift Container Platform 4.13.0 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:1326