Verified this bug on 4.10.0-0.nightly-2022-06-30-014715 ovnkube-master-7cqm9-ovnkube-master.log:I0630 04:00:05.421865 1 ovn.go:687] Detected completed pod: openshift-operator-lifecycle-manager_collect-profiles-27609360-4klmj. Will remove. ovnkube-master-7cqm9-ovnkube-master.log:I0630 04:00:05.422036 1 pods.go:200] Releasing IPs for Completed pod: openshift-operator-lifecycle-manager/collect-profiles-27609360-4klmj, ips: 10.128.2.16 ovnkube-master-7cqm9-ovnkube-master.log:I0630 04:15:06.250055 1 ovn.go:687] Detected completed pod: openshift-operator-lifecycle-manager_collect-profiles-27609375-bpdp5. Will remove. ovnkube-master-7cqm9-ovnkube-master.log:I0630 04:15:06.250227 1 pods.go:200] Releasing IPs for Completed pod: openshift-operator-lifecycle-manager/collect-profiles-27609375-bpdp5, ips: 10.128.2.19 ovnkube-master-7cqm9-ovnkube-master.log:I0630 04:16:37.594257 1 ovn.go:687] Detected completed pod: openshift-operator-lifecycle-manager_collect-profiles-27609375-bpdp5. Will remove. ovnkube-master-7cqm9-ovnkube-master.log:I0630 04:16:37.594876 1 ovn.go:687] Detected completed pod: openshift-operator-lifecycle-manager_collect-profiles-27609345-zgjmv. Will remove. ovnkube-master-7cqm9-ovnkube-master.log:I0630 04:16:37.601908 1 ovn.go:726] Ignoring delete event for completed pod openshift-operator-lifecycle-manager/collect-profiles-27609375-bpdp5 ovnkube-master-7cqm9-ovnkube-master.log:I0630 04:16:37.609332 1 ovn.go:726] Ignoring delete event for completed pod openshift-operator-lifecycle-manager/collect-profiles-27609345-zgjmv ovnkube-master-7cqm9-ovnkube-master.log:I0630 04:16:37.797955 1 ovn.go:687] Detected completed pod: openshift-operator-lifecycle-manager_collect-profiles-27609360-4klmj. Will remove. ovnkube-master-7cqm9-ovnkube-master.log:I0630 04:16:37.800792 1 ovn.go:726] Ignoring delete event for completed pod openshift-operator-lifecycle-manager/collect-profiles-27609360-4klmj ovnkube-master-7cqm9-ovnkube-master.log:I0630 04:30:12.523803 1 ovn.go:687] Detected completed pod: openshift-operator-lifecycle-manager_collect-profiles-27609390-6wd55. Will remove. ovnkube-master-7cqm9-ovnkube-master.log:I0630 04:30:12.523968 1 pods.go:200] Releasing IPs for Completed pod: openshift-operator-lifecycle-manager/collect-profiles-27609390-6wd55, ips: 10.129.2.19 ovnkube-master-7cqm9-ovnkube-master.log:I0630 04:45:08.998742 1 ovn.go:687] Detected completed pod: openshift-operator-lifecycle-manager_collect-profiles-27609405-pm2j2. Will remove. ovnkube-master-7cqm9-ovnkube-master.log:I0630 04:45:08.998984 1 pods.go:200] Releasing IPs for Completed pod: openshift-operator-lifecycle-manager/collect-profiles-27609405-pm2j2, ips: 10.129.2.20 ovnkube-master-7cqm9-ovnkube-master.log:I0630 05:00:07.589050 1 ovn.go:687] Detected completed pod: openshift-operator-lifecycle-manager_collect-profiles-27609420-7ktpr. Will remove. ovnkube-master-7cqm9-ovnkube-master.log:I0630 05:00:07.589236 1 pods.go:200] Releasing IPs for Completed pod: openshift-operator-lifecycle-manager/collect-profiles-27609420-7ktpr, ips: 10.128.2.31 ovnkube-master-7cqm9-ovnkube-master.log:I0630 05:15:06.280678 1 ovn.go:687] Detected completed pod: openshift-operator-lifecycle-manager_collect-profiles-27609435-dssbk. Will remove. ovnkube-master-7cqm9-ovnkube-master.log:I0630 05:15:06.280977 1 pods.go:200] Releasing IPs for Completed pod: openshift-operator-lifecycle-manager/collect-profiles-27609435-dssbk, ips: 10.128.2.32 ovnkube-master-7cqm9-ovnkube-master.log:I0630 05:15:06.346822 1 ovn.go:687] Detected completed pod: openshift-operator-lifecycle-manager_collect-profiles-27609390-6wd55. Will remove. ovnkube-master-7cqm9-ovnkube-master.log:I0630 05:15:06.352755 1 ovn.go:726] Ignoring delete event for completed pod openshift-operator-lifecycle-manager/collect-profiles-27609390-6wd55 ovnkube-master-7cqm9-ovnkube-master.log:I0630 05:30:11.285500 1 ovn.go:687] Detected completed pod: openshift-operator-lifecycle-manager_collect-profiles-27609450-nz6kg. Will remove. ovnkube-master-7cqm9-ovnkube-master.log:I0630 05:30:11.285730 1 pods.go:200] Releasing IPs for Completed pod: openshift-operator-lifecycle-manager/collect-profiles-27609450-nz6kg, ips: 10.128.2.34 ovnkube-master-7cqm9-ovnkube-master.log:I0630 05:30:11.351705 1 ovn.go:687] Detected completed pod: openshift-operator-lifecycle-manager_collect-profiles-27609405-pm2j2. Will remove. ovnkube-master-7cqm9-ovnkube-master.log:I0630 05:30:11.355063 1 ovn.go:726] Ignoring delete event for completed pod openshift-operator-lifecycle-manager/collect-profiles-27609405-pm2j2 ovnkube-master-7cqm9-ovnkube-master.log:I0630 05:45:09.269117 1 ovn.go:687] Detected completed pod: openshift-operator-lifecycle-manager_collect-profiles-27609465-p9zlg. Will remove. ovnkube-master-7cqm9-ovnkube-master.log:I0630 05:45:09.269402 1 pods.go:200] Releasing IPs for Completed pod: openshift-operator-lifecycle-manager/collect-profiles-27609465-p9zlg, ips: 10.128.2.35 ovnkube-master-7cqm9-ovnkube-master.log:I0630 05:45:09.326167 1 ovn.go:687] Detected completed pod: openshift-operator-lifecycle-manager_collect-profiles-27609420-7ktpr. Will remove. ovnkube-master-7cqm9-ovnkube-master.log:I0630 05:45:09.329177 1 ovn.go:726] Ignoring delete event for completed pod openshift-operator-lifecycle-manager/collect-profiles-27609420-7ktpr
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days