Actions
Bug #64841
openjava_s3tests: testObjectCreateBadExpectMismatch failure
Status:
Triaged
Priority:
High
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
java 100-continue
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
2024-03-10T16:40:31.654 INFO:teuthology.orchestra.run.smithi060.stdout:suite > Object tests > ObjectTest.testObjectCreateBadExpectMismatch STARTED 2024-03-10T16:40:32.455 INFO:teuthology.orchestra.run.smithi060.stdout: 2024-03-10T16:40:32.455 INFO:teuthology.orchestra.run.smithi060.stdout:suite > Object tests > ObjectTest.testObjectCreateBadExpectMismatch FAILED 2024-03-10T16:40:32.455 INFO:teuthology.orchestra.run.smithi060.stdout: com.amazonaws.services.s3.model.AmazonS3Exception at ObjectTest.java:525
scanning the rgw log http://qa-proxy.ceph.com/teuthology/cbodley-2024-03-10_14:50:40-rgw-wip-cbodley2-testing-distro-default-smithi/7589576/remote/smithi060/log/rgw.ceph.client.0.log.gz i see this sequence of requests:
2024-03-10T16:40:31.653+0000 CreateBucket test-c2dd4bb1-7d2b-431d-a7b0-200c96d8349313 2024-03-10T16:40:32.445+0000 status ok 2024-03-10T16:40:33.409+0000 ListObjectVersions 2024-03-10T16:40:34.465+0000 status ok 2024-03-10T16:40:34.469+0000 a4d1c640 1 failed to read header: bad method 2024-03-10T16:40:34.885+0000 ListObjectVersions 2024-03-10T16:40:35.645+0000 status ok 2024-03-10T16:40:35.649+0000 DeleteBucket
that "bad method" error corresponds to the test's PutObject request that's supposed to pass `Expect: 200`. the "bad method" error comes from beast's http parser when it's trying to read the next request from a connection. i assume this means we either read too many bytes from the previous request, or too few
there are several other occurrances of this "bad method" error, but none led to test failures. scanning the rgw log of successful java_s3tests runs, i don't see any "bad method" errors
Actions