HDDS-4022. Ozone s3 API return 400 Bad Request for head-bucket for non existing bucket. #1251
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Ozone s3 API returns 400 Bad Request for head-bucket for non-existing bucket.
**hrt_qa$ aws s3api --ca-bundle=/usr/local/share/ca-certificates/ca.crt --endpoint https://s3g:9879/ head-bucket --bucket fsdghj
An error occurred (400) when calling the HeadBucket operation: Bad Request**
It should return 404 as per AWS documentation:
https://docs.aws.amazon.com/cli/latest/reference/s3api/head-bucket.html
A client error (404) occurred when calling the HeadBucket operation: Not Found
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4022
How was this patch tested?
Added test.