Skip to content
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

bgpd: fix resolvedPrefix in show nexthop json output #17409

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

krishna-samy
Copy link
Contributor

While populating the nexthop info for "show bgp nexthop json", resolvedPrefix is added in parent json object instead of json_nexthop object. This results in displaying wrong resolvedPrefix for nexthops. Fixing the same by adding resolvedPrefix to json_nexthop object, so that the proper resolvedPrefix would be displayed for the respective nexthop

While populating  the nexthop info for "show bgp nexthop json", resolvedPrefix
is added in parent json object instead of json_nexthop object.
This results in displaying wrong resolvedPrefix for nexthops.
Fixing the same by adding resolvedPrefix to json_nexthop object, so that
the proper resolvedPrefix would be displayed for the respective nexthop

Signed-off-by: Krishnasamy R <krishnasamyr@nvidia.com>
@donaldsharp
Copy link
Member

LGTM

@ton31337
Copy link
Member

@Mergifyio backport stable/10.2 stable/10.1

@ton31337 ton31337 added this to the 10.2 milestone Nov 11, 2024
Copy link

mergify bot commented Nov 11, 2024

backport stable/10.2 stable/10.1

✅ Backports have been created

@ton31337 ton31337 merged commit 1abe911 into FRRouting:master Nov 11, 2024
16 checks passed
riw777 added a commit that referenced this pull request Nov 12, 2024
bgpd: fix resolvedPrefix in show nexthop json output (backport #17409)
riw777 added a commit that referenced this pull request Nov 12, 2024
bgpd: fix resolvedPrefix in show nexthop json output (backport #17409)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants