The autoscaler smoke-test errand fails with staging the test app
search cancel

The autoscaler smoke-test errand fails with staging the test app

book

Article ID: 417459

calendar_today

Updated On:

Products

VMware Tanzu Application Service

Issue/Introduction

The autoscaler smoke-test errand failed with error like "malformed buildpack does not contain ..." when pushing the test app. For example,


===== 2025-11-04 06:06:11 UTC Running "/usr/local/bin/bosh --no-color --non-interactive --tty --environment=#.#.#.#--deployment=cf-#### run-errand test-autoscaling --instance clock_global/first"
......
           + cf push app-17168 --no-route --stack cflinuxfs4
           Pushing app app-17168 to org system / space space-22704 as admin...
           Applying manifest file /var/vcap/data/packages/autoscaling_smoke_test/cf5ee57a631####9a834b129e5101f5b3594/app/manifest.yml...

           Updating with these attributes...
             ---
             applications:
           + - name: app-17168
               disk-quota: 16M
               memory: 64M
           +   no-route: true
           +   stack: cflinuxfs4
           +   buildpack: go_buildpack
           +   env:
           +     GOPACKAGENAME: smoke_test/app
           Manifest applied
           Packaging files to upload...
           Uploading files...
            0 B / 881 B    0.00% 881 B / 881 B  100.00% 881 B / 881 B  100.00% 881 B / 881 B  100.00% 881 B / 881 B  100.00% 881 B / 881 B  100.00% 881 B / 881 B  100.00% 1s

           Waiting for API to complete processing files...

           Staging app and tracing logs...
              Downloading go_buildpack...
              Downloaded go_buildpack (49.3K)
              Cell d0ea118b-####-c772942112dc creating container for instance d5cd4eab-####-f22120125c0a
              Security group rules were updated
              Cell d0ea118b-####-c772942112dc successfully created container for instance d5cd4eab-####-f22120125c0a
              Downloading app package...
              Downloaded app package (881B)
              Failed to run all supply scripts: malformed buildpack does not contain a /bin dir: 9fdee01a-####-####8524654_c3ca5e3b5ed7afa6ba9f36####1994673c3e62737dcaecdc0c8d2f94893
              Exit status 225
           StagingError - Staging error: staging failed
           FAILED

 

Attempt to push another simple test app using same go_buildpack would also fail with the same error "Failed to run all supply scripts: malformed buildpack does not contain a /bin dir ...".

 

Cause

There is issue with go_buildpack currently installed on the platform (e.g. corrupted package in blobstore).

Resolution

Follow the steps below to recreate the go_buildpack.

1. Download go_buildpack package for expected version from Broadcom Support Portal

2. Run cf buildpacks to list out all installed buildpacks and note down the position number of go_buildpack

3. Delete the currently installed go_buildpack

cf delete-buildpack go_buildpack -s cflinuxfs4

4. Create go_buildpack again with package downloaded at step 1

cf create-buildpack go_buildpack <go_buildpack package path> <position number noted down at step 2>

5. Run cf buildpacks again to verify go_buildpack is recreated

6. Try to push a simple test app using go_buildpack. If the app is successfully deployed then the newly recreated go_buildpack is working

7. Try to run autoscaler smoke-test errand again

 

Additional Information

Buildpack related CF CLI commands