Remove LOGLEVEL DB since is no longer used #12657
Merged
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
EdenGri
changed the title
dprital
approved these changes
Nov 9, 2022
|
@StormLiangMS can you please take a look at this PR to see if we can merge? Thanks. |
qiluo-msft
approved these changes
Nov 13, 2022
davidpil2002
pushed a commit
to davidpil2002/sonic-buildimage
that referenced
this pull request
Nov 15, 2022
This PR is part of the following HLD: Persistent loglevel HLD: sonic-net/SONiC#1041 - Why I did it After the Logger tables moved from the LOGLEVEL_DB to the CONFIG_DB and the jinja2_cache was deleted the LOGLEVEL_DB is not in use. - How I did it Removed the LOGLEVEL_DB from the SONiC code - How to verify it All tests were passed
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.
This PR is part of the following HLD:
Persistent loglevel HLD: sonic-net/SONiC#1041
Why I did it
After the Logger tables moved from the LOGLEVEL_DB to the CONFIG_DB and the jinja2_cache was deleted the LOGLEVEL_DB is not in use.
How I did it
Removed the LOGLEVEL_DB from the SONiC code
How to verify it
All tests were passed
Which release branch to backport (provide reason below if selected)
Description for the changelog
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)