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
Cannot delete files with S3 protocol (GreenQloud) #6598
Comments
As suggested: GreenQloud doesn't support versioning or multi factor authentication (yet and possibly won't). If it's simply a matter of not having the service implemented on our end and not a bug I suggest the delete method tries this method first (for the first file to delete) and if that fails to switch to the old method for the remainder of the session. cheers |
Replying to [comment:2 greenqloud]:
This is not per se a feature related to versioning or MFA we support. Refer to S3 API documentation.
This was introduced by AWS in the 07 December 2011 release. |
Replying to [comment:2 greenqloud]:
I don't think I will support multiple paths here. You will have to bite the bullet and try to catch up on AWS here. |
I see...my mistake. We will definately add that method but can the next release however have the fallback until we do catch up, I suspect some other S3 compatible services will fail as well. When is the next release scheduled anyway? Also do you plan to support the standardised SNIA CDMI storage protocol? http://www.snia.org/cdmi cheers |
Replying to [comment:6 greenqloud]:
Will take another month.
Admittedly I haven't looked into this yet. I heard about Scality supporting this but don't know about anyone else. You might want to open an enhancement request so we can track this.
|
It worked fine to delete files in 4.2.1 but is broken in the latest snapshot release (9483). I get a "forbidden" error message. The test I did was to upload a file with no special characters to a bucket with no special characters and then I tried deleting it again. I have a feeling the command is trying to delete the wrong path or something has changed in the delete method for S3 protocol in this release.
The text was updated successfully, but these errors were encountered: