update watchdogutil to call Platform with set logging level on the fly with value False #6
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
with value False to avoid runtime error with traceback in warm-reboot
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
prevent runtime error with traceback in warm-reboot due to new python logger functionality allowing to change
the logging level on the fly
How I did it
call Platform with this set on the fly flag set to False, which will pass to chassis and call the logger with this flag
set to False when watchdogutil is calling it
How to verify it
run warm-reboot and verify runtime error and traceback doesn't happen
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)