+++ This bug was initially created as a clone of Bug #1509029 +++ It covers reproduction case #1 as detailed in https://github.com/kubernetes-incubator/service-catalog/issues/1423 If the ServiceBinding is in an error state, it can block deletion of the binding. Version-Release number of selected component (if applicable): 3.7 How reproducible: Always Steps to Reproduce: Reproduction #1. Go through the walkthrough without starting the service broker. A. kubectl create -f contrib/examples/walkthrough/ups-broker.yaml B. kubectl create namespace test-ns C. kubectl create -f contrib/examples/walkthrough/ups-instance.yaml D. kubectl create -f contrib/examples/walkthrough/ups-binding.yaml E. At this point you can't get rid of the binding. Try kubectl delete -n test-ns servicebindings ups-binding F. The instance can't be deleted either because of the associated binding.
This is fixed and working properly in 3.9 MASTER. steps to verify: kubectl create -f ../../kubernetes-incubator/service-catalog/contrib/examples/walkthrough/ups-broker.yaml kubectl create namespace test-ns kubectl create -f ../../kubernetes-incubator/service-catalog/contrib/examples/walkthrough/ups-instance.yaml kubectl create -f ../../kubernetes-incubator/service-catalog/contrib/examples/walkthrough/ups-binding.yaml kubectl delete servicebindings -n test-ns ups-binding kubectl delete serviceinstance -n test-ns ups-instance
I'm changing status to ON_QA since downstream image ready for test.