After upgrading TAS push-apps-manager errand fails due to nodejs offline buildpack not updated

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

After upgrading TAS push-apps-manager errand fails with following error,
 

.
.
.
2022-12-28T22:48:52.89+0000 [STG/0] OUT        yarn.lock and package.json match
       2022-12-28T22:48:53.77+0000 [STG/0] ERR Failed to compile droplet: Failed to run finalize script: signal: killed
       2022-12-28T22:48:53.78+0000 [STG/0] OUT Exit status 223
       2022-12-28T22:48:54.38+0000 [STG/0] OUT Cell ad889f87-4436-4a85-ac4c-9586681208a7 stopping instance 38716434-99ca-42aa-829a-e90d058a2cf8
       2022-12-28T22:48:54.38+0000 [STG/0] OUT Cell ad889f87-4436-4a85-ac4c-9586681208a7 destroying container for instance 38716434-99ca-42aa-829a-e90d058a2cf8
       2022-12-28T22:48:54.52+0000 [API/1] ERR Failed to stage build: staging failed
[1m[31mInvitations deployment FAILED!

This can happen if nodejs offline buildpack is locked, therefore, not updated with TAS and a newer version of the buildpack needs to run with the upgraded TAS version.

Environment

Product Version: 2.11

Resolution

Check the nodejs-offline-buildpack version that is shipped with your new TAS version in the release notes, E.g.  https://docs.vmware.com/en/VMware-Tanzu-Application-Service/2.11/tas-for-vms/runtime-rn.html, go to https://network.tanzu.vmware.com/products/nodejs-buildpack/ and download the needed version.

Then use the cf create-buildpack command to upload the buildpack into your deployment
 

cf create-buildpack BUILDPACK PATH POSITION

Make sure that the position is lower than the older, locked buildpack so the newer one is picked up when the errand is running. You can also just delete the old one, to avoid conflict with newer.