Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2027770

Summary: Unexpected Multus error messages
Product: OpenShift Container Platform Reporter: Shivkumar Ople <sople>
Component: NetworkingAssignee: Douglas Smith <dosmith>
Networking sub component: multus QA Contact: Weibin Liang <weliang>
Status: CLOSED WONTFIX Docs Contact:
Severity: medium    
Priority: medium CC: aos-bugs, bbennett, ccoleman, danw, dosmith, zzhao
Version: 4.7   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1705712 Environment:
Last Closed: 2022-04-27 17:45:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1705712    
Bug Blocks:    

Comment 1 Douglas Smith 2021-11-30 21:36:13 UTC 
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.
Comment 2 Shivkumar Ople 2021-12-01 06:45:11 UTC 
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.