summaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Adding test to run gluster commands when glusterd is down on one nodekshithijiyer2019-04-121-0/+102
| | | | | Change-Id: Ibf41c11a4e98baeaad658ee10ba8a807318504be Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Validating whether peers are connected or not before volume creationBala Konda Reddy M2019-04-121-1/+17
| | | | | | | | | | In jenkins this case is failing with peers are not connected while volume creation. Now having a check before creating the volume to make sure that peers are in cluster and in connected state after peer probe. Change-Id: I8aa9d2c4d1669475dd8867d42752a31604ff572f Signed-off-by: Bala Konda Reddy M <bmekala@redhat.com>
* Adding code for cleanup of all bricks on each serverkshithijiyer2019-04-091-2/+18
| | | | | Change-Id: I405843e0093ddb7138ee0a8afbfd4cd2f91e6284 Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Checking if peers are connected after peer probekshithijiyer2019-04-091-0/+24
| | | | | Change-Id: I252ab0c0f6248b9a5c1d7977146c15876e144b38 Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* This TC is to check for File operations in an EC volumeubansal2019-04-081-0/+337
| | | | | Change-Id: Ib1aff1c1bf843dddac5862e55a049d7b47603049 Signed-off-by: ubansal <ubansal@redhat.com>
* Removing test_volume_sanity TCAkarsha2019-04-011-106/+0
| | | | | Change-Id: I82c76f26f4bf359ce153ff35850ce5c349bc759b Signed-off-by: Akarsha <akrai@redhat.com>
* Adding code to check if peers are connected in test_spurious_rebalancekshithijiyer2019-03-291-1/+13
| | | | | Change-Id: I4a1097fbdebd49555fffcfa5fe609f4070e39182 Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Validating peer is in connected or notBala Konda Reddy M2019-03-281-0/+15
| | | | | | | | | In jenkins right after peer probe, add brick function is failing with peer not in cluster. So having check for the peer to be connected or not then proceed to next step. Change-Id: I73bf92819ad44f7a6a14795ab07c45d260cd04eb Signed-off-by: Bala Konda Reddy M <bmekala@redhat.com>
* Test case to change reserve limit with remove brick in progresskshithijiyer2019-03-131-0/+270
| | | | | Change-Id: I53fb7f4cceae395698568129669dc5f3a9a5e4bb Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Fixing busy umount errorsAnees Patel2019-02-251-0/+239
| | | | | Change-Id: I7f7b5cfdee09067d8d96bfcf56ce8a3372ca9368 Signed-off-by: Anees Patel <anepatel@redhat.com>
* Test to check remove brick scenarios wrt to glusterdkshithijiyer2019-02-201-0/+188
| | | | | Change-Id: I1bfa2fb3ae4ff1fc247b40c73f4fade9a3afeede Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Test to reduce volume from 2x3 to 2x2 and to distkshithijiyer2019-02-121-0/+115
| | | | | Change-Id: I64309c3b46dc9087eeb3181acba63b981b2ecc6f Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Test to check volume create with glusterd restart on one nodekshithijiyer2019-02-121-0/+116
| | | | | Change-Id: Ica0771bdee1e96e9d6bb5157fb6c2125a4b419f1 Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Test case to check peer detach warningkshithijiyer2019-02-111-0/+83
| | | | | Change-Id: Idc379ad7f31274cc63f384d7223bf769bb89ace3 Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Fixes for checking uid, gid and permissionVitalii Koriakov2019-02-081-60/+79
| | | | | Change-Id: I683e6ff47120b7db8ee6ae02ed83eba19e6ac4c9 Signed-off-by: Vitalii Koriakov <vkoriako@redhat.com>
* This Tc is used to check remove brick on a dispersed volumeubansal2019-02-071-0/+166
| | | | | Change-Id: Id8cfc0dd31cf4f6f381ec7bb07d4aba06d52b43e Signed-off-by: ubansal <ubansal@redhat.com>
* Test to check if setting volume level options at cluster level is crashing ↵kshithijiyer2019-02-071-0/+72
| | | | | | | glusterd Change-Id: I6ee034f019a4aa36a83e087f2d9fed007e4fd9d7 Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* This testcase checks add-brick on a dispersed volumeubansal2019-02-071-0/+186
| | | | | Change-Id: I640f5c554fab791aa5f196415c5204f7cbca83a4 Signed-off-by: ubansal <ubansal@redhat.com>
* Increasing the wait time for rebalance after remove brick operationJilju Joy2019-02-051-1/+1
| | | | Change-Id: Idc864d0efb02d021d7e30908f1a9ef5553afee65
* Increase wait time for the completion of rebalance. Correction in assert ↵Jilju Joy2019-01-311-4/+4
| | | | | | statement Change-Id: I4333ab2eb63271c5c35756798ea515c7a4d4a3fb
* Delete quorum method from old file. Added fixes for flake8Vitalii Koriakov2019-01-303-801/+140
| | | | | Change-Id: I2acf835a4cf7301c64c4c8a9423f78672cdf9aa4 Signed-off-by: Vitalii Koriakov <vkoriako@redhat.com>
* New quorum behavior fixesVitalii Koriakov2019-01-281-0/+651
| | | | | Change-Id: I364054c35f623893700798bedef965fe05f6aabf Signed-off-by: Vitalii Koriakov <vkoriako@redhat.com>
* Fixed jira issue RHGSQE-33kshithijiyer2019-01-281-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>
* Delete test_client_side_quorum_with_auto_option and ↵Vitalii Koriakov2019-01-251-360/+0
| | | | | | | test_client_side_quorum_with_auto_option_overwrite_fixed Change-Id: I5e22228eaf8574f2ccb1ae38cb98ec01e6493fdf Signed-off-by: Vitalii Koriakov <vkoriako@redhat.com>
* fixing the quorum changes according to new behaviourVijay Avuthu2019-01-251-3/+4
| | | | | | | If quorum is not met, reads/writes fails with transport end point not connected Change-Id: I219c99fc5b96147c059174daf0383454e1bd2831
* New quorum behavior fixesVitalii Koriakov2019-01-251-0/+333
| | | | | Change-Id: I0a2c0ba2e28fc23fe3ff2db57b4ba3c0f08993aa Signed-off-by: Vitalii Koriakov <vkoriako@redhat.com>
* New quorum behavior fixesVitalii Koriakov2019-01-251-0/+218
| | | | | Change-Id: I156e80e958d9e4c7aeec3a97bbcb16e8bfa36f30 Signed-off-by: Vitalii Koriakov <vkoriako@redhat.com>
* This testcase checks that EC version of bricks are not updated when non FOPs ↵ubansal2019-01-251-0/+115
| | | | | | operation are performed like chmod Change-Id: I797253cd4454359bd8f0596c322b2eb71a8a4751
* Correction in verification of volume/sub_directory unmountJilju Joy2019-01-243-6/+6
| | | | Change-Id: I2abad563b965d67520b8bea6da39b30422d7d028
* Fixed jira issue RHGSQE-29 and added quorum reset codekshithijiyer2019-01-242-30/+50
| | | | | Change-Id: Ibd50170d2c3172d7b98c2174630d31a066762f7c Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Fixed jira issue RHGSQE-31kshithijiyer2019-01-231-13/+16
| | | | | Change-Id: I627c78792c6c1ea12c4a023095a4a983f8cee9b0 Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Reset quorum value to defaultkshithijiyer2019-01-231-0/+9
| | | | | Change-Id: I0486abff96ea3ea626ce4d18ac0c24f10ed6a846 Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Reverting quorum value back to 51%kshithijiyer2019-01-231-0/+7
| | | | | Change-Id: I9e61480ff93d0c16b66eeddacdaef715a0b47d1c Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Fix in teardown()kshithijiyer2019-01-221-10/+19
| | | | | Change-Id: Ie44703a9d114b9ecaa5bbce07a98c8a040393f2c Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Fix: Volume create should fail when a node is downBala Konda Reddy M2019-01-221-2/+6
| | | | | | | | | | | | Earlier while volume creation randomly selected one node and stopped gluster but the volume type used in the test is pure distribute and default glusto config takes 4 bricks. With the fix now randomly selecting only first 4 nodes for volume creation and it will fail. Change-Id: I3cf2fc8281c9747b190e1fe9ef471edbb2c4d2ca Signed-off-by: Bala Konda Reddy M <bmekala@redhat.com>
* Reverting back quorum value to 51%kshithijiyer2019-01-221-6/+8
| | | | | Change-Id: I7494b877dff64e195a3517af0176e2a00fa2a86c Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Reverting back quorum value to 51%kshithijiyer2019-01-221-7/+8
| | | | | Change-Id: I7361059b663ea19c08a44c4763881634703d36a4 Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Reverting quorum value back to 51%kshithijiyer2019-01-181-0/+8
| | | | | Change-Id: Ic7f61241addec2ad81c4ef05dd3268c013dbb083 Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
* Reverting the quorum ratio to 51Bala Konda Reddy M2019-01-181-1/+10
| | | | | Change-Id: Iac928311281fac68a5e0c773d87842a35c8d499e Signed-off-by: Bala Konda Reddy M <bmekala@redhat.com>
* Avoid running on 'dispersed' and 'distributed-dispersed' volume types ↵Jilju Joy2019-01-141-2/+1
| | | | | | | | because of bz 1663375 The change will be reverted after the bug 1663375 is resolved Change-Id: Id2b2fb8fdd090c5d9e8495e8f8907dd616bf6e88
* changing testcase names to reflect uniquenessnagpavanchilakam2019-01-042-2/+2
| | | | Change-Id: I35dd3c387c7b6eb3957c5a790af9ff8693403202
* Moved test_glustershd_on_all_volume_types to separate folderVitalii Koriakov2018-12-272-223/+271
| | | | | Change-Id: I3d749c5d131973217d18fc1158236806645e4ab4 Signed-off-by: Vitalii Koriakov <vkoriako@redhat.com>
* Per BZ 1401969, modifying the IO pattern to write single large filesAnees Patel2018-12-201-38/+55
| | | | | | | | | | | | When eager-lock is on, and two writes happen in parallel on a FD, Arbiter becoming source of heal is observed, hence modifing the IO pattern, Also this is a race-condition, hence executing the same remove-brick cycle thrice per BZ 1401969, this patch also takes care of multiple clients writing to different files/dirs, no two clients writing to same file Change-Id: If0003afb675bbcf9f6b555b43e9a11e4def5435c Signed-off-by: Anees Patel <anepatel@redhat.com>
* Fixing the test-case to delete brick directories of replaced bricks, As this ↵Anees Patel2018-12-112-158/+206
| | | | | | | was not handled by teardown class Change-Id: I789adbf0909c5edd0a2eb19ed4ccebcb654700fd Signed-off-by: Anees Patel <anepatel@redhat.com>
* Distribute to replica 2 conversion is done with force option to avoid ↵Anees Patel2018-12-091-1/+1
| | | | | | | split-brain warning per BZ1579758 Change-Id: I674557e153234e0f6af20f12d168b744bda3a3f8 Signed-off-by: Anees Patel <anepatel@redhat.com>
* Moved test_data_self_heal_algorithm_full_default from afr to arbiter folderVitalii Koriakov2018-12-062-148/+243
| | | | | Change-Id: I04ffdedb1ce25ab05239c77b4dd5893ce18b32f7 Signed-off-by: Vitalii Koriakov <vkoriako@redhat.com>
* Moved test_self_heal_differing_in_file_type from afr to arbiter folderVitalii Koriakov2018-12-062-193/+289
| | | | | Change-Id: I9f33c84be39bdca85909c2ae337bd4482532d061 Signed-off-by: Vitalii Koriakov <vkoriako@redhat.com>
* Moved test_existing_glustershd_should_take_care_of_self_healing to separate ↵Vitalii Koriakov2018-12-062-230/+256
| | | | | | | folder Change-Id: I1fb4497ac915c7a93f223ef4e6946eeb4dcd0e90 Signed-off-by: Vitalii Koriakov <vkoriako@redhat.com>
* Quorum ratio not reset to defaultroot2018-12-061-1/+8
| | | | | | | | Earlier quorum ratio is not reset to default which affects the remaining cases.` Change-Id: I5b2e6c23c5b9cd4cfb310534a7ff89a99bf0931b Signed-off-by: root <root@localhost.localdomain>
* Modified the test per BZ Bug 1579758root2018-12-021-1/+1
| | | | | Change-Id: I8d15f482dbde12670975e32af685570a0eaa50b6 Signed-off-by: Anees <anepatel@redhat.com>