| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | [testfix] Add steps to stabilise glusterd | Sri Vignesh | 2020-02-25 | 1 | -16/+15 |
| | | | | | | | | | | | | 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> | ||||
| * | [py2to3] Add py3 support in 'tests/functional/glusterd'. Part 1 | Valerii Ponomarov | 2019-12-18 | 1 | -2/+2 |
| | | | | | | Change-Id: Ib414b8496ca65a48bbe42936e32a863c9c1072e4 Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com> | ||||
| * | [TC] Resubmitting testcase test_glusterd_quorum_validation after bug fix | kshithijiyer | 2019-11-21 | 1 | -0/+301 |
| As the below mentioned bug is fixed resubmitting testcase: https://bugzilla.redhat.com/show_bug.cgi?id=1690753 Test case: -> Creating two volumes and starting them, stop the second volume -> Set the server quorum and set the ratio to 90 -> Stop the glusterd in one of the node, so the quorum won't meet -> Peer probing a new node should fail -> Volume stop will fail -> Volume delete will fail -> Volume reset will fail -> Start the glusterd on the node where it is stopped -> Volume stop, start, delete will succeed once quorum is met Change-Id: Ic9dea44364d4cb84b6170eb1f1cfeff1398b7a9b Signed-off-by: kshithijiyer <kshithij.ki@gmail.com> | |||||
 |
index : glusto-tests.git | |
| [no description] |
| summaryrefslogtreecommitdiffstats |