[stable10] Fix migration issue caused during upgrade to version 10 #29049
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
|
@sharidas please do a quick retest when coming from 10.0.3 to this branch (just one case is enough) |
|
@sharidas please always add a link in the original PR to the backport |
|
Test result of migration from 10.0.3beta ( tarball ) to the current change:
|
This change will help users to fix the migration issue caused during upgrade to version 10. If user had opted user specific key in the older versions then no drop down will appear in the version 10. Same applies if user had opted for the masterkey in older version, no drop down will appear in version 10. Signed-off-by: Sujith H <sharidasan@owncloud.com>
sharidas
force-pushed
the
fix-migration-issue-stable10
branch
from
ecf9ba9
to
10933cb
Compare
87 tasks
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This change will help users to fix the migration
issue caused during upgrade to version 10. If
user had opted user specific key in the older versions
then no drop down will appear in the version 10.
Same applies if user had opted for the masterkey
in older version, no drop down will appear in version
10.
Signed-off-by: Sujith H sharidasan@owncloud.com
Description
When user tries to upgrade from versions < 10, the userSpecificKey is not present in the appConfig. And as a result during migration to version 10.0.2, the user gets an option to select the encryption mode :
This issue is addressed with this change.
Related Issue
#28985
Motivation and Context
The change made here solves, the issues caused during migration.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: