ceph/qa/suites/rgw/multisite/valgrind.yaml

# see http://tracker.ceph.com/issues/20360 and http://tracker.ceph.com/issues/18126
#os_type: centos
# ubuntu and no valgrind until we migrate test to py3
os_type: ubuntu

overrides:
  install:
    ceph:
#      flavor: notcmalloc
  ceph:
    conf:
      global:
        osd heartbeat grace: 40
      mon:
        mon osd crush smoke test: false
      osd:
        osd fast shutdown: false
#    valgrind:
#      mon: [--tool=memcheck, --leak-check=full, --show-reachable=yes]
#      osd: [--tool=memcheck]
#      mds: [--tool=memcheck]
do all valgrind runs on centos We are fighting two issues with valgrind on ubuntu (xenial, yakkety, and z): http://tracker.ceph.com/issues/18126 http://tracker.ceph.com/issues/20360 Revert this when it is fixed. Signed-off-by: Sage Weil <sage@redhat.com> 2017-06-30 13:33:10 +00:00			`# see http://tracker.ceph.com/issues/20360 and http://tracker.ceph.com/issues/18126`
qa/suites/rgw: disable valgrind for tests that require py2/ubuntu Signed-off-by: Sage Weil <sage@redhat.com> 2019-12-17 16:52:37 +00:00			`#os_type: centos`
			`# ubuntu and no valgrind until we migrate test to py3`
			`os_type: ubuntu`
do all valgrind runs on centos We are fighting two issues with valgrind on ubuntu (xenial, yakkety, and z): http://tracker.ceph.com/issues/18126 http://tracker.ceph.com/issues/20360 Revert this when it is fixed. Signed-off-by: Sage Weil <sage@redhat.com> 2017-06-30 13:33:10 +00:00
qa/rgw: add multisite suite Signed-off-by: Casey Bodley <cbodley@redhat.com> 2017-04-23 23:37:49 +00:00			`overrides:`
			`install:`
			`ceph:`
qa/suites/rgw: disable valgrind for tests that require py2/ubuntu Signed-off-by: Sage Weil <sage@redhat.com> 2019-12-17 16:52:37 +00:00			`# flavor: notcmalloc`
qa/rgw: add multisite suite Signed-off-by: Casey Bodley <cbodley@redhat.com> 2017-04-23 23:37:49 +00:00			`ceph:`
			`conf:`
			`global:`
			`osd heartbeat grace: 40`
qa/suites: disable mon crush smoke test with valgrind Valgrind runs itself on forked children, and does its cleanup when they complete, and this is slow... slow enough that it frequently makes the test time out. Valgrind let's you ignore child processes that you exec, but I can't find a way to skip forked children in the same address space. Work around this by skip this validation when running under valgrind. Fixes: http://tracker.ceph.com/issues/20602 Signed-off-by: Sage Weil <sage@redhat.com> 2017-07-14 15:42:31 +00:00			`mon:`
			`mon osd crush smoke test: false`
osd: add osd_fast_shutdown option (default true) If we get a SIGINT or SIGTERM or are deleted from the OSDMap, do a fast shutdown by exiting immediately. This has a few important benefits: - We immediately stop responding (binding) to any sockets, which means other OSDs will immediately decide we are down (and dead!). This minimizes IO interruption. - We avoid the complex "clean" shutdown process, which is historically a source of bugs. In reality, the only purpose of the "clean" shutdown is to try to tear down everything in memory so we can do memory leak checking with valgrind. Set this option to false for valgrind QA runs so we can still do that. Not that with the new read leases in octopus, we rely on the default behavior that a ECONNREFUSED is taken to mean that the OSD is fully dead, so that we don't have to wait for any leases to time out. This works in sane environments with normal IP networks, but that behavior could conceivably be a bad idea if there are some weird network shenanigans going on. If osd_fast_fail_on_connection_refused were disabled, then this fast shutdown procedure might be worse than the clean shutdown because we would have to wait for the heartbeat timeout. Signed-off-by: Sage Weil <sage@redhat.com> 2019-11-15 15:31:50 +00:00			`osd:`
			`osd fast shutdown: false`
qa/suites/rgw: disable valgrind for tests that require py2/ubuntu Signed-off-by: Sage Weil <sage@redhat.com> 2019-12-17 16:52:37 +00:00			`# valgrind:`
			`# mon: [--tool=memcheck, --leak-check=full, --show-reachable=yes]`
			`# osd: [--tool=memcheck]`
			`# mds: [--tool=memcheck]`