190130
From b311385a3c4bd56d69d1fa7e9bd3d9a2ae5c344e Mon Sep 17 00:00:00 2001
190130
From: Pranith Kumar K <pkarampu@redhat.com>
190130
Date: Mon, 7 Oct 2019 12:27:01 +0530
190130
Subject: [PATCH 403/449] Fix spurious failure in bug-1744548-heal-timeout.t
190130
190130
Script was assuming that the heal would have triggered
190130
by the time test was executed, which may not be the case.
190130
It can lead to following failures when the race happens:
190130
190130
...
190130
18:29:45 not ok  14 [     85/      1] <  26> '[ 331 == 333 ]' -> ''
190130
...
190130
18:29:45 not ok  16 [  10097/      1] <  33> '[ 668 == 666 ]' -> ''
190130
190130
Heal on 3rd brick didn't start completely first time the command was executed.
190130
So the extra count got added to the next profile info.
190130
190130
Fixed it by depending on cumulative stats and waiting until the count is
190130
satisfied using EXPECT_WITHIN
190130
190130
> Upstream patch link:https://review.gluster.org/23523
190130
>fixes: bz#1759002
190130
>Change-Id: I3b410671c902d6b1458a757fa245613cb29d967d
190130
>Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
190130
190130
BUG: 1764091
190130
Change-Id: Ic4d16b6c8a1bbc35735567d60fd0383456b9f534
190130
Signed-off-by: Ravishankar N <ravishankar@redhat.com>
190130
Reviewed-on: https://code.engineering.redhat.com/gerrit/202369
190130
Tested-by: RHGS Build Bot <nigelb@redhat.com>
190130
Reviewed-by: Sunil Kumar Heggodu Gopala Acharya <sheggodu@redhat.com>
190130
---
190130
 tests/bugs/replicate/bug-1744548-heal-timeout.t | 17 +++++++++++------
190130
 1 file changed, 11 insertions(+), 6 deletions(-)
190130
190130
diff --git a/tests/bugs/replicate/bug-1744548-heal-timeout.t b/tests/bugs/replicate/bug-1744548-heal-timeout.t
190130
index 3cb73bc..0aaa3ea 100644
190130
--- a/tests/bugs/replicate/bug-1744548-heal-timeout.t
190130
+++ b/tests/bugs/replicate/bug-1744548-heal-timeout.t
190130
@@ -4,6 +4,11 @@
190130
 . $(dirname $0)/../../volume.rc
190130
 . $(dirname $0)/../../afr.rc
190130
 
190130
+function get_cumulative_opendir_count {
190130
+#sed 'n:d' prints odd-numbered lines
190130
+    $CLI volume profile $V0 info |grep OPENDIR|sed 'n;d' | awk '{print $8}'|tr -d '\n'
190130
+}
190130
+
190130
 cleanup;
190130
 
190130
 TEST glusterd;
190130
@@ -20,23 +25,23 @@ TEST ! $CLI volume heal $V0
190130
 TEST $CLI volume profile $V0 start
190130
 TEST $CLI volume profile $V0 info clear
190130
 TEST $CLI volume heal $V0 enable
190130
-TEST $CLI volume heal $V0
190130
 # Each brick does 3 opendirs, corresponding to dirty, xattrop and entry-changes
190130
-COUNT=`$CLI volume profile $V0 info incremental |grep OPENDIR|awk '{print $8}'|tr -d '\n'`
190130
-TEST [ "$COUNT" == "333" ]
190130
+EXPECT_WITHIN $HEAL_TIMEOUT "^333$" get_cumulative_opendir_count
190130
 
190130
 # Check that a change in heal-timeout is honoured immediately.
190130
 TEST $CLI volume set $V0 cluster.heal-timeout 5
190130
 sleep 10
190130
-COUNT=`$CLI volume profile $V0 info incremental |grep OPENDIR|awk '{print $8}'|tr -d '\n'`
190130
 # Two crawls must have happened.
190130
-TEST [ "$COUNT" == "666" ]
190130
+EXPECT_WITHIN $HEAL_TIMEOUT "^999$" get_cumulative_opendir_count
190130
 
190130
 # shd must not heal if it is disabled and heal-timeout is changed.
190130
 TEST $CLI volume heal $V0 disable
190130
+#Wait for configuration update and any opendir fops to complete
190130
+sleep 10
190130
 TEST $CLI volume profile $V0 info clear
190130
 TEST $CLI volume set $V0 cluster.heal-timeout 6
190130
-sleep 6
190130
+#Better to wait for more than 6 seconds to account for configuration updates
190130
+sleep 10
190130
 COUNT=`$CLI volume profile $V0 info incremental |grep OPENDIR|awk '{print $8}'|tr -d '\n'`
190130
 TEST [ -z $COUNT ]
190130
 cleanup;
190130
-- 
190130
1.8.3.1
190130