Pods failing with OutOfcpu or OutOfmemory in OpenShift 4

Solution Verified - Updated -

Issue

  • There are pods failing with reason OutOfcpu or OutOfmemory, even if they have configured requests and limits.
  • Some pods are failing to run after they are scheduled in a node.
  • There are pods showing OutOfcpu or OutOfmemory messages:

    application-pod           0/1     OutOfcpu     0          2h
    application2-pod          0/1     OutOfmemory  0          2h
    
      message: 'Pod was rejected: Node didn't have enough resource: cpu, requested: 200, used: 12769, capacity: 12800'
      phase: Failed
      reason: OutOfcpu
    
    2h        Normal    Scheduled                      pod/application-pod                         Successfully assigned my-project/application-pod to [node_name]
    2h        Warning   OutOfcpu                       pod/application-pod                         Node didn't have enough resource: cpu, requested: 200, used: 12769, capacity: 12800
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content