From 53896a19aba9c3e527e4b2aa944cfc5ac81de01d Mon Sep 17 00:00:00 2001 From: treddy08 Date: Mon, 9 Sep 2024 13:41:19 +1000 Subject: [PATCH] update --- content/modules/ROOT/pages/14-troubleshooting.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/modules/ROOT/pages/14-troubleshooting.adoc b/content/modules/ROOT/pages/14-troubleshooting.adoc index ca5f297..fa977e7 100644 --- a/content/modules/ROOT/pages/14-troubleshooting.adoc +++ b/content/modules/ROOT/pages/14-troubleshooting.adoc @@ -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--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--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] ====