Pods stuck in ContainerCreating - "Failed to run CNI IPAM ADD: failed to allocate for range 0" on OCP 4

Solution Verified - Updated -

Issue

  • On OpenShift Container Platform 4.6, pods fail to start with the following error message:

    Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_example-129-deploy_example_2ac1743b-4739-46e1-ad6c-5bd669b6bf6b_0(66fd8ea801b26df11e890b9cb9afbd2fcea8d6063e331e9a6e7dccebbaefb4b4): [example/example-129-deploy:openshift-sdn]: error adding container to network "openshift-sdn": CNI request failed with status 400: 'failed to run IPAM for 66fd8ea801b26df11e890b9cb9afbd2fcea8d6063e331e9a6e7dccebbaefb4b4: failed to run CNI IPAM ADD: failed to allocate for range 0: no IP addresses available in range set: 10.177.220.1-10.177.221.254 '

  • Pod deployments failing with the following messages:

    Failed to create pod sandbox: rpc error: code = Unknown desc = Kubelet may be retrying requests that are timing out in CRI-O due to system load: error reserving pod name k8s_customer-information-xxx: name is reserved

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.6
    • 4.7
    • 4.8

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