Generally speaking, there's no problem if the pod isn't found, this message is... essentially informative. I don't believe you should see a "stuck pod" -- that is, a pod that's failing to delete completely. If a pod is removed by force and no grace period e.g. ``` oc delete pod foo --force --grace-period=0 ``` This could be somewhat expected, as the API could delete the pod object before Multus is able to delete it. The referenced upstream fix has appeared in the product since 4.1.0 and should prevent pods from getting stuck.
Yes this message is just an informative one, and afaik there is no force deletion of pods that happened in this cluster but still, we see such messages despite the fix having landed 4.1.x. Seems like it is just spamming the logs, so if possible let us know if this can be addressed in the latest versions too.