]> git-server-git.apps.pok.os.sepia.ceph.com Git - s3-tests.git/commit
Fix create_bucket tests as per new bucket naming conventions 305/head
authorSoumya Koduri <skoduri@redhat.com>
Thu, 20 Jun 2019 18:14:13 +0000 (23:44 +0530)
committerCasey Bodley <cbodley@redhat.com>
Tue, 24 Sep 2019 17:48:58 +0000 (13:48 -0400)
commit15d4dd96c586845ea13995e2286543f77d8cf6f4
treec83d495c7fecf37a354f1a214db5b860f104fea1
parentae3ab351c8a97def4f9767d846a5b7692773d191
Fix create_bucket tests as per new bucket naming conventions

As per amazon s3 spec -
https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-s3-bucket-naming-requirements.html

The s3 bucket names should not contain upper case letters or underscore.
Name cannot end with dash or have consecutive periods, or dashes adjacent to periods
Name length shouldn't exceed 63 characters.

These rules are being enforced via
- https://github.com/ceph/ceph/pull/26787

This patch is to update the respective testcases as well.

Note: check_invalid_bucket_name() seems to have been broken. It should
try to create bucket using invalid name. Have addressed it in this
patch. Because of this few testcases (which were incorrectly passing
earlier) are failing in validate_bucket_name. Have marked them
'fails_on_rgw' as done for test_bucket_create_naming_bad_punctuation

Signed-off-by: Soumya Koduri <skoduri@redhat.com>
s3tests_boto3/functional/test_s3.py