Skip to content

[Bug] - The InvalidPartOrder xml error response should include UploadId, PartNumber, ETag #2038

@niksis02

Description

@niksis02

Describe the bug
The InvalidPartOrder error response is missing the UploadId, PartNumber, ETag properties in the xml response.

To Reproduce

aws s3api create-bucket --bucket test
aws s3api create-multipart-upload --bucket test --key mp
aws s3api complete-multipart-upload --bucket test --key mp --upload-id <uploadId> --multipart-upload file://mp.json --debug

Where mp.json is:

{
  "Parts": [
    {
      "ETag": "e868e0f4719e394144ef36531ee6824c",
      "PartNumber": 200
    },
    {
      "ETag": "e868e0f4719e394144ef36531ee6824c",
      "PartNumber": 134
    }
  ]
}

Expected behavior
The complete request xml response should look like:

<Error><Code>InvalidPart</Code><Message>One or more of the specified parts could not be found.  The part may not have been uploaded, or the specified entity tag may not match the part's entity tag.</Message><UploadId>pZLu3jNNC2tEFczV.PxnU5tQKcbroKjuv6oO_KXPKwUzDRCvC4fCwYWgNwFK0rOMl7qlqT68QG8sK0oeW49PVA--</UploadId><PartNumber>134</PartNumber><ETag>e868e0f4719e394144ef36531ee6824c</ETag><RequestId>3R4SS08N2VR270FV</RequestId><HostId>3BI189RpMofwBuic3tC02o39iSPy7+30SX92gP69L9+Gl4/GKoVcUkcJ0GIRZnNzpu6scSCyNR+87g5d8mTwDruq4b+YiVJC</HostId></Error>

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions