Removing dedicated-vm Service Instances on CF when already deleted from BOSH
search cancel

Removing dedicated-vm Service Instances on CF when already deleted from BOSH

book

Article ID: 295125

calendar_today

Updated On:

Products

Redis for VMware Tanzu

Issue/Introduction

To remove service instances from the Cloud Controller database when those deployments have already been removed from BOSH.

When an operator upgrades a Redis for PCF tile with the pre-existing dedicated-vm service instances and enables the checkbox "Delete all dedicated instances" on the "WARNING - DEDICATED INSTANCES" tab this causes a deletion of the dedicated service instances from BOSH.
The service instances will appear to still exist in CF. This is due to the fact that the CF database is not informed that they are now deleted.

Symptoms:

In the case that dedicated VMs were deleted but there are still service instance references left, you won't be able to simply delete service instances:

$ cf delete-service my-dedicated-redis
Really delete the service my-dedicated-redis?> yes
Deleting service my-dedicated-redis in org system / space pivotal-services as admin...
FAILED
Server error, status code: 504, error code: 10001, message: Service instance my-dedicated-redis: The request to the service broker timed out:...

Resolution

Checklist:

In order to reconcile the state you would need to purge the remaining service instances:

$ cf purge-service-instance my-dedicated-redis