glusto-tests.git - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	[py2to3] Add py3 support in 'tests/functional/glusterd'. Part 2	Valerii Ponomarov	2019-12-18	1	-3/+3
\| \| \| \| \|	Change-Id: I1395e14d8d0aa0cc6097e51c64262fb481f36f05 Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
*	Fixed jira issue RHGSQE-33	kshithijiyer	2019-01-28	1	-3/+10
\| \| \| \| \| \| \| \|	Altered code to check for daemons only on servers where the bricks for a given volume are present. Change-Id: I79312f3b09fd5e1b0fdf6db40e29481662e56303 Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
*	Fix spelling mistake across the codebase	Nigel Babu	2018-08-07	1	-3/+3
\| \| \| \|	Change-Id: I46fc2feffe6443af6913785d67bf310838532421
*	Fix up coding style issues in tests	Nigel Babu	2018-03-27	1	-69/+47
\| \| \| \|	Change-Id: I14609030983d4485dbce5a4ffed1e0353e3d1bc7
*	Test case for bitd, scrub, snapd checking after volume reset and volume	Rajesh Madaka	2018-01-28	1	-0/+200
	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>