Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-v0.50.x] Make sure we use the correct namespace for remote Pipeline validation #7023

Conversation

tekton-robot
Copy link
Collaborator

This is an automated cherry-pick of #7017

/assign vdemeester

Fix validation errors when using the cluster resolver

In the case of using the cluster resolver, the fetched `Pipeline` will
have a namespace attached to it, which **will** be different from the
current namespace (where the `PipelineRun` is applied). This causes
the following error when using the cluster resolver:

```
validation failed for referenced Pipeline pipeline-name: the namespace of the provided object does not match the namespace sent on the request
```

This make sure we use the PipelineRun's namespace namespace when doing
the remote `Pipeline` validation.

This fixes tektoncd#7015.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@tekton-robot tekton-robot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Aug 3, 2023
@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Aug 3, 2023
@vdemeester
Copy link
Member

/approve
/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 3, 2023
@tekton-robot
Copy link
Collaborator Author

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 3, 2023
@lbernick
Copy link
Member

lbernick commented Aug 3, 2023

/lgtm

@JeromeJu
Copy link
Member

JeromeJu commented Aug 3, 2023

/kind bug

@tekton-robot tekton-robot added the kind/bug Categorizes issue or PR as related to a bug. label Aug 3, 2023
@JeromeJu
Copy link
Member

JeromeJu commented Aug 3, 2023

/retest

@tekton-robot tekton-robot merged commit 77f7b15 into tektoncd:release-v0.50.x Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants