From bbb3369b5028c262ab40449075a2f7df4f2e24dd Mon Sep 17 00:00:00 2001 From: "Yan, Zheng" Date: Wed, 10 May 2017 18:37:08 +0800 Subject: [PATCH] qa/suites/fs: fix write size calculation in full tests 'max_avail' has already taken full_ratio into account Signed-off-by: "Yan, Zheng" --- qa/tasks/cephfs/test_full.py | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/qa/tasks/cephfs/test_full.py b/qa/tasks/cephfs/test_full.py index 3e59956674470..e69ccb373b982 100644 --- a/qa/tasks/cephfs/test_full.py +++ b/qa/tasks/cephfs/test_full.py @@ -405,8 +405,7 @@ class TestClusterFull(FullnessTestCase): # `max_avail` attribute of pools that sometimes occurs in between # tests (reason as yet unclear, but this dodges the issue) TestClusterFull.pool_capacity = self.fs.get_pool_df(self._data_pool_name())['max_avail'] - mon_osd_full_ratio = float(self.fs.get_config("mon_osd_full_ratio")) - TestClusterFull.fill_mb = int(1.05 * mon_osd_full_ratio * (self.pool_capacity / (1024.0 * 1024.0))) + TestClusterFull.fill_mb = int(1.05 * (self.pool_capacity / (1024.0 * 1024.0))) def is_full(self): return self.fs.is_full() -- 2.39.5