Cluster Application Migration Operator Migration-Controller is being OOMkilled

Solution Verified - Updated -

Issue

  • The migration-controller pod is being OOMKilled and the pod keeps restarting indefinitely.

    $ oc get pods -n openshift-migration
    NAME                                    READY   STATUS      RESTARTS   AGE
    migration-controller-859b57c546-c9wz2   0/2     OOMKilled   1          24s
    migration-operator-f847f8657-8t85d      2/2     Running     0          92m
    migration-ui-5d7998b74f-5p6zt           1/1     Running     0          89m
    restic-c2wdb                            1/1     Running     0          90m
    restic-d8ppp                            1/1     Running     0          90m
    restic-drgqk                            1/1     Running     0          90m
    restic-fjsxl                            1/1     Running     0          90m
    restic-ft8fg                            1/1     Running     0          90m
    velero-5bffbd77c4-cmlsx                 1/1     Running     0          90m
    
  • Because the Pod is being managed by the Cluster Application Migration Operator, the resources.limits.memory field is being reset by the Operator.

Environment

  • OpenShift Container Platform (OCP) 4.3
  • Cluster Application Migration Operator 1.1.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In