bgpd: fix do not use api.backup_nexthop in ZAPI message #16260
Merged
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
The backup_nexthop entry list has been populated by mistake, and should not. Fix this by reverting the introduced behavior. Fixes: 237ebf8 ("bgpd: rework bgp_zebra_announce() function, separate nexthop handling") Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
|
@Mergifyio backport dev/10.1 stable/10.0 |
✅ Backports have been created
|
This was referenced Jun 21, 2024
ton31337
added a commit
that referenced
this pull request
Jun 21, 2024
bgpd: fix do not use api.backup_nexthop in ZAPI message (backport #16260)
ton31337
added a commit
that referenced
this pull request
Jun 21, 2024
bgpd: fix do not use api.backup_nexthop in ZAPI message (backport #16260)
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.
The backup_nexthop entry list has been populated by mistake, and should not. Fix this by reverting the introduced behavior.
Fixes: 237ebf8 ("bgpd: rework bgp_zebra_announce() function, separate nexthop handling")