diff options
| author | Sanju Rakonde <srakonde@redhat.com> | 2018-10-08 19:33:58 +0530 |
|---|---|---|
| committer | Atin Mukherjee <amukherj@redhat.com> | 2018-10-25 06:58:45 +0000 |
| commit | 0ca6773eaf5aeb507ebc72d2c2f61902eeff414c (patch) | |
| tree | 59c1bd099b4db1d6e30d93d81ac9be9c8aa5b56d /xlators/storage/posix/src/posix-inode-fd-ops.c | |
| parent | 06bad119b8c773a34cd2942d665112fbf7799788 (diff) | |
tests: correction in tests/bugs/glusterd/optimized-basic-testcases-in-cluster.t
Patch https://review.gluster.org/#/c/glusterfs/+/19135/ has
optimised glusterd test cases by clubbing the similar test
cases into a single test case.
https://review.gluster.org/#/c/glusterfs/+/19135/15/tests/bugs/glusterd/bug-1293414-import-brickinfo-uuid.t
test case has been deleted and added as a part of
tests/bugs/glusterd/optimized-basic-testcases-in-cluster.t
In the original test case, we create a volume with two bricks,
each on a separate node(N1 & N2). From another node in cluster(N3),
we try to detach a node which is hosting bricks. It fails.
In the new test, we created volume with single brick on N1.
and from another node in cluster, we tried to detach N1. we
expect peer detach to fail, but peer detach was success as
the node is hosting all the bricks of volume.
Now, changing the new test case to cover the original test case scenario.
Please refer https://bugzilla.redhat.com/show_bug.cgi?id=1642597#c1 to
understand why the new test case is not failing in centos-regression.
fixes: bz#1642597
Change-Id: Ifda12b5677143095f263fbb97a6808573f513234
Signed-off-by: Sanju Rakonde <srakonde@redhat.com>
Diffstat (limited to 'xlators/storage/posix/src/posix-inode-fd-ops.c')
0 files changed, 0 insertions, 0 deletions