[Bugs] [Bug 1360573] Fix spurious failures in split-brain-favorite-child-policy.t

bugzilla at redhat.com bugzilla at redhat.com
Thu Jul 28 14:03:11 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1360573



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/15022 committed in release-3.8 by Pranith
Kumar Karampuri (pkarampu at redhat.com) 
------
commit 264c7496c875914fcaf8bded44d61e284633c719
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Fri Jul 22 07:48:27 2016 +0530

    tests: Fix spurious failures with split-brain-favorite-child-policy.t

    Problem:
    It is not guranteed that the self-heal daemon would apply the new option
    as soon as volume set is executed because all the command gurantees is that
    the process is notified of the change in volfile. Shd still needs to fetch
    volfile and reconfigure. If the next volume heal command comes even before
    the reconfigure happens, then the heal won't happen.

    Fix:
    Restart shd to make sure it has the option loaded with new value.

     >BUG: 1358976
     >Change-Id: I3ed30ebbec17bd06caa632e79e9412564f431b19
     >Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
     >Reviewed-on: http://review.gluster.org/14978
     >Smoke: Gluster Build System <jenkins at build.gluster.org>
     >Reviewed-by: Krutika Dhananjay <kdhananj at redhat.com>
     >Tested-by: Jeff Darcy <jdarcy at redhat.com>
     >NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
     >CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
     >Reviewed-by: Jeff Darcy <jdarcy at redhat.com>

    BUG: 1360573
    Change-Id: I09e097dbdc2cae659ad1617d336945eb804b09a5
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/15022
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list