Bug 1548618

Summary:	Need to clarify the notice for service catalog resources serviceinstance/servicebinding/project clean up
Product:	OpenShift Container Platform	Reporter:	Zhang Cheng <chezhang>
Component:	Documentation	Assignee:	Vikram Goyal <vigoyal>
Status:	CLOSED DUPLICATE	QA Contact:	Zhang Cheng <chezhang>
Severity:	medium	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	medium
Version:	3.9.0	CC:	aos-bugs, chezhang, erich, jiazha, jokerman, kalexand, mmccomas, pmorie
Target Milestone:	---
Target Release:	3.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-07 15:46:49 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 Zhang Cheng 2018-02-24 01:46:22 UTC

Description of problem: 
Need to clarify the notice for service catalog resources serviceinstance/servicebinding/project clean up.

Please refer to: 
https://bugzilla.redhat.com/show_bug.cgi?id=1541350#c5
https://bugzilla.redhat.com/show_bug.cgi?id=1540543#c5

Comment 1 Paul Morie 2018-02-26 15:14:31 UTC

We have already made a PR for this: https://github.com/openshift/openshift-docs/pull/7752

Does that improve things sufficiently, or is more clarification needed?

Comment 2 Zhang Cheng 2018-02-27 07:18:18 UTC

@Paul,
The clarification is OKay for me. Furthermore, I suggest to add more description about how to workaround and notice for '--force' while user try to removing service catalog resources.

As you said in another bug: https://bugzilla.redhat.com/show_bug.cgi?id=1540543#c5

You can remove the finalizer to unblock full deletion of the service instance, but you run the risk that there may be resources associated with the instance that aren't fully deleted.

For the record, '--force' doesn't have any effect on service catalog resources. My comment that it should work was a statement that ideally it should work, not that we expect it to work now. Since I wrote that comment, I've discovered the --force is basically a client-side notion only, and we won't be able to have custom behavior to make --force work for service catalog resources.

Comment 3 Kathryn Alexander 2021-04-07 15:46:49 UTC


*** This bug has been marked as a duplicate of bug 1544554 ***