cf create-service, update-service or bind-service fail on TAS 2.11.x

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

https://docs.vmware.com/en/Spring-Cloud-Services-for-VMware-Tanzu/3.1/spring-cloud-services/GUID-release-notes.html

Spring Cloud Services v3.1.0-v3.1.19 fails on service broker commands with Tanzu Application Service v2.11.x Tanzu Application Service deprecated the state field for service broker endpoints. This causes Spring Cloud Services v3.1.0 to v3.1.19 versions to fail on service broker commands for service instances including create-service, update-service and bind-service.

Environment

Product Version: 2.11

Resolution

Examine the diagnostic_report.json file

• Download the Support Bundle from Ops Manager
• Find it in the Ops Manager GUI (click login ID drop-down menu in upper right corner, choose Settings, Advanced Options in the left column, then the View Diagnostic Report button)

Check the versions of installed Tanzu Application Service (cf):

      {
        "name": "cf",
        "version": "2.11.10",
        "stemcells": [
          {
            "filename": "bosh-stemcell-621.183-azure-hyperv-ubuntu-xenial-go_agent.tgz",
            "os": "ubuntu-xenial",
            "version": "621.183"
          }
        ]
      },

and Spring Cloud Services (p_spring-cloud-services):

     {
        "name": "p_spring-cloud-services",
        "version": "3.1.19",
        "stemcells": [
          {
            "filename": "bosh-stemcell-621.183-azure-hyperv-ubuntu-xenial-go_agent.tgz",
            "os": "ubuntu-xenial",
            "version": "621.183"
          }
        ]
      },

If TAS is 2.11.x, then check whether SCS is between 3.1.0 and 3.1.19. If so, then they will need to upgrade to Spring Cloud Services version 3.1.20, which now has Tanzu Application Service v2.11.x support.