[202012] Fix CONFIG_DB_INITIALIZED flag check logic and set/reset flag for warmboot #16225
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.
Cherry pick of #15685
MSFT ADO: 24274591
Why I did it
Two changes:
1 Fix a day1 issue, where check to wait until
CONFIG_DB_INITIALIZED
is incorrect.There are multiple places where same incorrect logic is used.
Current logic (
until [[ $($SONIC_DB_CLI CONFIG_DB GET "CONFIG_DB_INITIALIZED") ]];
) will always result in pass, irrespective of the result of GET operation.Fix this logic by checking for value of flag to be "1".
This gap in logic was highlighted when another fix was merged: #14933
The issue being fixed here caused warmboot-finalizer to not wait until config-db is initialized.
2 Set and unset CONFIG_DB_INITIALIZED for warm-reboot case
Currently, during warm shutdown
CONFIG_DB_INITIALIZED
's value is stored in redis db backup. This is restored back when the dump is loaded during warm-recovery.So the value of
CONFIG_DB_INITIALIZED
does not depend on config db's state, however it remain what it was before reboot.Fix this by setting
CONFIG_DB_INITIALIZED
to 0 as when the DB is loaded, and set it to 1 after db_migrator is done.Work item tracking
How I did it
How to verify it
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)