fix python logger enhancement runtime error with traceback when warm-reboot takes place #16
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
when warm-reboot takes place
dbarashinvd
force-pushed
the
dbarashi_python_logger_fix
branch
from
b26d9a7 to
6bd373d
Compare
|
your PR should aginst Junchao's private branch in this PR: sonic-net#17829 |
dbarashinvd
pushed a commit
that referenced
this pull request
Mar 14, 2024
…sonic-net#17750) #### Why I did it src/dhcpmon ``` * 2443073 - (HEAD -> 202311, origin/202311) [counter] Clear counter table when dhcpmon init (#14) (#16) (2 days ago) [Yaqiang Zhu] ``` #### How I did it #### How to verify it #### Description for the changelog
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.
Why I did it
fix python logger enhancement runtime error with traceback when warm-reboot takes place
Work item tracking
How I did it
create another logger file for chassis, which watchdogutil will call through Platform with the flag of set logging level on the fly
set to False
How to verify it
run warm-reboot and verify the runtime error with traceback doesn't happen
change logging level of nvidia-platform-api (mlnx-platform-api) to different then default, like info or debug
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)