-
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
problem retrieving object with swift backend #7667
Comments
Would be good to know which version of ownCloud you are using. Thanks! |
Steps to reproduceMount owncloud on external storage (openstack swift v1 with keystone v2.0 auth) mount config :{"user":{"all":{"/$user/files/OpenStackObjectStorage":{"class":"\OC\Files\Storage\Swift","options":{"user":"ayoub","bucket":"owncloud_Container","region":"RegionOne","tenant":"ayoub","password":"*****","service_name":"swift","url":"192.168.103.6:5000/v2.0/","timeout":"5000"}}}}} Actual behaviorproblem uploading files (WebGui and client application), doesObjectExist($path) method in Swift.php is throwing exception Server configurationOperating system: windows7/ubuntu12.04 The content of owncloud.log{"app":"files_external","message":"Problem retrieving object [http://192.168.103.6:8080/swift/v1/owncloud_Container/New%20folder/release_notes.pdf]","level":3,"time":"2014-03-11T13:26:21+00:00"} |
@ayoubboulila this warning can be ignored. This PR will remove the useless warning: #7897 Are you having trouble download files ? That should work regardless of the warning. |
I made the changes and the warning was gone and the download/upload threw the web interface is working.thank you. |
So I guess we can close this now |
Successefully mounted Swift on owncloud and owncloud is showing the existed files on the backend but :
doesObjectExist($path) method in Swift.php is throwing exception making problems when traying to upload files to swift .
owncloud.log :
{"app":"files_external","message":"Problem retrieving object [http://192.168.103.6:8080/swift/v1/owncloud_Container/New%20folder]","level":3,"time":"2014-03-11T12:50:50+00:00"}
So what's going wrong ?
The text was updated successfully, but these errors were encountered: