Project

General

Profile

Actions

Bug #7346

closed

An unfound object as part of multi-object delete should return deleted instead of error

Added by Brian Andrus about 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Support
Tags:
Backport:
dumpling
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Upon trying to issue a multiple delete operation on a bucket that contains an unfound object, we return:


<DeleteResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Error>
<Key>92.jpg</Key>
<Code>404</Code>
<Message>NoSuchKey</Message>
</Error>
</DeleteResult>

We should be returning a "Deleted" result instead of an "Error" as described in the S3 API documentation:

"Note that, if the object specified in the request is not found, Amazon S3 returns the result as deleted."

A Sample of the expected response would be:


<DeleteResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Deleted>
<Key>sample1.txt</Key>
</Deleted>
</DeleteResult>

Actions #1

Updated by Ian Colle about 10 years ago

  • Assignee set to Yehuda Sadeh
Actions #2

Updated by Yehuda Sadeh about 10 years ago

  • Status changed from New to In Progress
Actions #3

Updated by Yehuda Sadeh about 10 years ago

  • Status changed from In Progress to Fix Under Review
Actions #4

Updated by Yehuda Sadeh about 10 years ago

  • Status changed from Fix Under Review to Pending Backport

A fix was pushed, commit:8ca3d95bf633ea9616852cec74f02285a03071d5.

Actions #5

Updated by Yehuda Sadeh about 10 years ago

  • Status changed from Pending Backport to Resolved
  • Backport set to dumpling
Actions

Also available in: Atom PDF