Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-11903

[1958108] KubeMacPool fails to start due to OOM likely caused by a high number of Pods running in the cluster

XMLWordPrintable

    • High
    • None

      Description of problem:
      When KubeMacPool boots, it attempts to reconcile all already allocated MAC addresses in the cluster. On a big cluster, this can lead into OOM.

      This issue was originally raised on https://bugzilla.redhat.com/show_bug.cgi?id=1851829#c6. Find more info and captured artifacts there.

      Version-Release number of selected component (if applicable):
      CNV 2.5.5

      How reproducible:
      Always on customer's environment, so far we failed to reproduce it locally.

      Steps to Reproduce:
      1. Have a cluster with thousands of Pods
      2. ... the step above alone is not enough as we were not able to reproduce it locally
      3. Install OpenShift Virtualization
      Actual results:
      The KubeMacPool pod gets killed by kubelet due to OOM. This can be observed through `oc describe pod ...`.

      Expected results:
      KubeMacPool must not fail due to high number of pods. OpenShift Virtualization should be successfully installed and start running.

      Additional info:
      When KubeMacPool pod's memory limit is removed (or raised), this issue does no occur.

              ralavi@redhat.com Ram Lavi
              phoracek@redhat.com Petr Horacek
              Ofir Nash Ofir Nash (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: