Actions
Bug #5866
closedrgw s3 test failure
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):
Description
the rgw_s3_test suite fails on Centos 6.3 and Centos 6.4
Log files are in ~ubuntu/centos63-dumpling-install/rgw_s3tests on
teuthology.front.sepia.ceph.com
Updated by Anonymous over 10 years ago
Actually, so far this has only failed on 6.3. It is still running on my 6.4
test.
The last few lines of output are:
INFO:teuthology.orchestra.run.err:[10.214.138.108]: s3tests.functional.test_s3.test_bucket_list_marker_after_list ... ERROR INFO:teuthology.orchestra.run.err:[10.214.138.108]: s3tests.functional.test_s3.test_bucket_list_marker_before_list ... ERROR INFO:teuthology.orchestra.run.err:[10.214.138.108]: s3tests.functional.test_s3.test_bucket_list_return_data ... ERROR INFO:teuthology.orchestra.run.err:[10.214.138.108]: s3tests.functional.test_s3.test_bucket_list_object_time ... ERROR INFO:teuthology.orchestra.run.err:[10.214.138.108]: s3tests.functional.test_s3.test_bucket_notexist ... ok INFO:teuthology.orchestra.run.err:[10.214.138.108]: s3tests.functional.test_s3.test_bucket_delete_notexist ... ok INFO:teuthology.orchestra.run.err:[10.214.138.108]: s3tests.functional.test_s3.test_bucket_delete_nonempty ... ERROR INFO:teuthology.orchestra.run.err:[10.214.138.108]: s3tests.functional.test_s3.test_object_write_to_nonexist_bucket ... ok INFO:teuthology.orchestra.run.err:[10.214.138.108]: s3tests.functional.test_s3.test_bucket_create_delete ... ok INFO:teuthology.orchestra.run.err:[10.214.138.108]: s3tests.functional.test_s3.test_object_read_notexist ... ok
Updated by Yehuda Sadeh over 10 years ago
haven't looked at the log, but it might be that the wrong fastcgi module is being used.
Updated by Zack Cerza about 10 years ago
- Status changed from New to Need More Info
- Assignee set to Anonymous
Is this still a problem? If not, please close this ticket.
Updated by Anonymous about 10 years ago
- Status changed from Need More Info to Resolved
This problem appears to be fixed. I did not see this the last time I ran s3 bucket tests
Actions