-
Story
-
Resolution: Unresolved
-
Critical
-
Pipelines 1.19.0
-
2
-
False
-
-
False
-
-
-
Pipelines Sprint Pioneers 39, Pipelines Sprint Pioneers 40
*###Issue : *
A pipeline will experience a silent failure after a timeout, if its .spec.tasks[*].taskRef.apiVersion field is configured with an invalid value, making it difficult to diagnose the problem because no explicit errors are thrown.
The customer expects that it should provide a clear and specific error message when an incorrect value is assigned to the .spec.tasks[*].taskRef.apiVersion field in pipeline. Instead of failing silently after a timeout, the pipeline should immediately flag the invalid apiVersion so the issue can be quickly identified and resolved.
- is documented by
-
RHDEVDOCS-6799 Document the new behavior of ".spec.tasks[*].taskRef.apiVersion" field set to an incorrect value
-
- Open
-
- links to