Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1507448

Summary:	[tsb]Can't delete templateinstance and other resoureces when deprovision a failed serviceinstance
Product:	OpenShift Container Platform	Reporter:	XiuJuan Wang <xiuwang>
Component:	Service Broker	Assignee:	Jeff Peeler <jpeeler>
Status:	CLOSED ERRATA	QA Contact:	XiuJuan Wang <xiuwang>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.7.0	CC:	aos-bugs, bparees, pmorie, spadgett
Target Milestone:	---
Target Release:	3.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Deleting a failed ServiceInstance was not deleting other dependent resources, now all resources are deleted as expected.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-28 22:20:01 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 XiuJuan Wang 2017-10-30 09:53:03 UTC

Description of problem:
Deprovision serviceinstance which status is failed, will not delete other resources include templateinstance.

Version-Release number of selected component (if applicable):
brew-*/ose-service-catalog   v3.7.0-0.185.0.0    ef0dd815574a        2 days ago          266 MB

How reproducible:
always

Steps to Reproduce:
1.Provision jenkins-ephemral clusterserviceclass via browse catalog
2.Cancel jenkins deployment so no jenkins pod is running
3.jenkins serviceinstance will failed due to 'Provision call failed: Readiness failed on DeploymentConfig wang1/jenkins'
4.Deprovision the failed serviceinstance

Actual results:
Only serviceinstance be deleted,templateinstance and other resources(like dc,rc,pod,bc,builds,service) don't be deleted.

Expected results:
Should delete all resources

Additional info:

Comment 1 Paul Morie 2017-10-30 14:51:34 UTC

This should be fixed by https://github.com/openshift/origin/pull/17075.

Jeff, will you test this and verify that it is fixed with the version in your PR?  If so, please move this bug to POST.

Comment 2 Paul Morie 2017-10-30 19:56:26 UTC

It's not clear to me what the point of the cancel button is, if it doesn't delete the ServiceInstance.  It was definitely confusing to users in this case.  Is this a bug related to the button, or is the button itself a bug until we have a way to actually cancel the operation?

Comment 3 Samuel Padgett 2017-10-30 20:29:10 UTC

There is no cancel for provision in the console. I think the description is referring to cancelling the running deployment for the deployment config created by the template.

Comment 4 Samuel Padgett 2017-10-30 20:44:32 UTC

Verified this is working

https://github.com/openshift/origin/pull/17075

Comment 5 XiuJuan Wang 2017-10-31 02:03:42 UTC

Paul
I cancel jenkins deployment just to make serviceinstance provision failed.
Serviceinstance provision failed is a necessary conditions for this bug.

Comment 7 XiuJuan Wang 2017-11-02 02:41:41 UTC

Can't reproduce this bug with [1]

[1]
openshift v3.7.0-0.189.0
kubernetes v1.7.6+a08f5eeb62

ose-service-catalog:v3.7.0-0.189.0

Comment 10 errata-xmlrpc 2017-11-28 22:20:01 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, 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-2017:3188