Normal Description of problem:
A problemtaic pod is currently running in customer environment that is still using podIP instead of egress for outside communication.
Version-Release number of selected component (if applicable):
How reproducible:
Curretnly, they have 1 problematic pod running( previously there were a few of them)
Steps to Reproduce:
1. On call we checked the snatting rules existing in OVN_Db
2. When captured TCPDump on primary interface, we see that one pod still using PodIP
3. For the other pods they restarted & the issue got fixed
Actual results:
The problematic pod still using PodIP
Expected results:
This shouldn't happen
Additional info:
Customer is more interested to know why this is happening as the already have the fix(restarting tdhe po). But, they are retaining the pod for us to check.
