[hostcfgd] Restart container if auto_restart
field in CONFIG_DB
is enabled
or always_enabled
#10620
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.
Signed-off-by: Yong Zhao yozhao@microsoft.com
Why I did it
This PR aims to enable a container to be auto-restarted if
auto_restart
field inFEATURE
table is set toenabled
oralways_enabled
.This issue only occurred in master image. When the command
show feature status
is issued to check theauto_restart
status ofdatabase
, it is enabled. However, the systemd configuration file ofdatabase
shows theRestart=no
. Please see the following result:How I did it
This PR determines whether the keyword
enabled
appears inauto_restart
field or not.How to verify it
This PR is tested on the DuT
str-s6000-on-5
.Which release branch to backport (provide reason below if selected)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)