-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
-
False
-
-
The Tekton documentation states that when a TaskRun references a result from a previous TaskRun, but the previous TaskRun fails to initialize the result, the PipelineRun will fail with a message like "InvalidTaskResultReference" :
unable to find result referenced by param 'foo' in 'task';: Could not find result with name 'commit' for task run 'checkout-source'
The actual behavior is the PipelineRun fails with the reason PipelineValidationFailed and no other context. The controller logs emit an info log like "Failed to resolve task result reference for "deployment-validation-operator-fbc-on-pull-request-mlgxw" with error Invalid task result reference: Could not find result with name RENDERED_CATALOG_DIGEST for task validate-fbc", but no event is emitted on the PipelineRun, and the PipelineRun's status does not mention which Task failed validation or what about the Validation failed.
Reproduction Steps:
- Have a kind or Openshift cluster running Tekton or Openshift Pipelines
- In the tektoncd/pipeline repository, modify examples/v1/pipelinejruns/task_results_example.yaml: modify the Multiply Task so that it does not write to the product result by deleting `| tee $(results.product.path)` from line 91
- Create the pipelinerun with kubectl create -f ./examples/v1/pipelineruns/task_results_example.yaml
- Observe the failure mode.