-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Open
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Milestone
Description
Expected Behavior
In case of error use existing name on a task resolved on git instead of metadata name
Actual Behavior
In case of error an empty name is provided, making hard to detect error:
Pipeline devtoolsqe--pipeline/crc-qe-virtualized can't be Run; it contains Tasks that don't exist: Couldn't retrieve Task "": error requesting remote resource: invalid resource request "devtoolsqe--pipeline/git-97649dfef75c38b5bbde423fa9875e7b": failed to validate params: missing required hub resolver params: name, version
it made up too the resolver (hub, bundles) and fail with various errors, but if we can use the task name instead of metadata name (which looks like is not fetched) resolve problems would be easier
Steps to Reproduce the Problem
- Create a pipeline with a task fetched by git resolver (several ones a set one of them with an incorrect pathInRepo
- run the pipeline and see the error points to Task "", so you cannot identify problematic task
Additional Info
Related code, where only metadata.name is used:
"Pipeline %s/%s can't be Run; it contains Tasks that don't exist: %s", |
- Kubernetes version:
$ kubectl version
Client Version: v1.29.7
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.15+6147456
WARNING: version difference between client (1.29) and server (1.27) exceeds the supported minor version skew of +/-1
$ oc version
Client Version: 4.16.13
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Kubernetes Version: v1.27.15+6147456
- Tekton Pipeline version:
not sure how to retrieve this
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Type
Projects
Status
Todo