Details
-
Bug
-
Status: Complete
-
High
-
Resolution: Done
-
None
-
None
-
None
-
None
-
Unset
Description
The attached journalctl logs show that during yesterday's automated upgrade, the correct packages appear to have been downloaded, but the migration script failed to run. If the steward tries to manually run the migration script, he gets the same error. It appears that the package updates did not run properly, even though dpkg -l returns the correct 1.6.78 version information.
Question 1: How can we recover from this?
After the failed migration, the logs show that an attempt to roll back the node packages failed. There are no apt holds of packages on this node.
Question 2: Correct upgrade logic to fix failed roll back.
Attachments
Issue Links
- relates to
-
INDY-1848 Downgrade (roll-back) should work properly in case one of the dependencies is changed
-
- Complete
-