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 <sage@redhat.com>

diff --git a/qa/suites/rados/singleton-nomsgr/all/balancer.yaml b/qa/suites/rados/singleton-nomsgr/all/balancer.yaml
index 75410508215d31b50c97e3f00829e38a8ff36b1d..4cce39c4eb55d4549d76b60272f25c3271764008 100644 (file)
--- 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: