Red Hat Bugzilla – Bug 1507448
[tsb]Can't delete templateinstance and other resoureces when deprovision a failed serviceinstance
Last modified: 2017-11-28 17:20:01 EST
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:
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.
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?
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.
Verified this is working https://github.com/openshift/origin/pull/17075
Paul I cancel jenkins deployment just to make serviceinstance provision failed. Serviceinstance provision failed is a necessary conditions for this bug.
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
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