s3 returned wrong status code after we tried to delete object through boto3 protocol #58

Closed
opened 2023-03-14 11:54:18 +00:00 by anikeev-yadro · 2 comments
Member

Steps to reproduce:

Delete object from bucket through boto3 returned status code 200, but actually nothing was deleted because object was not found:

COMMAND: 'S3 Delete objects result'
OUTPUT:
 {
    "Errors": [
        {
            "Code": "BadRequest",
            "Key": "2cd4cf47-6e02-41cd-8194-a92d2ed00428",
            "Message": "mark object removal via connection pool: failed to collect relatives: failed to get raw object header: read object header via client: status: code = 2049 message = object not found"
        }
    ],
    "ResponseMetadata": {
        "HTTPHeaders": {
            "content-length": "400",
            "content-type": "text/xml; charset=utf-8",
            "date": "Tue, 14 Mar 2023 10:52:25 GMT",
            "x-amz-request-id": "bed61d19-c71f-4a46-8e54-b4fdc23e507a"
        },
        "HTTPStatusCode": 200,
        "HostId": "",
        "RequestId": "bed61d19-c71f-4a46-8e54-b4fdc23e507a",
        "RetryAttempts": 0
    }
}

Versions:

AWS
2.2.0

node
0.0.1-205-g9929dcf5

s3-gate
0.0.1-78-g0af06c3b

Environment

Server setup and configuration:
Virtual, 4 servers, 4 SN, 4 http qw, 4 s3 gw

Operating System and version (uname -a):
linux vedi 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux

## Steps to reproduce: Delete object from bucket through boto3 returned status code 200, but actually nothing was deleted because object was not found: ``` COMMAND: 'S3 Delete objects result' OUTPUT: { "Errors": [ { "Code": "BadRequest", "Key": "2cd4cf47-6e02-41cd-8194-a92d2ed00428", "Message": "mark object removal via connection pool: failed to collect relatives: failed to get raw object header: read object header via client: status: code = 2049 message = object not found" } ], "ResponseMetadata": { "HTTPHeaders": { "content-length": "400", "content-type": "text/xml; charset=utf-8", "date": "Tue, 14 Mar 2023 10:52:25 GMT", "x-amz-request-id": "bed61d19-c71f-4a46-8e54-b4fdc23e507a" }, "HTTPStatusCode": 200, "HostId": "", "RequestId": "bed61d19-c71f-4a46-8e54-b4fdc23e507a", "RetryAttempts": 0 } } ``` ## Versions: ``` AWS 2.2.0 node 0.0.1-205-g9929dcf5 s3-gate 0.0.1-78-g0af06c3b ``` ## Environment Server setup and configuration: Virtual, 4 servers, 4 SN, 4 http qw, 4 s3 gw Operating System and version (uname -a): linux vedi 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux
realloc added the
P2
label 2023-03-14 11:55:17 +00:00
dkirillov was assigned by alexvanin 2023-03-14 16:30:02 +00:00
Member

Such behavior is in accordance with the specification and its examples https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObjects.html

Such behavior is in accordance with the specification and its examples https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObjects.html
alexvanin added this to the v0.27.0 milestone 2023-03-16 06:56:51 +00:00
dkirillov was unassigned by alexvanin 2023-03-17 15:20:15 +00:00
ironbee was assigned by alexvanin 2023-03-17 15:20:15 +00:00
Owner

Follows specification, not a bug.

Follows specification, not a bug.
alexvanin removed this from the v0.27.0 milestone 2023-04-03 15:15:29 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-s3-gw#58
No description provided.