Fix ctrmgrd unexpectedly restart service issue #11037
Open
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
* If the state_db has any docker stop setting which will set the current_owner to none, the ctrmgrd will then restart the service when it receive config_db change
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
During our test time, we run config reload and reboot for multiple times. We found occasionally the ctrmgrd.py will restart some features(services) and that will disturb the system status.
How I did it
Prevent the ctrmgrd.py to restart the services when the owner is setting a new value from "none". Which is a default value setting by container script when docker stop.
How to verify it
Run the same test for few days and make sure the following type syslog will not occur.
Which release branch to backport (provide reason below if selected)
Description for the changelog
If the state_db has any docker stop setting which will set the current_owner to none, the ctrmgrd will then restart the service when it receive config_db change.
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)