+++ This bug was initially created as a clone of Bug #1898670 +++
Description of problem: When using a daemonset and a Whereabouts range gets exhausted, a pod can get stuck in a containercreating state indefinitely.
How reproducible: Always.
Steps to Reproduce:
Create a net-attach-def:
Create a deployment:
- image: busybox:latest
command: [ "/bin/sh", "-c", "while true; do date; sleep 10; done"]
List the pods (oc get pods -w), you'll show one pod running.
Delete that pod. (oc delete pod multustest2-594975985d-clp6z) for example.
That pod is stuck in a ContainerCreating status, indefinitely.
Pod is recreated normally after it's deleted.
Tested and verified in 4.6.0-0.nightly-2021-01-30-211400
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: OpenShift Container Platform 4.6.16 security and bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.