-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Cross-storage move doesn't properly update oc_mounts #25805
Comments
Hey, this issue has been closed because the label (This is an automated comment from GitMate.io. |
Hey, this issue has been closed because the label (This is an automated comment from GitMate.io.) |
Hey, this issue has been closed because the label (This is an automated comment from GitMate.io.) |
This issue has been automatically closed. |
Steps
Expected result
The value of "storage_id" must change to match the new storage in which the "root_id" is on.
Actual result
"storage_id" still points at the home storage of "user1".
I didn't find any negative side-effects in regular OC use. However if some apps are using APIs to reverse-resolve storages based on oc_mounts, they will get wrong results.
Versions
v9.1.0
The text was updated successfully, but these errors were encountered: