You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[db_migrator] make LOG_LEVEL_DB migration more robust (#2651)
It could be that LOG_LEVEL_DB includes some invalid data and/or a KEY_SET that is not cleaned up due to an issue, for example we observed _gearsyncd_KEY_SET set included in the LOG_LEVEL_DB and preserved in warm reboot. However, this key is not of type hash which leads to an exception and migration failure. The migration logic should be more robust allowing users to upgrade even though some daemon has left overs in the LOG_LEVEL_DB or invalid data is written.
- What I did
To fix migration issue that leads to device configuration being lost.
- How I did it
Wrap the logic in try/except/finally.
- How to verify it
202205 -> 202211/master upgrade.
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
0 commit comments