Bug 2087035 - Pipeline didnt get triggered after the PR is created in ADO, issue with pipelines operator in 4.9v of openshift
Summary: Pipeline didnt get triggered after the PR is created in ADO, issue with pipel...
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenShift Pipelines
Classification: Red Hat
Component: pipelines
Version: 1.7
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Vincent Demeester
QA Contact: Ruchir Garg
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-17 07:51 UTC by sushma
Modified: 2023-07-21 23:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description sushma 2022-05-17 07:51:11 UTC
Description of problem:

We have updated ARO from 4.8 to 4.9 and noticed there is issue with pipelines(see the below error), which is Pipeline is not getting triggered after Pull request is created in Azure Devops.

admission webhook "webhook.triggers.tekton.dev" denied the request: mutation failed: cannot decode incoming new object: json

So when i checked, i see that it is bug in 1.1.2v and it was fixed in 1.5.2v release.
So, i have updated to the latest version of pipelines operator which is 1.7v

But even after updated the issue is not resolved.



Version-Release number of selected component (if applicable):1.7v


How reproducible: Upgrade to 1.7v of pipelines operator


Steps to Reproduce:
1.Create pull request in Azure Devops
2.Check the pipeline pod logs
3.check the pipelinerun of that pipeline, which will show that new pipelinerun didnt happen.

Actual results: Pipeline didnt get triggered after the PR is created in ADO


Expected results: Pipeline should be triggered as soon as the PR is created in ADO



Additional info: We are blocked with deployments because of this issue.

I suspect this also have link with the API's deprecation in 1.22v of K8S which is used in ARO v4.9.

Error:

 "logger":"eventlistener","caller":"sink/sink.go:381","msg":"could not resolve interceptor URL: url resolution failed for interceptor  with: name is required","commit":"8b4da3f","eventlistener":"honda-exo-be-pull-request-check-listener","namespace":"honda-pipelines-env","/triggers-eventid":"c310ed5a-4792-48e3-8a72-de045ff29337","eventlistenerUID":"25cf7f25-57fd-41f0-bf27-31c86c41abf5","/triggers-eventid":"c310ed5a-4792-48e3-8a72-de045ff29337","/trigger":"honda-exo-be-pull-request-check-trigger","stacktrace":"github.com/tektoncd/triggers/pkg/sink.Sink.processTrigger\n\t/opt/app-root/src/go/src/github.com/tektoncd/triggers/pkg/sink/sink.go:381\ngithub.com/tektoncd/triggers/pkg/sink.Sink.HandleEvent.func1\n\t/opt/app-root/src/go/src/github.com/tektoncd/triggers/pkg/sink/sink.go:196"}

Comment 1 sushma 2022-05-17 08:03:51 UTC
from 1.1.2v i have update to v1.6.2v, i have recived below error.

Error from server (InternalError): Internal error occurred: failed calling webhook "validation.webhook.pipeline.tekton.dev": Post "https://tekton-pipelines-webhook.openshift-pipelines.svc:443/resource-validation?timeout=10s": service "tekton-pipelines-webhook" not found.


So i have updated to the latest version 1.7.


Note You need to log in before you can comment on or make changes to this bug.