Rolling strategy deployment causes broken/unavailable app even though deployment was previously healthy

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

You followed the following steps
 

1. . cf push healthy app to Tanzu application Service (TAS)
2. modify the source code to simulate a unhealthy app
3. push the modified source code. cf push <unhealthy-app> --strategy rolling
4. notice how the app with try to start but fails to start. The app falls back to the version in step 2 where you have an unhealthy version instead of the last healthy version

Environment

Product Version: 2.10

Resolution

This issue is caused by a bug in CAPI and is fixed in CAPI version 144.0

As of writing there is no Tanzu Application Service (TAS) containing CAPI version 1.144.0+
This fix will be included in future release of TAS.