Why do you receive a deployment rollback error when you run the PCF operation update command with a buildpack update and service binding?

Products

• DX SaaS

Issue/Introduction

You encounter a deployment failure when you attempt to update a Pivotal Cloud Foundry (PCF) application using a specific buildpack while simultaneously binding services like Introscope. This issue typically manifests as a rollback operation after the deployment fails to start containers on the foundation. This article provides guidance on resolving the conflict by separating the service binding and buildpack update tasks.

Environment

• DX APM SaaS
• PCF (Pivotal Cloud Foundry)
• Java Buildpack (e.g., version 4.86 or 4.89)

Cause

The error occurs when you attempt to bind the Introscope service and upgrade the buildpack version within the same update operation. Running these actions simultaneously can cause the deployment to fail during the container initialization phase, leading to an automatic rollback on foundations

Resolution

To resolve this issue, you must perform the service binding and the buildpack update as separate operations.

1. Update the application buildpack first without binding new services.
2. Verify that the deployment completes successfully across all foundations.
3. Bind the Introscope service to the application once the buildpack update is stable.
4. If services do not appear in the APM console immediately, allow up to 30 minutes for the metrics to reflect automatically.

Note on Fixes: This issue is related to deployment sequencing rather than a specific software defect. However, if you are using older buildpacks, it is recommended to upgrade to ensure compatibility.

• Non-VCF Divisions: Targeted to be fixed in a future release if a defect is identified.
• All Divisions (Post-GA): Fixed in release 4.89 and higher. See Download Broadcom products and software for steps to download this release.

Additional Information

• Deploy and Monitor a Java Application on Cloud Foundry