signpost: cancel-upgrade
behavior fix
#950
Merged
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.
Issue number: Fixes #949
Description of changes:
Testing done:
Initial status:
Mark inactive partition as valid, see tries_left set to 1
Make the inactive as next to boot, see priority bumped to 2
cancel-upgrade
then properly rolls backupgrade-to-inactive
by setting the priority back to 0 while keepingtries_left
at 1Subsequent
upgrade-to-inactive
call is successful because the inactive partition is still marked valid (tries_left
> 0)cancel-upgrade
then restores active partition as next to boot.Another
clear-inactive
call then wipes the inactive partition priority bits.Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.