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

Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_collect-profiles-27984525-hfrqg_openshift-operator-lifecycle-manager_3b2980b7-514f-4344-aaa2-09e53b571561_0(9ab31dfae16548a70554f127080c0226e1586568bb1027a579430c4c1ff888fb): error adding pod openshift-operator-lifecycle-manager_collect-profiles-27984525-hfrqg to CNI network "multus-cni-network": plugin type="multus" name="multus-cni-network" failed (add): [openshift-operator-lifecycle-manager/collect-profiles-27984525-hfrqg/3b2980b7-514f-4344-aaa2-09e53b571561:openshift-sdn]: error adding container to network "openshift-sdn": CNI request failed with status 400: 'failed to run IPAM for 9ab31dfae16548a70554f127080c0226e1586568bb1027a579430c4c1ff888fb: failed to run CNI IPAM ADD: failed to allocate for range 0: no IP addresses available in range set: 10.7.105.1-10.7.105.254

The customer tried manually rebooting the node and that fixed the issue for a while and again it persists.

Followed the below steps to release the IP's but the issue is repeating:

• Unschedule the node and drain with `$ oc adm drain <node> --delete-local-data --ignore-daemonsets`
• then remove the "/var/lib/cni/networks/openshift-sdn/*" content:
• verified that IP's released and scheduled the node.

**https://access.redhat.com/solutions/5943591