Summary
After PR #405 landed (merge commit 6558d04, implementation feecfe7), our Concourse pipeline that runs DRATs against a Toolsmiths / cf-deployment environment fails during the CredHub scenario. Pinning DRATs to the parent of that change (c6c888c) restores a passing run.
Observed failure
Test: “backing up Cloud Foundry” / CredHub instance creds path (CfCredhubSSITestCase).
Symptom: cf push of the fixture app fails with Cloud Foundry reporting something like:
Error staging application: BuildpackCompileFailed - App staging failed in the buildpack compile phase
Stack: Failure surfaces from RunCommandSuccessfully in runner/command_line_helpers.go, called from testcases/credhub_instance_creds_testcase.go during BeforeBackup (the cf push … -b go_buildpack … step).
On our foundation, behavior before #405 (still at c6c888c) is OK; at or after #405 it is not.
Environment (ours)
Foundation: cf-deployment–style env from Toolsmiths (Shepherd lease), not a hand-built laptop bosh-lite.
CI: Concourse runs the upstream task ci/tasks/drats-with-integration-config/task.yml with a custom Docker image only for the task runner; the failure is CF staging (go_buildpack), not compilation of DRATs inside the image.
Workaround
Our CI job passes if DRATs pinned to c6c888c.
The failure message from Concourse build
Staging app and tracing logs...
Downloading go_buildpack...
Downloaded go_buildpack
Cell 3f2e1d2a-9f27-4460-b139-89f8427ee89d creating container for instance b1cda50d-05b2-4a7e-8903-f1dc1bd01a4d
Security group rules were updated
Cell 3f2e1d2a-9f27-4460-b139-89f8427ee89d successfully created container for instance b1cda50d-05b2-4a7e-8903-f1dc1bd01a4d
Downloading app package...
Downloaded app package (279.8K)
-----> Go Buildpack version 1.10.38
-----> Installing godep 80
Download [https://buildpacks.cloudfoundry.org/dependencies/godep/godep_80_linux_x64_cflinuxfs4_20fea317.tgz]
Error staging application: BuildpackCompileFailed - App staging failed in the buildpack compile phase
FAILED
[FAILED] in [It] - /tmp/build/b7784222/src/github.com/cloudfoundry/disaster-recovery-acceptance-tests/runner/command_line_helpers.go:20 @ 04/23/26 01:44:49.139
STEP: cleaning up the artifact @ 04/23/26 01:44:49.139
STEP: running the Cleanup step for cf-credhub @ 04/23/26 01:44:49.15
STEP: deleting the test secret @ 04/23/26 01:44:49.15
[FAILED] in [AfterEach] - /tmp/build/b7784222/src/github.com/cloudfoundry/disaster-recovery-acceptance-tests/runner/cf_helpers.go:67 @ 04/23/26 01:44:49.15
STEP: cleaning up the test context @ 04/23/26 01:44:49.151
STEP: remove workspace directory @ 04/23/26 01:44:49.151
• [FAILED] [18.505 seconds]
backing up Cloud Foundry [It] backs up and restores a CF
/tmp/build/b7784222/src/github.com/cloudfoundry/disaster-recovery-acceptance-tests/runner/runner.go:55
[FAILED] Expected
<int>: 1
to match exit code:
<int>: 0
In [It] at: /tmp/build/b7784222/src/github.com/cloudfoundry/disaster-recovery-acceptance-tests/runner/command_line_helpers.go:20 @ 04/23/26 01:44:49.139
Full Stack Trace
github.com/cloudfoundry/disaster-recovery-acceptance-tests/runner.RunCommandSuccessfully({0xc000156180, 0x22}, {0x0, 0x0, 0x0})
/tmp/build/b7784222/src/github.com/cloudfoundry/disaster-recovery-acceptance-tests/runner/command_line_helpers.go:20 +0x13e
github.com/cloudfoundry/disaster-recovery-acceptance-tests/testcases.(*CfCredhubSSITestCase).BeforeBackup(_, {{{0xc000246f00, 0x2}, {0xc00015d640, 0x32}, {0xc000246f02, 0x5}, {0xc000155a80, 0x1e}, {0xc000160f30, ...}, ...}, ...})
/tmp/build/b7784222/src/github.com/cloudfoundry/disaster-recovery-acceptance-tests/testcases/credhub_instance_creds_testcase.go:73 +0x3e6
github.com/cloudfoundry/disaster-recovery-acceptance-tests/runner.RunDisasterRecoveryAcceptanceTests.func2()
/tmp/build/b7784222/src/github.com/cloudfoundry/disaster-recovery-acceptance-tests/runner/runner.go:60 +0x17e
There were additional failures detected. To view them in detail run ginkgo -vv
------------------------------
Summarizing 1 Failure:
[FAIL] backing up Cloud Foundry [It] backs up and restores a CF
/tmp/build/b7784222/src/github.com/cloudfoundry/disaster-recovery-acceptance-tests/runner/command_line_helpers.go:20
Summary
After PR #405 landed (merge commit 6558d04, implementation feecfe7), our Concourse pipeline that runs DRATs against a Toolsmiths / cf-deployment environment fails during the CredHub scenario. Pinning DRATs to the parent of that change (c6c888c) restores a passing run.
Observed failure
Test: “backing up Cloud Foundry” / CredHub instance creds path (CfCredhubSSITestCase).
Symptom: cf push of the fixture app fails with Cloud Foundry reporting something like:
Error staging application: BuildpackCompileFailed - App staging failed in the buildpack compile phase
Stack: Failure surfaces from RunCommandSuccessfully in runner/command_line_helpers.go, called from testcases/credhub_instance_creds_testcase.go during BeforeBackup (the cf push … -b go_buildpack … step).
On our foundation, behavior before #405 (still at c6c888c) is OK; at or after #405 it is not.
Environment (ours)
Foundation: cf-deployment–style env from Toolsmiths (Shepherd lease), not a hand-built laptop bosh-lite.
CI: Concourse runs the upstream task ci/tasks/drats-with-integration-config/task.yml with a custom Docker image only for the task runner; the failure is CF staging (go_buildpack), not compilation of DRATs inside the image.
Workaround
Our CI job passes if DRATs pinned to c6c888c.
The failure message from Concourse build