-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
OpenStack Swift external storage broke after upgrade to 14.0.0 #11264
Comments
Also, when clicking on the folder (in pink) the following message appears: There was an error with message: Empty response from the server. Do you want to review mount point config in personal settings page? If one clicks on the "OK" button, it simply sends me back to the folder list and not to the "mount point config in personal settings page" as expected. I have also confirmed that the Nextcloud server can reach the Swift cluster just fine. |
None of the above bot-suggested tickets appear to be relevant. |
Same issue for me, i've got this message from command line updater :
|
Any news for this ? |
I also encountered this issue today and got the following log message:
Searching the last part of the message I found the following commit which is in v14, but not in v13: ba71918 Thus, the issue seems that we cannot set the required scope in the external storage configuration UI. Strangely, it also does not work when using OpenStack v2 authentication. |
NC 14.0.6 still can not integrate with Openstack Object storage (Mitaka + Ceph Jewel) |
Hi @teleassist this is maybe off topic, but you can run into it later: I noticed you use
|
NC 15, same here!
|
Yes. There is no option to set the scope.
If you change the file like below it should be possible to define a scope. Unfortunately I don't have a working test setup for OpenStack 😞
|
I think this is not gonna work 🤣 (https://developer.openstack.org/api-ref/identity/v3/index.html#password-authentication-with-unscoped-authorization looks like one input is not enough) |
@danielkesselberg What do you need to test against? I can definitely get you a Swift endpoint to test against if that's what you need. |
Thank you! I wrote something on the pull request and hope that either @rullzer or @icewind1991 could pick this up. |
this is an working setup for my current test-env (NC 15):
|
If you want to use Swift as objectstorage. For external storage it's not possible to set a scope (right now). |
Hi! Any update on this? I had to comment these lines to be able to configure an openstack v3 object storage (provided by OVH) as external storage: I think this restriction should be removed for the moment until we can configure scope, or try to find a quick solution. |
Needed to comment lines suggested by @alejandrocq in 17.0.1 for OVH object storage to work again. |
After updating to 17.0.2 you still need to comment lines 126-129 for OVH object storage to work, but on the page posted by @alejandrocq I see that wrong lines are getting highlighted. The file on github has 259 lines, but my local SwiftFactory.php file has only 251 lines. I'm not sure why, but the bottom line is that these lines need to be commented: 126 # if (!isset($this->params['scope'])) { |
OVH will drop the support for the v2 API on March 24, 2020, as explained there. It looks like it will be necessary to use the v3 API and manually modify the SwiftFactory.php to continue using Openstack from OVH as a backend. |
Thanks for the quick & dirty fix for OVH ! |
this needs asap documentation so swift ovh users are aware of this result. |
cc @icewind1991 @rullzer 🏓 |
I can confirm that after commenting the scope line in lib/private/Files/ObjectStore/SwiftFactory.php |
Indeed it works with OVH hosted swift, as stated in #5882 (comment) Can this be fixed on the nextcloud side so that we do not have to temper with the code? |
@remidebette as your the one who verifyed its working can you make a conclusion did you comment out the
? |
I can confirm it is still required to comment out these lines because there's no way to set the scope (at least in the external storage GUI). |
I'm using swift as primary storage and setting scope made it work, no need to edit any nextcloud code. |
Hi, can you please provide your config.php, i'm stuck with V2 and can't get V3 to work. Thanks Edit: I think I got it
I had to clean files in CLI to get it working |
Thanks a lot, I managed to make it work with Keystone v3, the mail documentation is confusing, I plan to fix it today as soon as I have time: |
Yeah, that's it.
Mine was throwing an error when I left it (late at night), but started working apparently a couple minutes later (as I checked the next day). |
The cleanup part might indeed not be needed. It happened that I could gain access to my nextcloud page right after I did it. Beforehand it kept throwing me "Storage temporarily not available". As it was late as well I didn't investigate any further. |
Please, do not forget that External Storage to OVH is also impacted (the ones configured in database in oc_external_mounts table), and not only Primary Storage. |
Add scope/project with TenantName, as discussed in nextcloud#11264 comment nextcloud/server#11264 (comment) This is necessary for OVH Object Storage. Not sure for other providers.
Add scope/project with TenantName, as discussed in #11264 comment nextcloud/server#11264 (comment) This is necessary for OVH Object Storage. Not sure for other providers.
Add scope/project with TenantName, as discussed in #11264 comment nextcloud/server#11264 (comment) This is necessary for OVH Object Storage. Not sure for other providers.
Add scope/project with TenantName, as discussed in #11264 comment nextcloud/server#11264 (comment) This is necessary for OVH Object Storage. Not sure for other providers.
Add scope/project with TenantName, as discussed in #11264 comment nextcloud/server#11264 (comment) This is necessary for OVH Object Storage. Not sure for other providers.
Hello, after upgrade to Nextcloud 19 OVH external storage stopped working as usual. However, when I selected "External storages" in the Settings I noticed that now there is an additional configuration field: "Tenant:". To find the value I connected to my OVH account, went to Public Cloud project and logged into "Horizon" (Openstack management interface). There I went to the Projects tab. I took 16 digit ID that shows as the name of OVH project and copy/pasted it into the Tenant field in Nextcloud. This worked great and now OVH storage works without any modification of configuration files. So basically it seems to be that the issue described in this topic has been fixed. |
Steps to reproduce
Expected behaviour
Should be able to access files
Actual behaviour
Complains that the setup is incorrect. This worked fine in 13.0.0. It appears that the new OpenStack v3 integration has broken previous v2 integration.
Server configuration
Operating system: Ubuntu 16.04.5
Web server: Apache2
Database: MySQL 5.7
PHP version: 7.0
Nextcloud version: (see Nextcloud admin page)
Updated from an older Nextcloud/ownCloud or fresh install: Upgrade from NC
Where did you install Nextcloud from: Zip
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: Swift
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
LDAP configuration (delete this part if not used)
LDAP config
Client configuration
Browser:
Operating system:
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log
The text was updated successfully, but these errors were encountered: