fix runtime error with traceback in warm-reboot #215
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 runtime error with traceback in warm reboot caused by watchdog
calling platform which calls chassis with the new logging mechanism
to set logging level on the fly
Work item tracking
How I did it
change the way chassis creates this logger
by default it will create the logger with new capabilities
watchdog will call it with new flag set to False. this way will make chassis create logger without new capabilities
How to verify it
run warm reboot and verify no runtime error with traceback occurs
run other logging to make sure no regression in new feature
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)