Increase time intervals for peer rate setting in LAG test#564
Closed
andrii-savka wants to merge 1 commit intosonic-net:masterfrom
Closed
Increase time intervals for peer rate setting in LAG test#564andrii-savka wants to merge 1 commit intosonic-net:masterfrom
andrii-savka wants to merge 1 commit intosonic-net:masterfrom
Conversation
|
this fix is not approved and it seems that all is being working using latest sonic-mgmt from April 12th, so no need for it |
sdszhang
pushed a commit
to sdszhang/sonic-mgmt
that referenced
this pull request
Aug 2, 2025
<!-- 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: Add debug info for `announce_routes` Fixes # 1. Print `upstream_neighbor_groups` and `downstream_neighbor_groups` for debug 2. Save log for `announce_routes.py` by default ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [ ] Bug fix - [x] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [ ] Test case improvement ### Back port request - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [x] 202505 ### 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 <!-- (If it's a new feature, new test case) Did you update documentation/Wiki relevant to your implementation? Link to the wiki page? -->
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
…lly (#25240) #### Why I did it src/sonic-gnmi ``` * d83a21e - (HEAD -> 202511, origin/202511) gNOI: Add support for Healthz Artifact and Acknowledge RPC (sonic-net#548) (3 hours ago) [jayaragini-hcl] * 2f8182f - [ssw][ha] use ProducerStateTable for DASH_HA_ tables. (sonic-net#564) (3 days ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
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
2 participants
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
Fixes # (issue)
Increase time intervals for peer rate setting in LAG test because 5sec is not enough to change a peer rate. The usual pause interval in LAG-2 test is 20sec, but for peer rate change is only 5sec.
Changed peer rate pause to 20sec as others pause intervals.
Type of change
Approach
How did you do it?
Changed peer rate pause to 20sec instead of 5sec.
How did you verify/test it?
Run LAG-2 test.
Any platform specific information?
No
Supported testbed topology if it's a new test case?
Documentation