A new test verifies that we are stopped by the pool quota (and get
the right error messages or block). See ceph.git
32962740ce.
Signed-off-by: Sage Weil <sage@redhat.com>
- in general, test simple vs async vs random
- not for msgr-less workloads
- not for thrash-erasure-*.. the regular thrash
should cover it.
Signed-off-by: Sage Weil <sage@redhat.com>
This has been timing out for weeks to months (hard to say since before that
we were consistently hitting an OSD crash on shutdown). The runs I've looked
at are making progress and seem fine ... just slow because of valgrind and
because of thrashing.
Backport: firefly
Signed-off-by: Sage Weil <sage@redhat.com>
This will mask occasional 'wrongly marked me down' errors when valgrind
is running (it makes things generally slow).
Signed-off-by: Sage Weil <sage@inktank.com>
This is ignored by old teuthology, but used by newer code to tell us when
to generate a product of all directory items.
Signed-off-by: Sage Weil <sage@inktank.com>
Put the client on the same node as some of the osds. This shouldn't cause
any problems. It will make timing a bit different, but if anything that
is probably a good thing.
Signed-off-by: Sage Weil <sage@inktank.com>
