Fails to delete Spring Cloud Services tile due to error "Unable to remove service binding from mirror-svc"

Products

• Support Only for Spring
• VMware Tanzu Platform Spring
• VMware Tanzu Platform - Cloud Foundry

Issue/Introduction

When deleting the Spring Cloud Service tile, the errand destroy-broker fails and reports the following error:

An unbind operation for the service binding between app config-server and service instance mirror-svc failed: 
Service broker error: Service instance does not exist: id=f2922f37-c1ca-45d1-96a3-a770d2319321 

Or you might see a similar error instead:

An unbind operation for the service binding between app config-server and service instance mirror-svc failed: Service broker error: appId must not be null  

Resolution

The config-server service instance has another backend service instance, mirror-srv. The problem is caused by the orphaned mirror-srv instance which blocks the config-server deletion, then blocks the tile deletion. 
 

We can manually delete the mirror-srv and config-server instance: 
 

1. Set target:

cf target -o p-spring-cloud-services -s f2922f37-c1ca-45d1-96a3-a770d2319321 

2. Purge this service instance mirror-svc:

cf purge-service-instance mirror-svc

3. Delete the config-server app:

cf delete config-server

 
After the procedures above are done, please run the errand destroy-broker to delete the SCS tile again.

Additional Information

If you see the below error then it might not be obvious what space to target in step 1:

An unbind operation for the service binding between app config-server and service instance mirror-svc failed: Service broker error: appId must not be null  

 

If that is the case, look for a line similar to the following in the errand logs with the 502 response code:

2025-10-08T14:03:44.004Z  WARN 7 --- [ry-client-nio-3] cloudfoundry-client.response             : 502    /v2/apps/6bdfc5f3-EXAMPLE-afde3d4a4cd4/service_bindings/4bf2d4e7-EXAMPLE-6c9724074b64 (970 ms) [Endpoint+deprecated]

Copy the app GUID (6bdfc5f3-EXAMPLE-afde3d4a4cd4 in the above example) and run the following command to get the space name to use for step 1:

cf curl /v3/spaces/$(cf curl /v3/apps/<APP_GUID> | jq -r '.relationships.space.data.guid') | jq -r .name

 

Example:

~ % cf curl /v3/spaces/$(cf curl /v3/apps/6bdfc5f3-EXAMPLE-afde3d4a4cd4 | jq -r '.relationships.space.data.guid') | jq -r .name
8c85b513-EXAMPLE-973d29e17bd6

8c85b513-EXAMPLE-973d29e17bd6 is the space name