-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicate Node Results for Live Traceflow #4714
Labels
area/ops/traceflow
Issues or PRs related to the Traceflow feature
kind/bug
Categorizes issue or PR as related to a bug.
Comments
antoninbas
added
kind/bug
Categorizes issue or PR as related to a bug.
area/ops/traceflow
Issues or PRs related to the Traceflow feature
labels
Mar 16, 2023
antoninbas
added a commit
to antoninbas/antrea
that referenced
this issue
Mar 16, 2023
After receiving a Packet In for a live Traceflow, the controller uninstalls the corresponding OVS flows to prevent additional Packet Ins (from different connections which also match the Live Traceflow filters). However, if 2 connections happen within a very short time window (< 1ms in my testbed) and both match the Live Traceflow filters, it is still possible for 2 Packet In messages to be received. To avoid duplicate Node Results in the Live Traceflow Status, we need to ignore all Packet In messages received after the first one. Fixes antrea-io#4714 Signed-off-by: Antonin Bas <abas@vmware.com>
antoninbas
added a commit
to antoninbas/antrea
that referenced
this issue
Mar 17, 2023
After receiving a Packet In for a live Traceflow, the controller uninstalls the corresponding OVS flows to prevent additional Packet Ins (from different connections which also match the Live Traceflow filters). However, if 2 connections happen within a very short time window (< 1ms in my testbed) and both match the Live Traceflow filters, it is still possible for 2 Packet In messages to be received. To avoid duplicate Node Results in the Live Traceflow Status, we need to ignore all Packet In messages received after the first one. Fixes antrea-io#4714 Signed-off-by: Antonin Bas <abas@vmware.com>
tnqn
pushed a commit
that referenced
this issue
Mar 17, 2023
After receiving a Packet In for a live Traceflow, the controller uninstalls the corresponding OVS flows to prevent additional Packet Ins (from different connections which also match the Live Traceflow filters). However, if 2 connections happen within a very short time window (< 1ms in my testbed) and both match the Live Traceflow filters, it is still possible for 2 Packet In messages to be received. To avoid duplicate Node Results in the Live Traceflow Status, we need to ignore all Packet In messages received after the first one. Fixes #4714
jainpulkit22
pushed a commit
to urharshitha/antrea
that referenced
this issue
Apr 28, 2023
After receiving a Packet In for a live Traceflow, the controller uninstalls the corresponding OVS flows to prevent additional Packet Ins (from different connections which also match the Live Traceflow filters). However, if 2 connections happen within a very short time window (< 1ms in my testbed) and both match the Live Traceflow filters, it is still possible for 2 Packet In messages to be received. To avoid duplicate Node Results in the Live Traceflow Status, we need to ignore all Packet In messages received after the first one. Fixes antrea-io#4714
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/ops/traceflow
Issues or PRs related to the Traceflow feature
kind/bug
Categorizes issue or PR as related to a bug.
Describe the bug
While running a Live Traceflow, I got the following result:
The Traceflow Status is not correct because the Node Result is duplicated.
To Reproduce
To reproduce, one needs to generate 2 connections in the cluster that will match the Live Traceflow filter. Easier way to do that is to use an ICMP Traceflow and run 2 ping commands. However, the 2 connections must run "at the same time", typically with ~1ms of each other, or the Antrea Agent Traceflow Controller will have time to uninstall the Traceflow OVS flows:
antrea/pkg/agent/controller/traceflow/packetin.go
Lines 133 to 136 in 4a80363
Expected
Status should include a single, non-duplicated, Node Result:
Actual behavior
The Status is incorrect, as shown above.
Versions:
Antrea v1.10 and main branch
The text was updated successfully, but these errors were encountered: