-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
With this fix, Pipelines as Code will match PipelineRun resources based on `name` or `generateName` field in incoming webhook events.
-
-
-
Pipelines Sprint Crookshank 18, Pipelines Sprint Crookshank 19
Description of problem:
When PipelineRun has defined metadata.generateName, the incoming webhook functionality will not find the PipelineRun and PAC controller returns: `cannot find pipelinerun windows11-qe-virtio-installer-run- for matching an incoming event in this repository`. When the I change the metadata.generateName to metadata.name the incoming webhook works.
https://redhat-internal.slack.com/archives/C0382KN768J/p1732520695203379
Prerequisites (if any, like setup, operators/versions):
OCP - 4.17
OCP Pipelines operator - 1.16.1
Steps to Reproduce
1) have PipelineRuns with metadata.generateName in .tekton folder (as. e.g. like here https://gitlab.cee.redhat.com/openshift-virtualization/windows-image-builder/-/blob/main/.tekton/windows-qe-virtio.yaml?ref_type=heads#L2)
2) Configure incoming webhook functionality
3) trigger `https://<PAC cluster URL>/incoming?secret=<Token>&repository=windows-image-builder&branch=main&pipelinerun=windows2k22-qe-virtio-installer-run`
4) Observe logs in PAC controller that it can't find the PipelineRun
Actual results:
PipelineRun is not triggered
Expected results:
PipelineRun is triggered
Reproducibility (Always/Intermittent/Only Once):
Always
Additional info (Such as Logs, Screenshots, etc):
PipelineRun definition and log from PAC controller are attached