From 82c2320fbb42fcd42297880ad84887c45889e0a1 Mon Sep 17 00:00:00 2001 From: Sage Weil Date: Tue, 19 Nov 2019 20:33:06 -0600 Subject: [PATCH] qa/suites/rados/singleton-nomsgr/all/balancer: whitelist PG_AVAILABILITY Balancer triggers peering, which may make PGs briefly go inactive--when they possibly haven't been active yet. E.g., "PG_AVAILABILITY": { "severity": "HEALTH_WARN", "summary": { "message": "Reduced data availability: 3 pgs inactive, 3 pgs peering", "count": 6 }, "detail": [ { "message": "pg 2.6 is stuck peering since forever, current state peering, last acting [2,0]" }, { "message": "pg 2.1c is stuck peering since forever, current state peering, last acting [2,1]" }, { "message": "pg 2.7a is stuck peering since forever, current state peering, last acting [2,0]" } ] } Signed-off-by: Sage Weil --- qa/suites/rados/singleton-nomsgr/all/balancer.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/qa/suites/rados/singleton-nomsgr/all/balancer.yaml b/qa/suites/rados/singleton-nomsgr/all/balancer.yaml index 75410508215..4cce39c4eb5 100644 --- a/qa/suites/rados/singleton-nomsgr/all/balancer.yaml +++ b/qa/suites/rados/singleton-nomsgr/all/balancer.yaml @@ -4,6 +4,8 @@ tasks: - install: - ceph: fs: xfs + log-whitelist: + - \(PG_AVAILABILITY\) - cram: clients: client.0: -- 2.39.5