search

Azure / meta-azure-service-broker

A service broker to manage multiple Azure services in Cloud Foundry
Apache License 2.0
39 stars 44 forks source link

azure-sqldb-failover-group module: unbinding issue in ExistingDatabaseInFailoverGroup plan #189

Closed zhongyi-zhang closed 5 years ago

zhongyi-zhang commented 5 years ago

Unbinding in ExistingDatabaseInFailoverGroup plan fails for an earlier deletion of the corresponding SecondaryDatabaseWithFailoverGroup plan instance. Because it fails to delete the user created in binding as the database is no longer existed on Azure. Normally, an ExistingDatabaseInFailoverGroup instance should be deleted before the SecondaryDatabaseWithFailoverGroup instance. But the mechanism is design for multiple CF clusters scenario. We can't ensure that order inside a broker. Possible solution: with ExistingDatabaseInFailoverGroup plan, unbinding can give up deleting the user if the database on Azure is no longer existed and return success.

NingKuang commented 5 years ago

The workaround is to just ignore the unbind error, as it actually succeed. it is just did not remove the user successfully.