csmbot
commented
3 weeks ago @anurajpd: Thank you for submitting this issue!
The issue is currently awaiting triage. Please make sure you have given us as much context as possible.
If the maintainers determine this is a relevant issue, they will remove the needs-triage label and respond appropriately.
We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at container.storage.modules@dell.com.
Bug Description
CSM Operator pod OOMKilled 24 nodes in the cluster increased the resource to 4Gi memory and 2000m cpu to get the pod in running state
Logs
Containers: manager: Container ID: cri-o://a7c60ac454f42e772c26dfd91cf3dcb5cebf0a4691c39996c61cbb0b5bb7a379 Image: /dell-csm-operator:v1.5.0 Image ID: /dell-csm-operator@sha256:d653f510bb9eaa3e89824accef28efd00eb2b1bdd11b7006744f2740eead280b Port:
Host Port:
Command:
/manager
Args:
--leader-elect
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: OOMKilled
Exit Code: 137
Started: Wed, 05 Jun 2024 17:48:16 +0800
Finished: Wed, 05 Jun 2024 17:48:39 +0800
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
create csm
Expected Behavior
operator pod should not crachloop
CSM Driver(s)
PowerScale 2.10.0
Installation Type
Operator v1.5.0
Container Storage Modules Enabled
No response
Container Orchestrator
OpenShift 4.14
Operating System
CoreOS