-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
-
False
-
-
Description of problem:
I have a private repository on GitLab and I'm trying to use (via Konflux) a remote pipeline from another (private) repo in the same group.
It works OK via Tekton git resolver, i.e.
pipelineRef:
resolver: git
params:
- name: serverURL
value: https://gitlab.com
- name: org
value: redhat/rhel/containers
- name: repo
value: tekton-pipelines
- name: pathInRepo
value: .tekton/build-pipeline.yaml
- name: revision
value: main
- name: scmType
value: gitlab
- name: token
value: pipelines-as-code-secret
- name: tokenKey
value: password
But when I try using the PAC annotation
pipelinesascode.tekton.dev/pipeline: https://gitlab.com/redhat/rhel/containers/tekton-pipelines/raw/main/.tekton/build-pipeline.yaml
I get Non-OK HTTP status: 403
PAC already has a token for the group so it should be able to access the remote pipeline.
I asked here and was told to open an issue in SRVKP.
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
/retest here (you need to be in bugzilla-redhat LDAP group and login via SSO)
Actual results:
There was an issue validating the commit: "error getting remote pipeline from pipelinerun annotations: error getting remote pipeline "https://gitlab.com/redhat/rhel/containers/tekton-pipelines/raw/main/.tekton/build-pipeline.yaml\": Non-OK HTTP status: 403"
Expected results:
Pipeline starts.
Reproducibility (Always/Intermittent/Only Once):
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):