Bug 1550048
| Summary: | Tracing the network traffic at OVS level not working in ovs-networkpolicy as network plugin. | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Sanket N <snalawad> |
| Component: | Networking | Assignee: | Ben Bennett <bbennett> |
| Networking sub component: | openshift-sdn | QA Contact: | zhaozhanqi <zzhao> |
| Status: | CLOSED NOTABUG | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | aos-bugs, bbennett, eparis, yannick.kint |
| Version: | 3.7.0 | ||
| 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: | Environment: | ||
| Last Closed: | 2018-03-02 17:21:27 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Sanket N
2018-02-28 12:04:05 UTC
You can get a little bit farther by including "ct_state=trk" in the argument to ofproto/trace, but it still may not make it all the way through the table, depending on exactly what source/destination you're tracing. The problem is that the NetworkPolicy plugin makes use of OVS connection tracking, which causes the processing of some packets to be stopped and then restarted. For actual network traffic, this is all completely transparent, but ofproto/trace didn't know how to deal with this in older OVS releases. I think OVS 2.8 is the first release that will automatically restart tracing at the right point after a ct() action. |