[action] [PR:10924] [dualtor] Fix mux config manual leftover#10930
Merged
mssonicbld merged 1 commit intosonic-net:202205from Dec 2, 2023
Merged
[action] [PR:10924] [dualtor] Fix mux config manual leftover#10930mssonicbld merged 1 commit intosonic-net:202205from
mssonicbld merged 1 commit intosonic-net:202205from
Conversation
Approach What is the motivation for this PR? Same purpose as PR: sonic-net#10555. This is to ensure mux auto to save to config_db.json to avoid any unwanted modification. How did you do it? Do a config save in teardown. How did you verify/test it? Any platform specific information? Supported testbed topology if it's a new test case?
7 tasks
Collaborator
Author
|
Original PR: #10924 |
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
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Same purpose as PR: #10555.
This is to ensure mux
autoto save toconfig_db.jsonto avoid any unwanted modification.How did you do it?
Do a
config savein teardown.How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation