glusterfs-containers-tests.git -

	Commit message (Collapse)	Author	Age	Files	Lines
*	[LibFix] Add 'collect_logs' param in 'oc_delete' lib	vamahaja	2020-07-02	1	-0/+1
\| \| \| \| \|	Change-Id: I9d99f367b82c6570e1390c6b137e0b9bf401a19c Signed-off-by: vamahaja <vamahaja@redhat.com>
*	[Config] Add variables for system testing	Nitin Goyal	2020-03-18	1	-0/+10
\| \| \| \| \| \| \|	Add variables in config file which will help us to scale our setup. Change-Id: I99739a090c1b2fd92afc2242b5ec6552205ce92f Signed-off-by: Nitin Goyal <nigoyal@redhat.com>
*	Add TC verify gluster pod respin does not affect the metrics	Arun	2020-01-13	1	-0/+1
\| \| \| \| \| \| \| \|	Delete a gluster pod which is hosted on active path Wait for new gluster pod to come up Verify the state of cassandra pod, iscsi and multipath Change-Id: Iba938e7203e6fb86cd953c48040f6f730df8626c
*	Add TC and config data for metrics	Arun Kumar	2019-12-26	1	-0/+23
\| \| \| \| \| \| \| \|	Test case to validate metrics add config data for metrics add config data of registry namespace to validate metrics Change-Id: I4886482ee33847f506ad898d4a313df866d0348c
*	Make 'provisioner' be autocalculated for storage classes	Valerii Ponomarov	2019-10-31	1	-2/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	In OCS 3.11.4 was changed the approach for 'provisioners' in storage classes due to the BugZilla bugs [1] and [2]. So, change the approach for getting 'provisioner' value in this project making it be autocalculated based on the data taken from the block provisioner pod, which is located in the working namespace. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1732787 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1738394 Change-Id: Ic1037038e39abba2b2a1ad6dc3ddbfe42473cb88 Signed-off-by: vamahaja <vamahaja@redhat.com>
*	Add possibility to check Heketi DB inconsistencies after each tc	Valerii Ponomarov	2019-10-25	1	-0/+1
\| \| \| \| \| \| \| \| \|	Define 'check_heketi_db_inconsistencies' config option setting there 'False' or 'True' values. Default value is 'True'. If heketi client doesn't support the 'heketi db check' feature, then 'heketi db check' just won't be performed. Change-Id: I7faff35b15e40d864c0377ae7fee154e217d8eae
*	Add 'additional_gluster_servers' parameter tests in config file	Nitin Goyal	2019-10-17	1	-0/+18
\| \| \| \| \| \| \|	Add new parameter 'additional_gluster_servers' in config file for node add and node remove TC's. Change-Id: I1472b09e0603179f81cbe145fad4343c8c2b6de5
*	Add test cases for the heketi zones feature	Valerii Ponomarov	2019-09-13	1	-0/+1
\| \| \| \| \| \| \| \| \| \|	Add 10 test cases for testing Heketi zones feature. To make all the Heketi zones test cases run in the single suite using the same cluster set 'common.allow_heketi_zones_update' config option to "True" value. By default it is set to "False" and only small set of test cases can run having such value. Change-Id: I69a1f7c96c9f52a06134e715e113ccd9b06764e6
*	Add TC restart app pod when target node is down	Nitin Goyal	2019-08-13	1	-0/+10
\| \| \| \| \| \| \| \| \| \| \|	New TC insures that app pod is restarted properly when one of the target node is down. This patch includes libs of vmware api These libraries can perform VM operations like power on and off via vmware client api's. Change-Id: I11ad4dc3318cb0583de5882d8067ed7e30ea9962
*	Add timeouts for heketi commands	Valerii Ponomarov	2019-03-19	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	It happens, that Heketi commands hang. So, to avoid cancelling of whole test runs, add timeouts for Heketi commands. By default, timeout is 120 sec (2 min). If it is needed to change default value, then define following config option: common: heketi_command_timeout: 180 Change-Id: I79f33daa05bde9a37245e94e66042944c6cd9242
*	rename config file	adityaramteke	2019-03-13	1	-0/+60
	Change-Id: Ib596c79ea3e7c3dd6c83c533e708313f3c4ecc2f