-
Notifications
You must be signed in to change notification settings - Fork 370
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
Fix network policy ingress policy stats #2078
Fix network policy ingress policy stats #2078
Conversation
4ef6d95
to
4b4bfe1
Compare
Codecov Report
@@ Coverage Diff @@
## main #2078 +/- ##
==========================================
- Coverage 61.05% 55.07% -5.99%
==========================================
Files 270 270
Lines 20366 20368 +2
==========================================
- Hits 12435 11218 -1217
- Misses 6636 7960 +1324
+ Partials 1295 1190 -105
Flags with carried forward coverage won't be shown. Click here to find out more.
|
5e9e8f1
to
ebb5a73
Compare
And please remove the issue link from the title of the commit message. |
5b22320
to
c00b230
Compare
commit message updated |
It seems updated |
Could you also wrap the commit message body to ~76 characters per line? |
c00b230
to
5f49a81
Compare
@tnqn Thanks for review. It seems the current changes make all the tests pass. However, I will update the code and reply the comments after looking at different |
055d38b
to
8cc89b8
Compare
commit message formatted |
8cc89b8
to
3eccfd0
Compare
Codecov Report
@@ Coverage Diff @@
## main #2078 +/- ##
==========================================
+ Coverage 61.05% 61.26% +0.20%
==========================================
Files 270 269 -1
Lines 20366 20422 +56
==========================================
+ Hits 12435 12511 +76
+ Misses 6636 6623 -13
+ Partials 1295 1288 -7
Flags with carried forward coverage won't be shown. Click here to find out more.
|
3eccfd0
to
e2e347a
Compare
/test-all |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, @jianjuns @antoninbas you may want to take a look too as it changes the default table of l2ForwardingCalcTable to fix the ingress traffic stats.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/test-integration |
@ceclinux could you check the integration failure: https://jenkins.antrea-ci.rocks/job/antrea-integration-manual-for-pull-request/8/console? It seems related to this change |
sure. |
Packets to the tunnel or gateway port will go directly to ConntrackCommitTable and bypass the IngressMetricsTable, which causing these packets uncounted when applying by certain Networkpolicy with ingress rules. Fixed by forwarding these packets to IngressMetricsTable.
e2e347a
to
2b8f42a
Compare
/test-integration |
1 similar comment
/test-integration |
updated and integration tests passed @tnqn |
/test-all |
Packets to the tunnel or gateway port will go directly to ConntrackCommitTable and bypass the IngressMetricsTable, which causing these packets uncounted when applying by certain Networkpolicy with ingress rules. Fixed by forwarding these packets to IngressMetricsTable.
Packets to the tunnel or gateway port will go directly to ConntrackCommitTable and bypass the IngressMetricsTable, which causing these packets uncounted when applying by certain Networkpolicy with ingress rules. Fixed by forwarding these packets to IngressMetricsTable.
This PR fixes #1976. The miscalculation is caused by
L2ForwardingCalcTable
with ruleTherefore, these packets will not get counted in this case.