Deleting Spring Cloud Services (SCS) 2.0.x tile can cause SCS 3.x outage

Products

• Support Only for Spring

Issue/Introduction

Symptoms:

When both

Spring Cloud Services for VMware Tanzu 2.0.x and 3.x are deployed, they share same backend apps space at `p-spring-cloud-services` org / `instances` space. When deleting the Spring Cloud Services for VMware Tanzu 2.0.x tile with "Pre-Delete Errands" enabled, those service instances (config-server) created by the Spring Cloud Services for VMware Tanzu 3.x broker will also be deleted because the entire org is deleted.

Environment

Cause

Due to Spring Cloud Services for VMware Tanzu 2.0.x tile errand approach to cleaning up the `p-spring-cloud-services` org, this could delete all backing applications and spaces for Spring Cloud Services for VMware Tanzu 3.x service instances. This would mean that existing Spring Cloud Services for VMware Tanzu 3.x p.config-server service instances will no longer work properly with their bound applications.

Resolution

Please do not uninstall the

Spring Cloud Services for VMware Tanzu 2.0.x tile until a patch release to resolve the delete tile errand cleanup approach. Pivotal R&D is actively working on a patch release. 

If this already occurred and all Spring Cloud Services for VMware Tanzu 3.x instances have been deleted due to deletion of the org, please rerun Spring Cloud Services for VMware Tanzu 3.x tile deployment errand to recreate `p-spring-cloud-services` org, then `cf purge-service-instance` all existing Spring Cloud Services for VMware Tanzu 3.x instances so CAPI knows that they are gone. Finally, recreate every instance and rebind to apps.