Skip to content

Commit

Permalink
update
Browse files Browse the repository at this point in the history
  • Loading branch information
treddy08 committed Sep 9, 2024
1 parent 07868b6 commit 53896a1
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/modules/ROOT/pages/14-troubleshooting.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ When ordering this demo from demo.redhat.com, you cluster will be woken up from

==== Webhook not triggering pipeline run

You will notice that any source code changes, tagging and releasing will not trigger a pipeline. To confirm this issue, navigate to your software components *xxx-dev* project and go to *Workloads -> Pods* then locate the *event listener* pod with the name *el-<component>-el**. If you select the *Logs* tab, you should notice a certificate error while communicating *tekcon-trigger-core-interceptors* service. To fix this issue, switch the project to *openshift-pipelines* and go to *Workloads - Pods*. Find the pod *tekton-triggers-core-interceptors-** and delete it. This action should recreat the pod and should resolve this issue. Attempt to trigger the pipeline again.
You will notice that any source code changes, tagging and releasing will not trigger a pipeline. To confirm this issue, navigate to your software components *xxx-dev* project and go to *Workloads -> Pods* then locate the *event listener* pod with the name *el-<component>-el\**. If you select the *Logs* tab, you should notice a certificate error while communicating *tekton-trigger-core-interceptors* service. To fix this issue, switch the project to *openshift-pipelines* and go to *Workloads - Pods*. Find the pod *tekton-triggers-core-interceptors-** and delete it. This action should recreat the pod and should resolve this issue. Attempt to trigger the pipeline again.

[Important]
====
Expand Down

0 comments on commit 53896a1

Please sign in to comment.