Actions
Bug #7064
closedS3 request to non-existent object in non-existent bucket results in 30 second timeout/500 error from Apache
% Done:
0%
Source:
Support
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
A request to:curl -v http://192.168.2.16:8080/doesnotexist/missingkey
Results in a 30 second timeout from Apache and a '500 Internal Server Error' being returned to the client.
Logs with 'debug rgw = 20, debug ms = 1'
attached (sanitized to remove customer identifying details).
- RGW attempts to map a bucket name to a pool, then query the proper pool for that bucket
- In this case, the bucket-to-pool mapping returns an empty string for the pool name since the bucket does not exist
- When a query is passed down to the rados level for an object in a pool with an empty string for a name (which does not exist), the call hangs
- By creating a pool with no name, the call will succeed and return ENOENT which will result in the 404 that we desire.
Files
Actions