s3api invalid version causes error

Bug #1882311 reported by clayg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
New
Undecided
Unassigned

Bug Description

While reviewing the fix for lp bug #1874295 (https://review.opendev.org/#/c/722552/) I realized the 400s from swift versioning just aren't be bubbled out through s3api very well

vagrant@saio:~$ aws s3api get-bucket-versioning --bucket s3test2
vagrant@saio:~$ aws s3api get-object --bucket s3test2 --key test --version-id 1591385392.69725 test.out

An error occurred (NoSuchVersion) when calling the GetObject operation: The specified version does not exist.
vagrant@saio:~$ aws s3api get-object --bucket s3test2 --key test --version-id foo test.out

An error occurred (NoSuchVersion) when calling the GetObject operation: The specified version does not exist.
vagrant@saio:~$ aws s3api put-bucket-versioning --bucket s3test2 --versioning-configuration Status=Enabled
vagrant@saio:~$ aws s3api get-object --bucket s3test2 --key test --version-id foo test.out

An error occurred (InternalError) when calling the GetObject operation (reached max retries: 4): We encountered an internal error. Please try again.

^ and we're returning internal errors

This isn't how s3 handles this invalid version id:

$ aws s3api get-object --bucket test.clayg.info --key README.md --profile clayg killme.out --version-id "foo"

An error occurred (InvalidArgument) when calling the GetObject operation: Invalid version id specified

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.