-
Bug
-
Resolution: Unresolved
-
Critical
-
CNV v4.18.0
-
1
-
False
-
-
False
-
CNV v4.18.0.rhel9-787
-
---
-
---
-
-
None
Description of problem:
On a large cluster, when spinning a large number of VMs (500), not all the VMs are running, and the kubevirt-ipam-controller-manager pod is stuck in a CrashLoopBackOff status.
Version-Release number of selected component (if applicable):
4.18.0-rc.4
How reproducible:
Steps to Reproduce:
1. On a large cluster, deploy a large amount of VMs (500).
Actual results:
Not all the VMs are running, and the kubevirt-ipam-controller-manager pod is stuck in a CrashLoopBackOff status.
When describing the pod you can see it was terminated due to oomkilled:
Last State: Terminated
Reason: OOMKilled
Exit Code: 137
Expected results:
All VMs should be running succesfully.
Additional info:
- is related to
-
CNV-55356 KubeletConfig autoSizingReserved should be enabled also in master nodes
-
- To Do
-
- links to
-
RHEA-2024:139653
OpenShift Virtualization 4.18.0 Images
