This integration test failed due to an "osd down" warning,
but we intentionally mark OSDs down in this test, so the warning should
be ignored.
Fixes: https://tracker.ceph.com/issues/67820
Signed-off-by: Linjing Li <linjingli2012@gmail.com>
The current ignore-list have \(SLOW_OPS\) but missing SLOW_OPS
Fixes: https://tracker.ceph.com/issues/66604
Signed-off-by: Nitzan Mordechai <nmordech@redhat.com>
As some Teuthology tests seem to block objects for long minutes,
we must not issue the "scrub is blocked for too long" warning
(that warning causes the tests to fail).
A new configuration parameter now controls the grace period before
the warning is issued. Some tests were modified to set this
configuration parameter to a large value.
Signed-off-by: Ronen Friedman <rfriedma@redhat.com>
When thrashing, we don't want this markdown behavior. In
fact, the only teuthology test that expects this behavior is
qa/standalone/osd/osd-markdown.
This bit of yaml is shared by all thrashing tests (although the name is
a bit unfortunate).
Fixes: https://tracker.ceph.com/issues/44348
Signed-off-by: Sage Weil <sage@redhat.com>
In addition to logging slow ops in mon and osd specific log files,
re-introduce logging the same information along with slow op type
details to cluster logs as well. The objective is to make debugging
slow ops easier.
Modify the log whitelisting string to "slow request" within qa suites in
order to make the search for the new warning log message within the
cluster log successful. This should not cause any issue as it's a
substring of the earlier string.
Fixes: https://tracker.ceph.com/issues/43975
Signed-off-by: Sridhar Seshasayee <sseshasa@redhat.com>
so we can avoid the warnings like
grep: Unmatched ( or \(
because we pass the whitelisted string to `egrep -v "$1"` directly.
Signed-off-by: Kefu Chai <kchai@redhat.com>
