-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
4.15
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
No
-
None
-
None
-
Rejected
-
Ivysaur OLM Sprint 269
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
redhat-operator in openshift-marketplace needs a lot of CPU resources every 15 minutes on OCP 4.15.8. >1.6 CPU for 5+ minutes?
Log:
$ $ oc logs -n openshift-marketplace redhat-operators-5z8zd Defaulted container "registry-server" out of: registry-server, extract-utilities (init), extract-content (init) time="2024-04-23T08:14:02Z" level=info msg="starting pprof endpoint" address="localhost:6060" time="2024-04-23T08:14:04Z" level=info msg="serving registry" configs=/extracted-catalog/catalog port=50051 time="2024-04-23T08:14:04Z" level=info msg="stopped caching cpu profile data" address="localhost:6060"
Status:
$ oc get catalogsources.operators.coreos.com -n openshift-marketplace redhat-operators -o yaml|tail -n12 status: connectionState: address: redhat-operators.openshift-marketplace.svc:50051 lastConnect: "2024-04-23T08:14:55Z" lastObservedState: READY latestImageRegistryPoll: "2024-04-23T10:32:51Z" registryService: createdAt: "2024-04-23T08:13:56Z" port: "50051" protocol: grpc serviceName: redhat-operators serviceNamespace: openshift-marketplace
- duplicates
-
OCPBUGS-48697 OLMv0: excessive catalog source snapshots cause severe performance regression [openshift-4.15.z]
-
- Closed
-
-
OCPBUGS-36421 redhat-operators pod experiencing unusually high CPU utilization
-
- Closed
-
-
OCPBUGS-38751 openshift-marketplace pods affect etcd sync latencies
-
- Closed
-
- is caused by
-
OCPBUGS-52422 OPM no longer prunes metadata from non-channel heads
-
- New
-
- links to