Error while upgrading AWS Cloud Service Broker version 1.10.0 --> 1.11.0. (Status Code: 410 Gone, Body: {})

Products

• Operations Manager

Issue/Introduction

Upgrading Tanzu Cloud Service Broker version for AWS results in error below during the upgrade services errand:

2024-10-07T11:01:21Z: upgrade of instance: "S3_CSB" guid: "22b3####-55##-4###-90##-dcba########" failed after 10.127100687s: The service broker returned an invalid response. Status Code: 410 Gone, Body: {}  

 

Resolution

This is a known issue and the recommended fix is to upgrade to Tanzu CSB for AWS v1.12.2.   This action is mentioned in the "Resolved Issues" section of the product Release Note.

Before performing the upgrade to CSB app for AWS v1.12.2, the user can manually delete the service instances in CF.

1. Delete the service instances in CF. The "cf delete-service" command will likely work, but "cf purge-service-instance" should remove it if not.
2. If desired, then can delete the S3 bucket in AWS

Once the service instances are deleted in CF, the upgrade to Tanzu Cloud Service Broker for AWS v1.12.2 should work.

Additional Information

If any issues with orphaned Binding and Service Keys during this process, then can perform then below and re-run the Resolution above:

A.). Firstly identify the GUIDs of the service instance and any service bindings that it may have by running below command(s):

1. Retrieve the guid:
cf service <name> --guid

2. Check for service bindings:
cf curl /v3/service_credential_bindings?service_instance_guids=<service-instance-guid> | jq .resources.guid

# For the command above, replace "<service-instance-guid>" with the output from 1st step (Retrieve the guid:)

B.). Cleaning up from the CSB database:

• Do a cf ssh to connect to the CSB app
• To clean up a service binding, run: `cloud-service-broker purge-binding <service instance GUID> <service binding GUID>
• To clean up a service instance, run: `cloud-service-broker purge <service instance GUID>

C.). Cleaning up from the CF database:

• cf purge-service-instance should remove data about the service instance and any service bindings

*If any issues encountered after performing all the above steps, then is suggested to open a Support Ticket with VMware by Broadcom.