-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.15, 4.17
-
No
-
Wolverine OLM Sprint 257, XMen OLM Sprint 258, Glaceon OLM Sprint 267
-
3
-
Rejected
-
False
-
Description of problem:
In ROSA cluster (29ravr8i7na7j7vrv69qojgee9ng034l), redhat-operators pod located on one of the master nodes was experiencing unusually high CPU utilization. This issue was not observed on the other master nodes. After restarting the pod, the CPU utilization returned to normal levels.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
Below are the outputs of the ps auxww --sort=-%cpu | head command. BEFORE: 1000230+ 2425215 >> 154 << 0.2 2731508 86932 ? Ssl Jun27 1705:36 /bin/opm serve /extracted-catalog/catalog --cache-dir=/extracted-catalog/cache AFTER: 1000230+ 787865 >> 5.5 << 0.3 2651328 105036 ? Ssl 09:27 4:53 /bin/opm serve /extracted-catalog/catalog --cache-dir=/extracted-catalog/cache Attaching must-gather in the comment section.
- duplicates
-
OCPBUGS-42005 Catalog Operator pods CPU spike every few minutes
-
- Closed
-
- is duplicated by
-
OCPBUGS-33094 redhat-operator needs a lot of CPU resources every 15 minutes
-
- New
-
-
OCPBUGS-38944 The redhat-operators catalogsource pod is using high CPU
-
- Closed
-
-
OCPBUGS-36811 [RHOCP 4.15] redhat-operators pod taking CPU
-
- Closed
-
-
OCPBUGS-50952 redhat-operators pod consuming lot of the master node's CPU
-
- Closed
-
- relates to
-
OCPBUGS-48697 OLMv0: excessive catalog source snapshots cause severe performance regression [openshift-4.15.z]
-
- Closed
-
-
OCPBUGS-38751 openshift-marketplace pods affect etcd sync latencies
-
- Closed
-