summaryrefslogtreecommitdiffstats
path: root/glustolibs-gluster/glustolibs/gluster
diff options
context:
space:
mode:
authorRajesh Madaka <rmadaka@redhat.com>2018-01-23 11:39:16 +0530
committerShwethaHPanduranga <shwetha-h-p@review.gluster.org>2018-01-28 09:53:24 +0000
commit7d4bf9511ba4b5b685717fc05177d50e14b0a6b1 (patch)
tree46097dc0adc41354f0b83a525ead892823610496 /glustolibs-gluster/glustolibs/gluster
parentfe5ac28d9f422eb14c168dd0bda68c25e2167aa0 (diff)
Test case for bitd, scrub, snapd checking after volume reset and volume
reset force Description: Create Distribute volume, then enable bitrot and uss on that volume, then check the bitd, scrub, snapd daemons running or not. Then peform the volume reset, after volume reset only snap daemon will get kill but bitd scrub daemons will be remain running. Then perform volume reset with force, after volume reset with force all three(bitd, scrub, snapd) daemons will get kill, these daemons will not be running. below are the steps performed for developing this test case: -> Create Distributed volume -> Enable BitD, Scrub and Uss on volume -> Verify the BitD, Scrub and Uss daemons are running on every node -> Reset the volume -> Verify the Daemons (BitD, Scrub & Uss ) are running or not -> Eanble Uss on same volume -> Reset the volume with force -> Verify all the daemons(BitD, Scrub & Uss) are running or not Change-Id: I15d71d1434ec84d80293fda2ab6a8d02a3af5fd6 Signed-off-by: Rajesh Madaka <rmadaka@redhat.com>
Diffstat (limited to 'glustolibs-gluster/glustolibs/gluster')
0 files changed, 0 insertions, 0 deletions