tests: Fix spurious failures in ta-write-on-bad-brick.t

2019-05-24T15:00:28+00:00

Problem:
afr_child_up_status_meta works only when LOOKUP on $M0 is successful.
There are cases where quorum is not met and LOOKUP fails on $M0 which
leads to failures similar to:
grep: /mnt/glusterfs/0/.meta/graphs/active/patchy-replicate-0/private: Transport endpoint is not connected
This was happening once in a while based on attribute-timeout and
md-cache not serving the lookup.

Fix:
Find child-up status based on statedump instead. Also changed mount
options to include --entry-timeout=0 and --attribute-timeout=0

updates bz#1193929
Change-Id: Ic0de72c3006d7399a5feb3e4d10d4748949b2ab3
Signed-off-by: Pranith Kumar K

cluster/afr: Add test for thin-arbiter feature

2018-11-26T07:46:10+00:00

Test : Check success/failure of write fop while
different bricks/ta process are down.

Change-Id: I3c376935df93ebf1f794c964bd19bc1280d91c59
updates: bz#1624332
Signed-off-by: Ashish Pandey

glusterfs.git/tests/basic/afr/ta-write-on-bad-brick.t, branch v7.2

tests: Fix spurious failures in ta-write-on-bad-brick.t

cluster/afr: Add test for thin-arbiter feature