rajeshkumarchandolu opened a new pull request, #11240: URL: https://github.com/apache/ozone/pull/11240
## What changes were proposed in this pull request? This change extends the S3 gateway smoketest coverage for create-bucket behavior aligned with AWS naming rules and related error responses. **What and why** [HDDS-12869](https://issues.apache.org/jira/browse/HDDS-12869) adds robot tests for create-bucket corner cases: invalid bucket names (length, uppercase, trailing dash) and validation that duplicate create returns the expected error when the requester already owns the bucket. The S3 gateway already returns the appropriate error codes; this PR adds smoketest coverage so regressions are caught in compose/CI. **Changes** In `hadoop-ozone/dist/src/main/smoketest/s3/bucketcreate.robot`, the following test cases are added: | Test | Expected | |------|----------| | Name too short (`ab`) | `InvalidBucketName` | | Name too long (64 characters) | `InvalidBucketName` | | All-uppercase bucket name | `InvalidBucketName` | | Mixed-uppercase bucket name | `InvalidBucketName` | | Trailing dash in name | `InvalidBucketName` | | Maximum valid length (63 characters) | Success | Duplicate create with the same name and the same credentials is unchanged; it remains covered by the existing `Create bucket which already exists` test, which expects `BucketAlreadyOwnedByYou`. The 63-character success case uses a unique 63-character name (`b` plus 62 random lowercase characters) so repeated runs on the same compose cluster do not fail with `BucketAlreadyOwnedByYou` on a fixed bucket name. No S3 gateway or OM code changes are included. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-12869 ## How was this patch tested? Manual smoketest on the docker-compose `ozone` environment: 1. Build dist smoketest artifacts: ```bash mvn clean install -DskipTests -f hadoop-ozone/dist/pom.xml -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
