Misleading logs in whereabout re-conciler pod during a pod deletion

Issue

• Below errors are seen when deleting pod's which are created using multus/net-attach-def.

  2024-02-16T10:27:45Z [debug] Used defaults from parsed flat file config @ /host/etc/cni/net.d/whereabouts.d/whereabouts.conf
  2024-02-16T10:27:45Z [verbose] result of garbage collecting pods: failed to get the IPPool data: ippool.whereabouts.cni.cncf.io "17x.xx.xx.xx-27" not found
  2024-02-16T10:27:45Z [error] dropping pod [mrf/evc-mrfp-1] deletion out of the queue - could not reconcile IP: failed to get the IPPool data: ippool.whereabouts.cni.cncf.io "17x.xx.xx.xx-27" not found
  2024-02-16T10:27:45Z [verbose] Event(v1.ObjectReference{Kind:"Pod", Namespace:"mrf", Name:"evc-mrfp-1", UID:"5556a063-77ba-4167-9562-02c6fcf36xxx", APIVersion:"v1", ResourceVersion:"131556466", FieldPath:""}): type: 'Warning' reason: 'IPAddressGarbageCollectionFailed' failed to garbage collect addresses for pod mrf/evc-mrfp-1
  

• During a pod deletion, the whereabouts reconciler correctly detects the pod deletion but it errors out claiming that the IPPool is not found although IPPool is present.

• Even though the pods are getting recreated or deleted without any issue but still above logs are seen in re-conciler daemon.