Pods assigned with Multus whereabouts IP get stuck in ContainerCreating state after node reboot in OCP 4

Solution Verified - Updated -

Issue

  • Pods assigned with Multus whereabouts IP get stuck in ContainerCreating state after node reboot.
  • When starting a container this error is thrown:

    error adding container to network "ipvlan-net": Error at storage engine: Could not allocate IP in range: ip: 10.10.10.0 / - 10.10.10.254 / range: net.IPNet{IP:net.IP{0xa, 0xa, 0xa, 0x0}, Mask:net.IPMask{0xff, 0xff, 0xff, 0x0}}
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.x

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