Bug #6472
closeds3tests failing on rpms
0%
Description
some of the s3tests are failing on rhel6.3, the logs are copied to ubuntu@mira055.front.sepia.ceph.com:/home/ubuntu/rgw_rhel6.3\
2013-10-03T12:32:56.383 INFO:teuthology.orchestra.run.err:[10.214.135.36]: s3tests.functional.test_s3.test_100_continue ... ERROR 2013-10-03T12:32:58.702 INFO:teuthology.orchestra.run.err:[10.214.135.36]: s3tests.functional.test_s3.test_bucket_acls_changes_persistent ... ok 2013-10-03T12:33:02.023 INFO:teuthology.orchestra.run.err:[10.214.135.36]: s3tests.functional.test_s3.test_stress_bucket_acls_changes ... ok 2013-10-03T12:33:02.159 INFO:teuthology.orchestra.run.err:[10.214.135.36]: s3tests.functional.test_s3.test_set_cors ... ok 2013-10-03T12:41:40.406 INFO:teuthology.orchestra.run.err:[10.214.135.36]: s3tests.functional.test_s3.test_atomic_read_1mb ... ERROR 2013-10-03T12:50:04.134 INFO:teuthology.orchestra.run.err:[10.214.135.36]: s3tests.functional.test_s3.test_atomic_read_4mb ... ERROR 2013-10-03T12:58:00.092 INFO:teuthology.orchestra.run.err:[10.214.135.36]: s3tests.functional.test_s3.test_atomic_read_8mb ... ERROR 2013-10-03T13:13:51.018 INFO:teuthology.orchestra.run.err:[10.214.135.36]: s3tests.functional.test_s3.test_atomic_write_1mb ... ERROR 2013-10-03T13:30:05.628 INFO:teuthology.orchestra.run.err:[10.214.135.36]: s3tests.functional.test_s3.test_atomic_write_4mb ... ERROR 2013-10-03T13:46:05.656 INFO:teuthology.orchestra.run.err:[10.214.135.36]: s3tests.functional.test_s3.test_atomic_write_8mb ... ERROR 2013-10-03T14:01:29.609 INFO:teuthology.orchestra.run.err:[10.214.135.36]: s3tests.functional.test_s3.test_atomic_dual_write_1mb ... ERROR 2013-10-03T14:17:54.322 INFO:teuthology.orchestra.run.err:[10.214.135.36]: s3tests.functional.test_s3.test_atomic_dual_write_4mb ... ERROR 2013-10-03T14:33:15.655 INFO:teuthology.orchestra.run.err:[10.214.135.36]: s3tests.functional.test_s3.test_atomic_dual_write_8mb ... ERROR 2013-10-03T14:33:17.779 INFO:teuthology.orchestra.run.err:[10.214.135.36]: s3tests.functional.test_s3.test_atomic_write_bucket_gone ... ok
Updated by Yehuda Sadeh over 10 years ago
Looking at the log:
2013-10-03T14:33:52.992 INFO:teuthology.orchestra.run.err:[10.214.135.36]: <Error><Code>RequestTimeTooSkewed</Code></Error>
looks like the clocks are not synchronized.
Updated by Yehuda Sadeh over 10 years ago
This can actually be a side effect of some other issue. From what I can see, for some reason this fails:
bucket.set_acl('public-read-write')
What we're getting is actually this:
<?xml version="1.0" encoding="UTF-8"?><AccessControlPolicy xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Owner><ID>foo.client.0</ID></Owner><AccessControlList><Grant><Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="CanonicalUser"><ID>foo.client.0</ID><DisplayName>None</DisplayName></Grantee><Permission>FULL_CONTROL</Permission></Grant></AccessControlList></AccessControlPolicy>
which doesn't make sense, as it's missing the All group here. Looks like some kind of an environment issue.
Updated by Tamilarasi muthamizhan over 10 years ago
- Project changed from rgw to teuthology
- Subject changed from s3tests failing on rhel 6.3 to s3tests failing on rpms
this happens on fedora 18 as well. looks like there are multiple rgw instances running on the cluster and that might be the issue.
also,the clock sync issue between the machines.
INFO:teuthology.orchestra.run.err:[10.214.134.8]: s3tests.functional.test_s3.test_atomic_read_1mb ... ERROR INFO:teuthology.orchestra.run.err:[10.214.134.8]: s3tests.functional.test_s3.test_atomic_read_4mb ... ERROR INFO:teuthology.orchestra.run.err:[10.214.134.8]: s3tests.functional.test_s3.test_atomic_read_8mb ... ERROR INFO:teuthology.orchestra.run.err:[10.214.134.8]: s3tests.functional.test_s3.test_atomic_write_1mb ... ERROR INFO:teuthology.orchestra.run.err:[10.214.134.8]: s3tests.functional.test_s3.test_atomic_write_4mb ... ERROR INFO:teuthology.orchestra.run.err:[10.214.134.8]: s3tests.functional.test_s3.test_atomic_write_8mb ... ERROR ... ...
Updated by Tamilarasi muthamizhan over 10 years ago
- Status changed from New to Resolved
removing the -x option while restarting apache fixed it.