search

Azure / open-service-broker-azure

The Open Service Broker API Server for Azure Services
https://osba.sh
MIT License
248 stars 100 forks source link

purge DeprovisionCallFailed entries from database #682

Closed cforce closed 5 years ago

cforce commented 5 years ago

I have the issue that i have left overs from DeprovisionCallFailed or Failed. How can i force to remove such entries (and accept i might handle the deprovisioning manually) Can't find an svcat cmd/param (line in "cf purge-service-instance mysql-dev") that allows to force delete the entries .

zhongyi-zhang commented 5 years ago

Yeah, svcat has not force delete so far: https://github.com/kubernetes-incubator/service-catalog/issues/2268. You can manually delete the stuck instance record from OSBA store (the redis cache). Then, use svcat to deprovision again. OSBA returns 410 in this case and svcat considers it as a success. And then don't forget to delete the ARM resource from Portal.

cforce commented 5 years ago

Looks like merg for solution has been done on incubator https://github.com/kubernetes-incubator/service-catalog/pull/2579

zhongyi-zhang commented 5 years ago

Solved by service-catalog as @cforce mentioned.