summaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
...
* Skip test case "test_pvc_deletion_while_pod_is_running" for OCP 3.9vamahaja2019-04-221-0/+4
| | | | | | | "test_pvc_deletion_while_pod_is_running" test case is not supported on OCP 3.9. Added skip statement for OCP 3.9 Change-Id: I5af35145c35371e7eed37d78c2fb9ce23dc9ffa6
* Fix support of OCP3.6 and 3.7Valerii Ponomarov2019-04-115-2/+32
| | | | | | | Project has lots of inconsistencies with OCP3.6 and 3.7 So, fix it. Change-Id: I8d38773637b779e1c2e1631568f100c1ab1fdd50
* Add py3 support to our tox config and fix several incompatibilitiesValerii Ponomarov2019-04-114-9/+19
| | | | | | | | | | | | | | | | | | Required steps to run test cases using py3: 1) Install py3 2) Install 'tox' package using "pip3" 3) Run test cases using tox package installed via pip3 Note that full py3 support is not tested yet. It only allows you to run it on py3 not providing any guarantees. Example: $ python3 -m tox -e functional3 -- \ glusto -c /path/to/the/config/file.yaml \ '--pytest=-v -rsx tests -k test_glusterblock_logs' Change-Id: I610faac0b75364c401734b6f892649893ca2320e
* Add test case PVC resize when heketi is downnigoyal2019-04-111-1/+71
| | | | | | | Verify that when heketi is down PVC expansion should not work. Bring heketi up and running, when heketi is up expansion should work. Change-Id: I4303a82581a91db220ff226f53dea7dc49d22d93
* add test gluster ops checkadityaramteke2019-04-101-0/+34
| | | | Change-Id: I1d9c7e14525ad8de35bfa7be8fffc533c010248b
* Add checks for PVC creation without vol_name prefixArun Kumar2019-03-291-0/+28
| | | | | | | Check if volume name is combination of string 'vol_' and volume id and check volume is present in heketidb and gluster cluster. Change-Id: I755a6447fe653a4ba148798f4c0317aa08a4a4eb
* Unskip TCs with recreation of Gluster PODsValerii Ponomarov2019-03-192-10/+14
| | | | | | | | BZ-1632873 was fixed, hence, unskip test cases which were skipped due to this BZ. Also, make it run only on containerized Gluster clusters. Change-Id: Iee49a303c4f191652d1c94c18e830e6d2fb4e381
* Add timeouts for heketi commandsValerii Ponomarov2019-03-191-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
* Unskip 'test_gluster_block_provisioning_with_valid_ha_count' tcValerii Ponomarov2019-03-181-1/+0
| | | | | | Because BZ-1609703 was fixed. Change-Id: I86e7690e8a190d9f913fb0140780a0bcbcce1e72
* Reorder lib files removing redundant dir layerValerii Ponomarov2019-03-1825-171/+196
| | | | | | | | | | | | Move all the files of 'cns-libs/cnslibs/common' dir to the 'openshift-storage-libs/openshiftstoragelibs', because 'common' is the only dir there, which doesn't really makes sense. And "cns" is old project name, so, replace it with "openshift-storage-libs". Also, fix all the imports of these libs. Change-Id: Ife00a73554e73b21b214b15016b0c8dbbf423446
* rename config fileadityaramteke2019-03-131-0/+0
| | | | Change-Id: Ib596c79ea3e7c3dd6c83c533e708313f3c4ecc2f
* Rename test modulenigoyal2019-03-072-0/+0
| | | | | | | | Rename test module to remove P0 from its name. Which will let us comsume same files for adding other priority test cases as well. Change-Id: I66cbb34ba7ecee1130b7d55952310955a9fe8722
* Reorder test files removing redundant dirsValerii Ponomarov2019-03-0631-0/+0
| | | | | | | | | | Move all the files of 'tests/functional/common/' dir to the 'tests/functional/', because 'common' is the only dir there, which doesn't really makes sense. Do the same about 'tests/functional/common/heketi/heketi_tests' and 'tests/functional/common/heketi/'. Change-Id: I1fa55e2e7bf09e9b9115629b06e1fd160e291a36
* Add TCs creating block-PVCs and app pods changing node scheduling policynigoyal2019-03-061-1/+147
| | | | | | | Add 2 test cases, where one verifies creation of an app pod on the Gluster node and another on the separate node Change-Id: I99dfc5db7fa74d0f69115cfed470f72e66b1a256
* Add tc creating and verifying pvc with volname prefix on an app podroot2019-03-051-0/+14
| | | | Change-Id: I519ce5c26f7bd6480a48512744626ba812524413
* Add CRS support for 'test_glusterblock_logs_presence_verification' tcValerii Ponomarov2019-03-041-20/+17
| | | | Change-Id: I95154066af3e574059199ced18239f7e34c95335
* Add CRS support to 'test_to_check_entry_in_fstab_file' tc and rename itValerii Ponomarov2019-02-281-18/+17
| | | | | | | Changing assertion logic. Now, instead of checking fstab file, we check brick paths presence on Gluster PODs and nodes. Change-Id: I00ed0cb5ef18b67ad0f112276120624c0c0b0763
* Use unique prefixes for test cases in 'test_gluster_services_restart.py'Valerii Ponomarov2019-02-261-5/+2
| | | | | | | | | | | | Right now, we use single prefix for all the test cases of 'test_gluster_services_restart' python test module. It is fragile approach, because if first test fails to delete heketi or gluster volume, then all other test cases fail too, but should not do it. So, use unique prefixes for each of the test cases in this module, to make failure be unique per test. Change-Id: I1cc68ffc0553f79d0b0623335a2aaf985feabade
* Merged HeketiBaseClass to BaseClassvamahaja2019-02-2225-139/+161
| | | | | | | | | | | Renamed cns_baseclass.py to baseclass.py with updated BaseClass. Merged HeketiBaseClass to BaseClass with appropriate changes. Updated delete_volumes and delete_block_volumes methods used in test case method with heketi_delete_volume and heketi_blockvolume- delete. Change-Id: I8f623f1692cd863dc8ff041f7e8525ee0dc84f7b Signed-off-by: vamahaja <vamahaja@redhat.com>
* Add CRS support to the 'restart gluster services' test casesValerii Ponomarov2019-02-082-52/+46
| | | | Change-Id: I40b7ea79d1f7dbc82db825f6ced4447a157361e6
* Add possibility to skip test cases and cleanups after failureValerii Ponomarov2019-02-051-0/+3
| | | | | | | | | | | | | In some cases, it is useful to stop test execution after first failure. Not only stop it, but also skip all the scheduled cleanups. It will allow us to keep a cluster in the best state for a root cause debugging. Just define 'common.stop_on_first_failure' option to True value in the config file. It will make the test runner stop after first failure skipping all the scheduled cleanups and pending test cases. Change-Id: I963eb038a11a8e2088a84f7ba4838870ea3e657a
* Add Heketi version checksnigoyal2019-02-042-0/+13
| | | | | | | | | Add Heketi version checks to the test cases and Heketi libraries. In case of incompatible Heketi version in a setup, test cases will be skipped and direct usage of Heketi libraries will cause them to raise the NotImplementedError exceptions. Change-Id: I462e76f615165140f2a8c7e796c1c582b8f4dc91
* adding library and test case for examine glusternigoyal2019-02-011-0/+45
| | | | | | | | This library is helpfull for diagnosing output of gluster and heketi and it compare both the outputs and the test case verify this feature is working properly. Change-Id: Ice607003f32db2bce2f540a7651024b66b071634
* [RHGSQE-108] Removed polarion test case ID's and updated descriptionvamahaja2019-01-1118-105/+104
| | | | | Change-Id: I9ab3c6bea56a02f76ce818ee095ffe4afc0e64c0 Signed-off-by: vamahaja <vamahaja@redhat.com>
* arbiter volume expand with avg file sizenigoyal2019-01-111-0/+74
| | | | | | | | Trying to create pvc with defined arbiter file size and verifying that when we are expanding volume it is expanding according to avg file size Change-Id: I5c39339f70702bf685c237ae16e21f54384e51db
* Merge "Fix 'verify_arbiter_brick_able_to_contain_expected_amount_of_files' tc"Valerii Ponomarov2019-01-101-22/+19
|\
| * Fix 'verify_arbiter_brick_able_to_contain_expected_amount_of_files' tcValerii Ponomarov2019-01-081-22/+19
| | | | | | | | | | | | | | | | | | This test case talks to the Gluster PODs directly. It is not compatible with Standalone Gluster clusters. So, fix this test by reusing special common function, which allows us to abstract from Gluster cluster deployment type. Change-Id: Ib131984ac0a4623d1d847f9961be26da573d8513
* | Merge "Fix 'test_volume_create_and_list_volume'"Valerii Ponomarov2019-01-101-21/+29
|\ \
| * | Fix 'test_volume_create_and_list_volume'Valerii Ponomarov2019-01-081-21/+29
| |/ | | | | | | | | | | | | | | | | | | | | This test case expects that Gluster cluster has the same amount of volumes as Heketi does. But, it is wrong expectation. We may either create gluster volumes without Heketi or have mismatches after some other Heketi failures. So, fix this test case by comparing starting and resulting amount of volumes in Gluster and Heketi. Change-Id: I322c922fbdf102ccc5fb9f2145eef7b3f1d1a80a
* | Merge "Properly skip TCs when 'additional gluster devices' not configured"Valerii Ponomarov2019-01-102-7/+27
|\ \
| * | Properly skip TCs when 'additional gluster devices' not configuredValerii Ponomarov2019-01-022-7/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For the moment, we have 3 different test cases which use 'additional_devices' config option. All of them will fail in case of specific structure of config. So, make those test cases be smart enough to understand absence of such option data and skip test cases with useful info about it. Change-Id: Id31de7e20188041d2148edf37b3f8c95645c5e52
* | | Removed jenkins scaling codevamahaja2019-01-091-14/+0
| |/ |/| | | | | | | | | | | | | | | | | | | | | Removing this code as it is in additional library file, requires to pass config through config file and requires to upload the scripts. Also it contains hardcoded credentials. Will add new function in openshift_ops.py library similar to "oc_create_app_dc_with_io" with new updated template. Change-Id: I7cfce3fe23b222d40bff1c829afa97f2ffcb621d Signed-off-by: vamahaja <vamahaja@redhat.com>
* | Fix 'test_glusterblock_logs_presence_verification' tcValerii Ponomarov2019-01-021-2/+3
|/ | | | | | | | In this tc we filter pod by dc name with hard-coded project name. It is completely incorrect approach. So, fix it by getting project name from config. Change-Id: I062bc22c9cbf22bbb101a48bad94d0540a3c4bb8
* Merge "[CNS-433][CNS-436] Fix for failed test cases"Valerii Ponomarov2019-01-022-25/+21
|\
| * [CNS-433][CNS-436] Fix for failed test casesvamahaja2019-01-022-25/+21
| | | | | | | | | | Change-Id: I2379043b771cc654eb227d457223b3a24434fd21 Signed-off-by: vamahaja <vamahaja@redhat.com>
* | Merge "Fix CNS-550 test case"Valerii Ponomarov2019-01-021-21/+22
|\ \
| * | Fix CNS-550 test caseValerii Ponomarov2018-12-261-21/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This test case has fragile logic. It doesn't assume we expect new block hosting volumes to be created when we calculate the size for block volume. So, fix it by doing 2 things: - Use total block hosting volume size, not it's 'free space'. - Get info of block hosting vol if block vol gets created unexpectedly, and read it's size. If the size is bigger than block vol's size, then pass the test. Here, we assume that existing, during calculation, block hosting volumes were not the biggest possible and autocreation is enabled in addition to the presence of the available size on the Heketi devices. Change-Id: Ic7d5325b1144dce0e56999617f3c6d7c0829e42d
* | | Merge "Completely rewrite 'heketi_with_device_removal_insuff_space' tc"Valerii Ponomarov2019-01-022-169/+90
|\ \ \
| * | | Completely rewrite 'heketi_with_device_removal_insuff_space' tcValerii Ponomarov2018-12-282-169/+90
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Because it was very fragile and skipped due to bug. So, after bug was fixed we need to enable it back. But, also, considering it's stability, it required complete change of logic. So, it is rewritten completely and moved to more appropriate module where we have other test cases which perform device operations. Change-Id: I1b8c18c8ea883f83861e81e97c534459d7588175
* | | | Merge "Refactor and enable 'test_device_remove_basic_validation' tc"Valerii Ponomarov2019-01-022-105/+43
|\| | |
| * | | Refactor and enable 'test_device_remove_basic_validation' tcValerii Ponomarov2018-12-272-105/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It was skipped some time ago due to the bug. Now this bug is fixed. So, we need to unskip it. So, do it, in addition to the required refactor. Change-Id: I7c426e9cd3dc38ed48e5b91870bc10bd63998694
* | | | Merge "Delete 'test_add_device_heketi_cli' tc as duplicate"Valerii Ponomarov2019-01-021-105/+0
|\| | | | |_|/ |/| |
| * | Delete 'test_add_device_heketi_cli' tc as duplicateValerii Ponomarov2018-12-271-105/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Current 'test_add_device_heketi_cli' [CNS-877] tc completely duplicates another existing tc - 'test_device_remove_operation' [CNS-766]. Being, on it's turn, very fragile and requiring refactor. So, remove this test as it makes no sense neither to keep it skipped nor to refactor it. Change-Id: I40cf7b3d015d1345f0ac2a89569dd64cd67711d3
* | | Merge "Fix CNS-797 and CNS-798 test cases"Valerii Ponomarov2019-01-021-4/+22
|\ \ \ | |/ / |/| |
| * | Fix CNS-797 and CNS-798 test casesValerii Ponomarov2018-12-261-4/+22
| |/ | | | | | | | | | | | | | | | | | | | | | | In some rare cases we get following error trying to create distributed volume: - Insufficient suitable allocatable extents for logical volume tp_foo: 25344 more required. So, fix such situation by catching exception with such message and retrying with smaller volume size. Change-Id: I015a4547347858cd8aff9e566e3dc662a94b6b83
* / Refactor config optionsValerii Ponomarov2018-12-259-93/+76
|/ | | | | | | | | | | | | | | | | | | Doing following: - Rename top-level config option group called 'cns' to the 'openshift'. - Rename 'cns.setup.cns_project_name' option to the 'openshift.storage_project_name'. - Rename 'scale' option to the 'openshift.scale'. - Delete ''devices' and 'zone' options from 'gluster_servers' config group. - Delete 'cns.setup.cnd_username' option as unneeded. - Delete 'cns.setup.cnd_password' option as unneeded. - Delete 'oc_login' common function as unneeded after deletion of 'cns.setup.cnd_username' and 'cns.setup.cnd_password' options. - Remove 'Cns' word from base classes. - Keep backwards compatibility for old options to make transition be smooth. Change-Id: I04ddbbad5f64ffeac79a6744480d33a263d63001
* Add abstraction between deployment types and gluster commandsValerii Ponomarov2018-12-257-152/+50
| | | | | | | | | | | | | | | | | | | | | | | | Now, it is possible to run glustolibs commands on both deployment types: containerized and standalone. It is possible using 'auto_get_gluster_endpoint' as target for lib function in addition to the '@podcmd.GlustoPod()' decorator. Example: """ from glustolibs.gluster.volume_ops import get_volume_list from cnslibs.common import heketi_libs from cnslibs.common import podcmd class TestExample(heketi_libs.HeketiBaseClass): @podcmd.GlustoPod() def test_get_vol_list_either_on_node_or_on_pod(self): volumes = get_volume_list('auto_get_gluster_endpoint') """ Also, delete all the current usages of 'deployment_type' config option, and delete the option as unneeded anymore. Change-Id: I281f287c432a5a9efefda588be436ee285188697
* Merge "Fix 'test_volume_expansion_no_free_space' test case"Valerii Ponomarov2018-12-211-121/+93
|\
| * Fix 'test_volume_expansion_no_free_space' test caseValerii Ponomarov2018-12-191-121/+93
| | | | | | | | | | | | | | This test is broken in several places. So, fix it and also remove redundant steps. Change-Id: I7a9f2c077dda35a8a477fa27882cddf79ec69ac5
* | Merge "changing test function name"Valerii Ponomarov2018-12-211-1/+2
|\ \
generated by cgit (git 2.34.1) at 2024-05-19 10:03:42 +0000