mgr/balancer: fix pg vs object terminology

Signed-off-by: Sage Weil <sage@redhat.com>
(cherry picked from commit 6513e8b0fc2ebcbbbda937ec6d533ea084ef278f)

diff --git a/src/pybind/mgr/balancer/module.py b/src/pybind/mgr/balancer/module.py
index 76b1360fe7e6a0c7fb34842e07a2d2f3080b845e..155f9b73e21e056cf4518c0400b91746e67fef43 100644 (file)
--- a/src/pybind/mgr/balancer/module.py
+++ b/src/pybind/mgr/balancer/module.py
@@ -574,11 +574,11 @@ class Module(MgrModule):
         if unknown > 0.0:
             self.log.info('Some PGs (%f) are unknown; waiting', unknown)
         elif degraded > 0.0:
-            self.log.info('Some PGs (%f) are degraded; waiting', degraded)
+            self.log.info('Some objects (%f) are degraded; waiting', degraded)
         elif inactive > 0.0:
             self.log.info('Some PGs (%f) are inactive; waiting', inactive)
         elif misplaced >= max_misplaced:
-            self.log.info('Too many PGs (%f > %f) are misplaced; waiting',
+            self.log.info('Too many objects (%f > %f) are misplaced; waiting',
                           misplaced, max_misplaced)
         else:
             if plan.mode == 'upmap':