Remove LOGLEVEL DB since is no longer used#2507
Merged
liat-grozovik merged 3 commits intosonic-net:masterfrom Nov 14, 2022
Merged
Remove LOGLEVEL DB since is no longer used#2507liat-grozovik merged 3 commits intosonic-net:masterfrom
liat-grozovik merged 3 commits intosonic-net:masterfrom
Conversation
dprital
approved these changes
Nov 9, 2022
Contributor
|
@EdenGri Will warm reboot cause this take to come back? Will there be issue if this table show up after upgrading from an older version? |
Contributor
Author
|
@yxieca Did you mean warm upgrade? In warm upgrade, the content from the LOGLEVEL_DB moves to the CONFIG_DB. There is nothing in the LOGLEVEL_DB after the warm-reboot. |
qiluo-msft
approved these changes
Nov 13, 2022
dprital
added a commit
to dprital/sonic-buildimage
that referenced
this pull request
Nov 14, 2022
Update sonic-swss submodule pointer to include the following: * da56bd6 Remove LOGLEVEL DB since is no longer used ([sonic-net#2507](sonic-net/sonic-swss#2507)) Signed-off-by: dprital <drorp@nvidia.com>
7 tasks
8 tasks
Janetxxx
pushed a commit
to Janetxxx/sonic-swss
that referenced
this pull request
Nov 10, 2025
This PR is part of the following HLD: Persistent loglevel HLD: sonic-net/SONiC#1041 - What I did Deleted the LOGLEVEL_DB. 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
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.
This PR is part of the following HLD:
Persistent loglevel HLD: sonic-net/SONiC#1041
- What I did
Deleted the LOGLEVEL_DB.
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
Details if related
Persistent loglevel HLD: sonic-net/SONiC#1041