radosgw now uses 512 frontend threads by default, and valgrind won't
start with its default --max-threads=500
Fixes: http://tracker.ceph.com/issues/25214
Signed-off-by: Casey Bodley <cbodley@redhat.com>
(cherry picked from commit
e617990efe4c39f592cff1541ea55fbcf9f2d6f2)
Conflicts:
qa/suites/rgw/tempest/tasks/rgw_tempest.yaml
qa/suites/rgw/verify/tasks/0-install.yaml
- ceph: {cluster: c2}
- rgw:
c1.client.0:
- valgrind: [--tool=memcheck]
+ valgrind: [--tool=memcheck, --max-threads=1024] # http://tracker.ceph.com/issues/25214
c1.client.1:
- valgrind: [--tool=memcheck]
+ valgrind: [--tool=memcheck, --max-threads=1024]
c2.client.0:
- valgrind: [--tool=memcheck]
+ valgrind: [--tool=memcheck, --max-threads=1024]
c2.client.1:
- valgrind: [--tool=memcheck]
+ valgrind: [--tool=memcheck, --max-threads=1024]
- rgw-multisite:
- rgw-multisite-tests:
config:
- ceph:
- rgw:
client.0:
- valgrind: [--tool=memcheck]
+ valgrind: [--tool=memcheck, --max-threads=1024] # http://tracker.ceph.com/issues/25214
- s3tests:
client.0:
force-branch: ceph-luminous
- ceph:
- rgw:
client.0:
- valgrind: [--tool=memcheck]
+ valgrind: [--tool=memcheck, --max-threads=1024] # http://tracker.ceph.com/issues/25214
- swift:
client.0:
rgw_server: client.0