[action] [PR:11223] Config bgp bbr by GCU cmd in test_bgp_bbr test #11248
+68
−4
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
What is the motivation for this PR? Config bbr status by GCU cmd. How did you do it? Config bbr status use cmd config apply-patch <json-patch> instead of sonic-cfggen How did you verify/test it? Run bgp/test_bgp_bbr.py case on dut manually and passed.
7 tasks
|
Original PR: #11223 |
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)
Config bbr status by using GCU cmd since we enable YANG model for bbr in sonic-net/sonic-buildimage#17622.
Type of change
Back port request
Approach
What is the motivation for this PR?
Config bbr status by GCU cmd.
How did you do it?
Config bbr status use cmd
config apply-patch <json-patch>instead ofsonic-cfggenHow did you verify/test it?
Run bgp/test_bgp_bbr.py case on dut manually and passed.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation