From 3683cdf496d564c8a179205230834528c7a328a9 Mon Sep 17 00:00:00 2001 From: Sage Weil Date: Tue, 25 Jul 2017 18:29:07 -0400 Subject: [PATCH] qa/suites/rados: at-end: ignore PG_{AVAILABILITY,DEGRADED} With the peering deletes change, setting luminous sets the osdmap flag which triggers a new peering interval. That can lead to health warnings about PG_AVAILABILITY or PG_DEGRADED. Ignore those! Fixes: http://tracker.ceph.com/issues/20693 Signed-off-by: Sage Weil --- qa/suites/rados/thrash/d-require-luminous/at-end.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/qa/suites/rados/thrash/d-require-luminous/at-end.yaml b/qa/suites/rados/thrash/d-require-luminous/at-end.yaml index de21c635e7fed..a18aa3342a010 100644 --- a/qa/suites/rados/thrash/d-require-luminous/at-end.yaml +++ b/qa/suites/rados/thrash/d-require-luminous/at-end.yaml @@ -21,5 +21,11 @@ overrides: conf: global: mon debug no require luminous: true + +# setting luminous triggers peering, which *might* trigger health alerts + log-whitelist: + - overall HEALTH_ + - (PG_AVAILABILITY) + - (PG_DEGRADED) thrashosds: chance_thrash_cluster_full: 0 -- 2.39.5