[vnetorch]: Fix tunnel route removal flow for bitmap VNET #912
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.
Signed-off-by: Volodymyr Samotiy volodymyrs@mellanox.com
What I did
Fixed tunnel route removal flow for bitmap VNET by adding remove logic for newly added
meta tunnel
entry.Why I did it
Some time ago, when
encap
flow was changed for bitmap VNET, onlycreate
flow was added for newmeta tunnel
entry andremove
was missed. As a result if remove tunnel routemeta tunnel
entry still exists in HW, which is incorrect.How I verified it
Ran ansible and VS tests.
Details if related
N/A