Stop forcing tunnel type to VXLAN for Kind NetworkPolicy tests #2625
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A patch was merged in upstream OVS and we picked up this patch when we upgraded to OVS 2.15.1. Fixes antrea-io#897 Signed-off-by: Antonin Bas <abas@vmware.com>
abhiraut
approved these changes
Aug 23, 2021
Codecov Report
@@ Coverage Diff @@
## main #2625 +/- ##
==========================================
- Coverage 60.72% 60.57% -0.16%
==========================================
Files 285 285
Lines 23053 23053
==========================================
- Hits 14000 13965 -35
- Misses 7580 7621 +41
+ Partials 1473 1467 -6
Flags with carried forward coverage won't be shown. Click here to find out more.
|
|
/skip-all |
antoninbas
deleted the
stop-forcing-tunnel-type-to-vxlan-for-kind-np-tests
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A patch was merged in upstream OVS and we picked up this patch when we
upgraded to OVS 2.15.1.
Fixes #897
Signed-off-by: Antonin Bas abas@vmware.com