-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.17.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The CVO pod streams too many unwanted logs even on fresh cluster. [1] 2025-04-09T01:22:54.561995277Z W0409 01:22:54.561967 1 warnings.go:70] unknown field "spec.signatureStores" ... $ oc logs cluster-version-operator-66fc567d9f-mm7rh |grep "spec.signatureStores" | wc -l 7207 [2] 2025-04-09T01:22:36.915496164Z I0409 01:22:36.915454 1 metrics.go:553] skipping metrics for csi-snapshot-controller ClusterOperator condition EvaluationConditionsDetected=Unknown (neither True nor False) ... $ oc logs cluster-version-operator-66fc567d9f-mm7rh |grep "skipping metrics" | wc -l 61919 [3] 2025-04-10T00:48:46.577160739Z I0410 00:48:46.577125 1 rbac.go:38] Updating ClusterRoleBinding cluster-baremetal-operator due to diff: &v1.ClusterRoleBinding{ ... $ oc logs cluster-version-operator-66fc567d9f-mm7rh |grep "due to diff" | wc -l 874
Version-Release number of selected component (if applicable):
4.17.22
How reproducible:
100%
Steps to Reproduce:
1. Deploy a fresh cluster 4.17.z 2. Check logs of cluster-version-operator pod after some time 3.
Actual results:
There are some suspicious / unwanted logs streaming repeatedly.
Expected results:
If the cluster is healthy, then such logs should not be streaming.
Additional info:
- duplicates
-
OCPBUGS-36246 CVO hot looping on configmap and ClusterRoleBinding resources
-
- New
-