[202012][dualtor] Fix config_db.json path for config-reload#2142
Merged
vaibhavhd merged 1 commit intosonic-net:202012from Apr 29, 2022
Merged
[202012][dualtor] Fix config_db.json path for config-reload#2142vaibhavhd merged 1 commit intosonic-net:202012from
vaibhavhd merged 1 commit intosonic-net:202012from
Conversation
prsunny
approved these changes
Apr 27, 2022
Contributor
|
Are you submitting another PR for master? |
Contributor
Author
|
/Azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
Just added: #2146 |
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.
What I did
Fix the path to
config_db.jsonin config-reload for dual-tor device.Related PR: #1465
Presently, there exists a typo in
config_db.jsonfilename that is sent as an argument tofilter_fdb_entries. This causes failure during config reload:How I did it
Fix the typo.
How to verify it
Config reload does not throw errors any more in the syslog.
Previous command output (if the output of a command-line utility has changed)
New command output (if the output of a command-line utility has changed)