MySQL Broker is unable to access service instances because they are still associated with the old broker

Products

• VMware Tanzu SQL

Issue/Introduction

Customer's may find themselves in situations (tile rollback for example) where there is a discrepancy between the service instances deployed and the broker.

Operations Manager (Ops Manager) creates a BOSH team for the deployment when creating the broker. When uninstalling and reinstalling a service tile a new team is created. If the old service instances still exist, they are associated with the OLD broker's team, and the new broker is unable to access them.

[upgrade-all-service-instances] 2021/03/11 04:47:12.155278 failed to trigger operation for instance "c9071a86-bdfc-4c81-ae6f-cfc32131927c": unexpected response status 502 when upgrading service instance "c9071a86-bdfc-4c81-ae6f-cfc32131927c"; response body "{\n \"description\": \"Service broker error: bosh deployment 'service-instance_c9071a86-bdfc-4c81-ae6f-cfc32131927c' not found\",\n \"error_code\": \"CF-ServiceBrokerBadResponse\",\n \"code\": 10001,\n \"http\": {\n \"uri\": \"http://10.0.4.12:8080/v2/service_instances/c9071a86-bdfc-4c81-ae6f-cfc32131927c?accepts_incomplete=true\",\n \"method\": \"PATCH\",\n \"status\": 500\n }\n}\n"

Resolution

Please contact Tanzu Support and provide this KB Article ID to assist with the resolution.