While adoption we disable ovncontroller using nodeselector[1] and later enable[2] it after ovn dbs are adopted. We have other Jira[3] where we would not have to use nodeSelector for adoption case, but still it can be used and having such garbage error is bad.

with this ovn-operator logs below error:-

2024-09-19T10:42:16.240Z        ERROR   Reconciler error        {"controller": "ovncontroller", "controllerGroup": "ovn.openstack.org", "controllerKind": "OVNController", "OVNController": {"name":"ovncontroller","namespace":"openstack"}, "namespace": "openstack", "name": "ovncontroller", "reconcileID": "1b644b07-d4e2-44d9-bf7b-e2741cbe1c9c", "error": "not all pods have interfaces with ips as configured in NetworkAttachments: tenant"}

Even there are no pods scheduled the error is logged and is confusing, it would be to get it fixed, can avoid calling VerifyNetworkStatusFromAnnotation when there are not schedulable nodes for daemonset.

[1] https://github.com/openstack-k8s-operators/data-plane-adoption/blob/2fae2e532090863191420e020e9a991585e0b799/tests/config/base/openstack_control_plane.yaml#L105-L106

[2] https://github.com/openstack-k8s-operators/data-plane-adoption/blob/2fae2e532090863191420e020e9a991585e0b799/tests/roles/ovn_adoption/tasks/main.yaml#L225-L229

[3] https://issues.redhat.com/browse/OSPRH-7463