-
Bug
-
Resolution: Unresolved
-
Major
-
Pipelines 1.15.2
-
1
-
False
-
-
False
-
Fixed excessive logging issue in OpenShift Pipelines Operator that was generating 2000+ log lines per second, demoted high-frequency debug operations from INFO to DEBUG level, reducing log volume
-
Bug Fix
-
Proposed
-
-
Description of problem:
The OpenShift Pipelines Operator is generating excessive logs (62 million logs in 15 hours) causing external logging systems to crash. Analysis reveals two root causes:
1. Excessive "Image not found" logs: Repeated at 2000+ lines/second using uncontrolled `log.Println` instead of structured logging
case https://access.redhat.com/support/cases/#/case/04363399
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
1. Install OpenShift Pipelines Operator 1.15
2. Create TektonConfig CR to trigger installation
3. Monitor operator logs:
oc logs deploy/openshift-pipelines-operator -c openshift-pipelines-operator-lifecycle -f
oc logs deploy/openshift-pipelines-operator -c openshift-pipelines-operator-lifecycle | wc -l
Actual results:
- Excessive Logging:
- 2000+ log lines per second
- "Image not found" messages repeated continuously
Expected results:
**
- Controlled Logging:
- "Image not found" messages use structured logger at DEBUG level
Reproducibility (Always/Intermittent/Only Once):
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):
*
- clones
-
SRVKP-10639 Fix Excessive Logging in OpenShift Pipelines Operator
-
- Verified
-