Hey Sakshi,
patch #10954 was not backported to 3.7 (for whatever reason) but introduced a helper routine
brick_up_status() in tests/volume.rc. This routine was used in writing test cases for couple
of patches
http://review.gluster.org/#/c/13120/
http://review.gluster.org/#/c/13044/
Obviously they fail regression when backported to 3.7. For now the routine has been hand copied
(thanks Pranith) in one the patches due to 3.7.7 urgency. There also exist a similar routine
brick_up_status_1() introduced by
http://review.gluster.org/#/c/13116/
which has been backported to 3.7, yet to get merged.
I'm thinking of changing all callers (just a handful) of brick_up_status() to use brick_up_status_1()
over backporting the initial patch (which was merged in master about 4 months ago).
What do you think? Does the original patch need a backport?
Thanks.
Venky
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
