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 (OpenShift Container Platform 4.10.21 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.
https://access.redhat.com/errata/RHBA-2022:5428
Hi - As requested by Martin Kennelly. My customer is running a disconnected v4.10.22 cluster (OCP on OSP) using ovn-kubernetes and we are still seeing this bug. Example pod error message:
addLogicalPort failed for <<namespaces>>/<<pod>>: failed to assign pod address for pod <<pod>> no node: worker-node, err: range is full.
The other way to resolve this is to either keep deleting the pod until it hits a node it can come up on, or removing all Completed / Error pods on the cluster.
If this could be re-looked at I would be most grateful.
Thanks - Dave
Comment 14Red Hat Bugzilla
2023-09-18 04:37:57 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days