-
Notifications
You must be signed in to change notification settings - Fork 199
Can't view or edit space members after upgrade #11119
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
Comments
I've run the steps with demo users and basic auth - no space members issues. cc @LukasHirt: How does it look like on web side? Perhaps there is a way to at least avoid endless loading |
I got a fix for the frontend issue with infinite loader - owncloud/web#12336 I will try to pull this into the next patch release. |
It seems the error comes from https://github.com/cs3org/reva/blob/v2.27.7/pkg/storage/utils/metadata/cs3.go#L153 . We should reach that point only if listing the storage spaces is correct returning an empty result but the space already exists. I'm not sure how, but a reasonable explanation is that the service account they're using to access the cs3 storage has changed during the update, and the new account can't see the previously created space. |
Maybe someone can double-check the permissions / grants on the space? The space could have "not-so-standard" grants coming from version 5 which might not be correctly interpreted in version 7. Even if the service account didn't change, the actual grants could be interpreted differently (by mistake) causing the user to lose access |
I can run tests against my environment if there are diagnostic commands that would help |
Describe the bug
The web UI does not display the members associated with a share, instead it shows a progress bar indefinitely. This behaviour started after I upgraded from 5.0.9 to 7.0.1, and is also seen in 7.0.0 and 7.1.0
Steps to reproduce
Expected behavior
Expect to see a list of members of the share and their permissions
Actual behavior
The progress bar displays indefinitely
Setup
The installation is a single owncloud/ocis container, started by docker compose
Additional context
This behaviour first appeared after upgrading to 7.0.1
During the upgrade process, I followed the upgrade guide.
ocis init --diff
reportsno changes, your config is up to date
I did NOT create a CSP because my environment does not any external service (per https://doc.owncloud.com/ocis/next/migration/upgrading_5.0.x_7.0.0.html)
Relevant log messages that appear after attempting to display space members, filtered with
sort -u | grep error
are:The text was updated successfully, but these errors were encountered: