[default-route-bgp-flap]: Fix for 9052 - test failure#15962
Merged
arlakshm merged 1 commit intosonic-net:masterfrom Jan 3, 2025
Merged
[default-route-bgp-flap]: Fix for 9052 - test failure#15962arlakshm merged 1 commit intosonic-net:masterfrom
arlakshm merged 1 commit intosonic-net:masterfrom
Conversation
arlakshm
approved these changes
Jan 3, 2025
11 tasks
nnelluri-cisco
pushed a commit
to nnelluri-cisco/sonic-mgmt
that referenced
this pull request
Mar 15, 2025
What is the motivation for this PR? 'test_default_route_with_bgp_flap' fails with "Default route nexthops doesn't match the testbed topology" issue. The count of the next hops is not matching with the upstream neighbor as per the topology. How did you do it? Instead of skipping T3 neighbors of AZNGHub, use the address family and next hops information to find out the list of upstream neighbors. How did you verify/test it? Ran the above-mentioned test case on a T2 chassis and made sure the test passed without any issues.
Merged
8 tasks
Collaborator
|
Cherry-pick PR to msft-202503: Azure/sonic-mgmt.msft#204 |
arlakshm
pushed a commit
that referenced
this pull request
Apr 18, 2025
What is the motivation for this PR? 'test_default_route_with_bgp_flap', for msft specific AZNG route maps on upstream LC fails even with the fix provided by [default-route-bgp-flap]: Fix for 9052 - test failure #15962 How did you do it? In addition to the fix provided by [default-route-bgp-flap]: Fix for 9052 - test failure #15962 , handle the case for all route maps. How did you verify/test it? Ran the test on T2 chassis with upstream LC, having different sets of route maps and made sure the tests are passing as expected.
auspham
pushed a commit
to auspham/sonic-mgmt
that referenced
this pull request
May 30, 2025
…G route-map for upstream LC (sonic-net#212) <!-- Please make sure you've read and understood our contributing guidelines; https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md Please provide following information to help code review process a bit easier: --> ### Description of PR <!-- - Please include a summary of the change and which issue is fixed. - Please also include relevant motivation and context. Where should reviewer start? background context? - List any dependencies that are required for this change. --> Summary: Fixes # (issue) In addition to the fix provided by sonic-net#15962 for the issue sonic-net#9052, this code change is also needed for handling AZNG route map changes on upstream LC. ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [x] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [x] Test case improvement ### Back port request - [ ] 202012 - [ ] 202205 - [ ] 202305 - [ ] 202311 - [x] 202405 - [x] 202411 ### Approach #### What is the motivation for this PR? - '_test_default_route_with_bgp_flap_', for msft specific AZNG route maps on upstream LC fails even with the fix provided by sonic-net#15962 #### How did you do it? - In addition to the fix provided by sonic-net#15962 , handle the case for all route maps. #### How did you verify/test it? - Ran the test on T2 chassis with upstream LC, having different sets of route maps and made sure the tests are passing as expected. #### Any platform specific information? #### Supported testbed topology if it's a new test case? ### Documentation <!-- (If it's a new feature, new test case) Did you update documentation/Wiki relevant to your implementation? Link to the wiki page? --> 
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
What is the motivation for this PR? 'test_default_route_with_bgp_flap', for msft specific AZNG route maps on upstream LC fails even with the fix provided by [default-route-bgp-flap]: Fix for 9052 - test failure sonic-net#15962 How did you do it? In addition to the fix provided by [default-route-bgp-flap]: Fix for 9052 - test failure sonic-net#15962 , handle the case for all route maps. How did you verify/test it? Ran the test on T2 chassis with upstream LC, having different sets of route maps and made sure the tests are passing as expected. Signed-off-by: opcoder0 <110003254+opcoder0@users.noreply.github.com>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
What is the motivation for this PR? 'test_default_route_with_bgp_flap', for msft specific AZNG route maps on upstream LC fails even with the fix provided by [default-route-bgp-flap]: Fix for 9052 - test failure sonic-net#15962 How did you do it? In addition to the fix provided by [default-route-bgp-flap]: Fix for 9052 - test failure sonic-net#15962 , handle the case for all route maps. How did you verify/test it? Ran the test on T2 chassis with upstream LC, having different sets of route maps and made sure the tests are passing as expected. Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
What is the motivation for this PR? 'test_default_route_with_bgp_flap', for msft specific AZNG route maps on upstream LC fails even with the fix provided by [default-route-bgp-flap]: Fix for 9052 - test failure sonic-net#15962 How did you do it? In addition to the fix provided by [default-route-bgp-flap]: Fix for 9052 - test failure sonic-net#15962 , handle the case for all route maps. How did you verify/test it? Ran the test on T2 chassis with upstream LC, having different sets of route maps and made sure the tests are passing as expected. Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
What is the motivation for this PR? 'test_default_route_with_bgp_flap', for msft specific AZNG route maps on upstream LC fails even with the fix provided by [default-route-bgp-flap]: Fix for 9052 - test failure sonic-net#15962 How did you do it? In addition to the fix provided by [default-route-bgp-flap]: Fix for 9052 - test failure sonic-net#15962 , handle the case for all route maps. How did you verify/test it? Ran the test on T2 chassis with upstream LC, having different sets of route maps and made sure the tests are passing as expected. Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
Pterosaur
pushed a commit
to Pterosaur/sonic-mgmt
that referenced
this pull request
Mar 25, 2026
…G route-map for upstream LC (sonic-net#1063) <!-- Please make sure you've read and understood our contributing guidelines; https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md Please provide following information to help code review process a bit easier: --> ### Description of PR <!-- - Please include a summary of the change and which issue is fixed. - Please also include relevant motivation and context. Where should reviewer start? background context? - List any dependencies that are required for this change. --> Summary: Fixes # (issue) In addition to the fix provided by sonic-net#15962 for the issue sonic-net#9052, this code change is also needed for handling AZNG route map changes on upstream LC. ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [x] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [x] Test case improvement ### Back port request - [ ] 202012 - [ ] 202205 - [ ] 202305 - [ ] 202311 - [x] 202405 - [x] 202411 ### Approach #### What is the motivation for this PR? - '_test_default_route_with_bgp_flap_', for msft specific AZNG route maps on upstream LC fails even with the fix provided by sonic-net#15962 #### How did you do it? - In addition to the fix provided by sonic-net#15962 , handle the case for all route maps. #### How did you verify/test it? - Ran the test on T2 chassis with upstream LC, having different sets of route maps and made sure the tests are passing as expected. #### Any platform specific information? #### Supported testbed topology if it's a new test case? ### Documentation <!-- (If it's a new feature, new test case) Did you update documentation/Wiki relevant to your implementation? Link to the wiki page? -->  Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>
This file contains hidden or 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
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.
Description of PR
Summary:
Fixes # (issue)
This PR fixes issue #9052, where 'test_default_route_with_bgp_flap' fails with "Default route nexthops doesn't match the testbed topology" issue.
The count of the next hops is not matching with the upstream neighbor as per the topology (reading data from config facts).
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation