-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
4.12
-
No
-
Rejected
-
False
-
-
Customer Escalated
-
-
Description of problem:
Even after configuriung the whereabouts uisng network attachment defination pods are still in pending state with the below error. ~~~ error adding container to network "mh0": Error at storage engine: Could not allocate IP in range: ip: x.x.x.x / - x.x.x.x / range: net.IPNet{IP:net.IP{0xa, 0x49, 0x4, 0x0}, Mask:net.IPMask{0xff, 0xff, 0xff, 0x0} ~~~
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.Forcefully shutting down one of the nodes running a statefulset pod, and then force deleting the pod I was able to get the new Pod created by manually editing the IPPool and removing the allocation in question from the spec. I also deleted the OverlappingRangeIPReservation related to the allocation. This allowed the IP to be issued to the new Pod.
Actual results:
Expected results:
Additional info:
- duplicates
-
OCPBUGS-16008 pods assigned with Multus whereabouts IP get stuck in ContainerCreating state after OCP upgrading [Backport 4.12]
- Closed