-
Bug
-
Resolution: Done
-
Critical
-
None
-
ACM 2.10.0
-
False
-
None
-
False
-
No
-
+
-
-
-
Important
Description of problem:
The multicluster-observability-operator pod getting OOMKilled:
containerStatuses:
- restartCount: 11
started: false
ready: false
name: multicluster-observability-operator
state:
waiting:
reason: CrashLoopBackOff
message: back-off 5m0s restarting failed container=multicluster-observability-operator pod=multicluster-observability-operator-684cc68967-4zt7z_open-cluster-management(7eac2186-9d7a-4d42-b461-355dcb64ee17)
imageID: 'registry.redhat.io/rhacm2/multicluster-observability-rhel9-operator@sha256:8080a961b0bc904fcc801d18ac00a6dd2fa07aba7d6410211a65aed96e1ac6ff'
image: 'registry.redhat.io/rhacm2/multicluster-observability-rhel9-operator@sha256:8080a961b0bc904fcc801d18ac00a6dd2fa07aba7d6410211a65aed96e1ac6ff'
lastState:
terminated:
exitCode: 137
reason: OOMKilled
startedAt: '2024-04-11T14:14:48Z'
finishedAt: '2024-04-11T14:15:59Z'
containerID: 'cri-o://1abad92de96270b3fbd4cfa353ed755a8ca8ff806f819d1e33ed6aa6ee10a533'
containerID: 'cri-o://1abad92de96270b3fbd4cfa353ed755a8ca8ff806f819d1e33ed6aa6ee10a533'
qosClass: Burstable
Version-Release number of selected component (if applicable):
ACM 2.10.0
How reproducible:
Always
Steps to Reproduce:
- Upgrade ACM 2.9.3 with Observability enabled to 2.10.0
Actual results:
The multicluster-observability-operator pod getting OOMKilled and getting into CrashLoopBackOff state.
Expected results:
The multicluster-observability-operator pod should be running after the successful upgrade to 2.10.0 version
Additional info:
- Current limits:
containers: - resources: limits: cpu: 600m memory: 1Gi requests: cpu: 100m memory: 128Mi - Not able to change the default memory limit by following the KCS as multicluster-observability-operator resource is unavailable in the csv: https://access.redhat.com/solutions/7031620 .
$ oc get csv advanced-cluster-management.v2.10.0 -n open-cluster-management -oyaml