Tanzu workload creation jobs may fail in CI/CD builds due to the error below. The impact of this is that all the builds are halted until the user accepts the EULA.
simple 13-Jan-2026 10:03:50 Starting task 'Tanzu create workload' of type 'com.######.######.plugins.scripttask:task.builder.script'
command 13-Jan-2026 10:03:50 Beginning to execute external process for build
---
build 13-Jan-2026 10:03:50 version: v1.4.1
build 13-Jan-2026 10:03:50 buildDate: 2024-08-14
build 13-Jan-2026 10:03:50 sha: bbde4b21
build 13-Jan-2026 10:03:50 arch: amd64
build 13-Jan-2026 10:03:50 7[?25l8[0G[2K[1;36m? [0m[1;99mYou must agree to the Broadcom Foundation Agreement in order to download,
build 13-Jan-2026 10:03:50 install, or use software from this registry via Tanzu CLI. Acceptance of the
build 13-Jan-2026 10:03:50 Broadcom Foundation Agreement covers all software installed via the Tanzu CLI
build 13-Jan-2026 10:03:50 during any Session. "Session" means the period from acceptance until any of the
build 13-Jan-2026 10:03:50 following occurs: (1) a change to Broadcom Foundation Agreement, (2) a new
build 13-Jan-2026 10:03:50 major release of the Tanzu CLI is installed, (3) software is accessed in a
build 13-Jan-2026 10:03:50 separate software distribution registry, or (4) re-acceptance of the Foundation
build 13-Jan-2026 10:03:50 Agreement is prompted by Broadcom.
build 13-Jan-2026 10:03:50
build 13-Jan-2026 10:03:50 To view the Broadcom Foundation Agreement, please see
build 13-Jan-2026 10:03:50 https://www.broadcom.com/company/legal/licensing.
build 13-Jan-2026 10:03:50
build 13-Jan-2026 10:03:50 If you agree, the essential plugins (required by the Tanzu CLI) will be
build 13-Jan-2026 10:03:50 automatically installed.
build 13-Jan-2026 10:03:50
build 13-Jan-2026 10:03:50 Note: this prompt can be avoided by running "tanzu config eula accept".
build 13-Jan-2026 10:03:50
build 13-Jan-2026 10:03:50 Do you agree to the Broadcom Foundation Agreement?
build 13-Jan-2026 10:03:50 [0m [36m[Use arrows to move, type to filter][0m
build 13-Jan-2026 10:03:50 [1;36m> Yes[0m
build 13-Jan-2026 10:03:50 [39m No[0m
error 13-Jan-2026 10:24:40 Force Stop build feature is enabled for current plan. Either Bamboo has detected the build has hung or it has been manually stopped.
simple 13-Jan-2026 10:24:40 Attempting to generate stack trace and terminate spawned sub-processes of process id: 1338357
simple 13-Jan-2026 10:24:40 Found related process: pid: 2204401 ppid: 1338357 pgid: 214772 %cpu: 0.0 %mem: 0.0 cmd: /bin/bash
simple 13-Jan-2026 10:24:40 Found related process: pid: 2204413 ppid: 2204401 pgid: 214772 %cpu: 0.0 %mem: 0.2 cmd: tanzu
simple 13-Jan-2026 10:24:40 getStackTraceAndKillRelatedProcesses for 2 processes
simple 13-Jan-2026 10:24:40 Executing kill -3 2204413
simple 13-Jan-2026 10:24:40 Executing kill -3 2204401
error 13-Jan-2026 10:24:40 SIGQUIT: quit
error 13-Jan-2026 10:24:40 PC=0x408a2c m=0 sigcode=0
This is most likely showing up because it may have been a year since you last accepted the EULA, or the EULA has changed, and a different one was used since you last accepted it.
To resolve this issue, the user will need to add/use 'tanzu config eula accept' in their pipeline.