Config Server update command fails with "Cannot scale this process while a deployment is in flight." in Spring Cloud Services for Tanzu

Products

• Support Only for Spring

Issue/Introduction

When using Tanzu Application Service for VMs (TAS for VMs) v2.10 and v2.11 and Spring Cloud Services (SCS) for Tanzu, you may see a Config Server update operation fail with this message:

status: update failed message: CF-ScaleDisabledDuringDeployment(390016): Cannot scale this process while a deployment is in flight.

Checking the broker logs, you see a similar error:

ERROR 36 --- [ry-client-nio-2] o.s.c.a.d.c.CloudFoundryAppDeployer      : Error updating environment. applicationId=<ID>, error=CF-ScaleDisabledDuringDeployment(390016): Cannot scale this process while a deployment is in flight.

Environment

Product Version: 3.1

Resolution

This is due to a known issue with TAS for VMs v2.10 and v2.11:

Rolling app deployments do not properly timeout when the startup timeout is reached. You may experience a rolling app deployment process that hangs indefinitely.

For more information about this known issue, refer to Rolling App Deployment Does Not Timeout.

To resolve this, you will need to cancel the deployment against the backing config server application. To do this, follow these steps:

1. First check the broker logs located in /var/vcap/sys/log/scs-service-broker/scs-service-broker.stdout.log in the VM spring-cloud-services/. In the error message "Cannot scale this process while a deployment is in flight", record the value of the applicationId.

2. Next, run the cf CLI command cf curl /v2/apps/<applicationId>, using the ID collected.

3. The above output returns a space_url. Taking the value for this, run cf curl /v2/spaces/<GUID>. This gives you the name of the space where the app lives, take note of this.

4. Target the org and space using the name we collected above with cf target -o p-spring-cloud-services -s <space>.

5. Run the command cf cancel-deployment config-server.

Note: This is a cf CLI v7 command, make sure you are on cf CLI v7.