Actions
Bug #17938
closedrgw: wrong error message is returned when putting container with a name that is too long
% Done:
0%
Source:
Tags:
Backport:
luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Recently Tempest got a few negative tests for verifying interactions with misbehaving clients. RadosGW wrongly responds on requests to create container with a name exceeding the length limit:
T 127.0.0.1:33523 -> 127.0.0.1:8000 [AP] PUT /v1/KEY_de994bc144a949a386669ee4fd16ad02/testtesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttesttest HTTP/1.1. Host: 127.0.0.1:8000. Accept-Encoding: identity. connection: close. X-Auth-Token: ff3e547b750b45368ba17489b276a30f. . ## T 127.0.0.1:8000 -> 127.0.0.1:33523 [AP] HTTP/1.1 400 Bad Request. Content-Length: 17. X-Trans-Id: tx000000000000000000007-00582db6ee-1011-default. Accept-Ranges: bytes. Content-Type: text/plain; charset=utf-8. Date: Thu, 17 Nov 2016 13:55:58 GMT. Connection: close. . ## T 127.0.0.1:8000 -> 127.0.0.1:33523 [AP] InvalidBucketName
According to Tempest the error message should be:
Container name length of <x> longer than <limit>
The issue causes failure of following Tempest's testcase:
tempest.api.object_storage.test_container_services_negative.ContainerNegativeTest.test_create_container_name_exceeds_max_length
Actions