-
Bug
-
Resolution: Done
-
Major
-
Pipelines 1.11.0, Pipelines 1.10.5
-
2
-
False
-
None
-
False
-
Triggers core interceptor now create secrets whenever its necessary
-
-
-
Pipelines Sprint 251, Pipelines Sprint 252
Description of problem:
Eventlistener pod logs complain about the CA trust issue connecting to tekton trigger:
x509: certificate signed by unknown authority (possibly because of \"x509: ECDSA verification failure\" while trying to verify candidate authority certificate \"tekton-triggers-core-interceptors.openshift-pipelines.svc\")","
When checked `spec.clientConfig.caBundle` in clusterinterceptor, the value differs from the `ca-cert.pem` value in secret `tekton-triggers-core-interceptors-certs`
Workaround
Following below KCS works but when the nodes are restarted, the issue reappears.
https://access.redhat.com/solutions/7024276
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
# <steps>
Actual results:
The CA certs are not updated correctly in the ClusterInterceptors after node reboot.
Expected results:
**
The CA certs should get updated correctly in the ClusterInterceptors after node reboot.
Reproducibility (Always/Intermittent/Only Once):
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):