NDB: Route Replace Error #1179
Merged
NDB: Route Replace Error #1179
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
When modifying an existing route with a different Gateway and Interface the current code does not query the existing route correctly from the database. Hence we end up with 2 routes in the database instead of replaceing the existing one. We need to specifically limit the count query to the unique attributes of a route that is replaced which are DST, DST_LEN, Priority and Table. Signed-Off-By: Sven Auhagen <[email protected]>
|
Thanks a lot! Testing |
svinota
added a commit
that referenced
this pull request
Feb 27, 2024
|
Thanks, merged! |
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.
When modifying an existing route with a different
Gateway and Interface the current code does not query the existing route correctly from the database.
Hence we end up with 2 routes in the database instead of replaceing the existing one.
We need to specifically limit the count query to the unique attributes of a route that is replaced which are DST, DST_LEN, Priority and Table.
Signed-Off-By: Sven Auhagen [email protected]