-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(v3.6.x): persists file handling should be at PROCESS_POSTUPDATE phase #274
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bodong-Yang
changed the title
fix: persists file handling should be at PROCESS_POSTUPDATE phase
fix(v3.6.x): persists file handling should be at PROCESS_POSTUPDATE phase
Mar 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
By design the persist file handling stage should be in PROCESS_POSTUPDATE phase.
However due to when migrating from old implementation, persist file handling is still implemented as part of create_standby mechanism. In newer otaclient, the create_standby stage is counted as APPLY_UPDATE phase, resulting in mismatch with design and implementation.
In real world condition, this mismatch might cause the following behavior in APPLY_UPDATE phase:
This PR fixes the issue by move persist file handling out of create_standby package, and implements it in PROCESS_POSTUPDATE phase.
Check list
Bug fix
Behaivor after fix
Related links & ticket
RT4-8805