| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | [py2to3] Add py3 support in 'tests/functional/glusterd'. Part 2 | Valerii Ponomarov | 2019-12-18 | 1 | -2/+2 |
| | | | | | | Change-Id: I1395e14d8d0aa0cc6097e51c64262fb481f36f05 Signed-off-by: Valerii Ponomarov <kiparis.kh@gmail.com> | ||||
| * | Fix: Volume create should fail when a node is down | Bala Konda Reddy M | 2019-01-22 | 1 | -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> | ||||
| * | Fix up coding style issues in tests | Nigel Babu | 2018-03-27 | 1 | -7/+17 |
| | | | | | Change-Id: I14609030983d4485dbce5a4ffed1e0353e3d1bc7 | ||||
| * | glusterd test cases: validate volume create operation | Sanju Rakonde | 2018-02-27 | 1 | -0/+200 |
| In this test case, volume create operations such as creating volume with non existing brick path, already used brick, already existing volume name, bring the bricks to online with volume start force, creating a volume with bricks in another cluster, creating a volume when one of the brick node is down are validated. Change-Id: I796c8e9023244c592c88116cf3baff52ddade48f Signed-off-by: Sanju Rakonde <srakonde@redhat.com> | |||||
 |
index : glusto-tests.git | |
| [no description] |
| summaryrefslogtreecommitdiffstats |