Reason "CoundNotGetTask" Provided if TaskRun Creation Fails

[adambkaplan]

Bug Report

Description

If the TaskRun for the associated BuildRun cannot be created, the listed failure reason is CouldntGetTask. This failure reason is misleading if the underlying TaskRun can't be created in the first place. This can happen, for instance, if the referenced build strategy requires additional security capabilities that are not granted to the user or service account for the build.

Expected Behavior

The failure reason more readily identifies the cause, in this case CreateTaskRunFailed

Actual Behavior

Reason provided is CouldntGetTask, which can be confusing since Shipwright does not create Tekton Tasks.

/kind bug

Notes

This issue was filed a long time ago. Help is needed to verify if this is an issue running Shipwright build on top of Tekton Pipelines v0.47.x

[SaschaSchwarze0]

From Grooming: CreatePodFailed would be even a better reason because we successfully create the TaskRun and Tekton fails to create the Pod.

[qu1queee]

From Grooming: @adambkaplan to revisit this directly with the Tekton community, as SHP relies on the Tekton status condition subresource from a TaskRun.

[qu1queee]

From Refinement, to validate if the use case continues with the latest Tekton updates.