Integration issue between Zero Downtime App Deployment and Spring Boot Actuators

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

Symptoms:

The user evaluates Zero Downtime App Deployment when using the cf v3-zdt-push command. The target application is based on Spring Boot with the Spring Boot Actuator feature (Spring Boot 2.0.8).

After executing  the cf v3-zdt-push command, the target application seems to be replaced by a newer version and it works. However, you will not be able to access stats through the Spring Boot Actuator feature on Apps Manager, PCF Metrics, etc. after executing Zero Downtime App Deployment.

Environment

Cause

cf v3-zdt-push temporarily assigns a new 'application_id' to the newer version of the application while executing Zero Downtime App Deployment.

It should be replaced by the original 'application_id' but is not. This can be observed by looking at the cloud.application.application_id at the /env endpoint of Spring Boot Actuator.

The 'application_id' value changes in two locations after executing Zero Downtime App Deployment. However, these values should be identical.

• 'application_id' changes at the Environment Variables section on Apps Manager.
• 'cloud.application.application_id' changes at the /env endpoint of Sprint Boot Actuator.

Resolution

This is a known issue between Zero Downtime App Deployment and Spring Boot Actuators. We expect this fix to be in a future patch version of PCF 2.4 and 2.5.