glusto-tests.git - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	[testfix] Add steps to stabilise glusterd	Sri Vignesh	2020-02-25	1	-1/+11
\| \| \| \| \| \| \| \| \| \| \|	Moved steps from teardown class to teardown and removed unwanted teardown class and rectified the testcase failing with wait for io to complete by removing the step because after validate io the sub process terminates and results in failure. Change-Id: I2eaf05680b817b681aff8b48683fc9dac88896b0 Signed-off-by: Sri Vignesh <sselvan@redhat.com>
*	[testfix] Add steps to stabilise content in glusterd - part2	Sri Vignesh	2020-02-19	1	-21/+12
\| \| \| \| \| \| \| \| \| \|	and used wait for peer to connect and wait for glusterd to connect functions in testcases added fixes to check file exists increased timeout value for failure cases Change-Id: I9d5692f635ed324ffe7dac9944ec9b8f3b933fd1 Signed-off-by: Sri Vignesh <sselvan@redhat.com>
*	[py2to3] Add py3 support in 'tests/functional/glusterd'. Part 2	Valerii Ponomarov	2019-12-18	1	-3/+2
\| \| \| \| \|	Change-Id: I1395e14d8d0aa0cc6097e51c64262fb481f36f05 Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com>
*	glusto-tests/glusterd: setting auth.allow with more than 4096 characters	Sanju Rakonde	2018-06-19	1	-0/+102
	In this test case we will set auth.allow option with more than 4096 characters and restart the glusterd. glusterd should restart successfully. Steps followed: 1. Create and start a volume 2. Set auth.allow with <4096 characters 3. Restart glusterd, it should succeed 4. Set auth.allow with >4096 characters 5. Restart glusterd, it should succeed 6. Confirm that glusterd is running on the stopped node Change-Id: I7a5a8e49a798238bd88e5da54a8f4857c039ca07 Signed-off-by: Sanju Rakonde <srakonde@redhat.com>