| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I4c75528e7fba934a2f9dd28d8ce79d4cf0d472dd
Signed-off-by: Arun Kumar <aanand01762@gmail.com>
|
|
|
|
|
| |
Change-Id: I0c9064c089872c218b5fc437c03b8de99820c12a
Signed-off-by: Arun Kumar <aanand01762@gmail.com>
|
|
|
|
|
| |
Change-Id: I87d5af3151d01319bdd7d36dbf9bf99527648f56
Signed-off-by: Arun Kumar <aanand01762@gmail.com>
|
|
|
|
|
| |
Change-Id: I03ae8d89b9019b67ff685064372a779e6ade1d08
Signed-off-by: Arun Kumar <aanand01762@gmail.com>
|
|
|
|
|
| |
Change-Id: I56807661c6a6b728a4b902ad14c1b8b0b0e268bf
Signed-off-by: Arun Kumar <aanand01762@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
TC's are separated as below for the better optimization:
1. Replicate volume with zone check option in sc
2. Replicate volume with expansion and zone check option in sc
3. Arbiter volume with zone check option in sc
4. Arbiter volume with expansion and zone check option in sc
Change-Id: Iff5846737fff1895f3d3b74b32c1742f249d32b8
Signed-off-by: Arun Kumar <aanand01762@gmail.com>
|
|
|
|
|
| |
Change-Id: I38546a5e91e56294c03981a182d37b19e2e151a2
Signed-off-by: Arun Kumar <aanand01762@gmail.com>
|
|
|
|
|
| |
Change-Id: I124578f9e314446b92b615a6c022ac5a7f990e95
Signed-off-by: Arun Kumar <aanand01762@gmail.com>
|
|
|
|
|
|
|
|
|
| |
TC consists of -
1. Replica volume with minimum 4 nodes
2. Arbiter volume with minimum 4 nodes
Change-Id: I325d8a7ebe8c0ff2f248712d517b43b484d70328
Signed-off-by: Arun Kumar <aanand01762@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix consists of :
- Currenlty this function check if pod is up and if not then
wait for to up which is incorrect approach as it takes time
to restart pod. Fix this by waiting for heketi pod to be
restarted.
- Remove skip for bugs
Change-Id: Ib3016764741d5fb7188a24e0e267bb0984e2e4a5
Signed-off-by: Arun Kumar <aanand01762@gmail.com>
|
|
|
|
|
| |
Change-Id: I9786d8d68854529624a17cc2c2c12656b4eb6631
Signed-off-by: Arun Kumar <aanand01762@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
Test case 'test_check_pvc_placement_based_on_the_heketi_zones'
has code to check for availabe heketi zone and validate brick
placement which can be used in other test cases. Separate this
code onto two different internal functions.
Change-Id: I76233a1a8bed1e6ab11f91a7820c90a26fa71381
Signed-off-by: Arun Kumar <aanand01762@gmail.com>
|
|
|
|
|
| |
Change-Id: I1d497a9b61762e68558026ddc49e5269b0354ce1
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Following combinations are added:
- 1 zone, replica3 volume, no zone checking flag
- 1 zone, arbiter volume, no zone checking flag
- 2 zones, replica3 volume, no zone checking flag
- 2 zones, arbiter volume, no zone checking flag
- 3 zones, replica3 volume, no zone checking flag
- 3 zones, arbiter volume, no zone checking flag
- 3 zones, replica3 volume, strict zone checking flag
- 3 zones, arbiter volume, strict zone checking flag
Change-Id: I130dcc7c6306b1cdfdee6a860fced19f48474006
|
|
|
|
|
|
|
|
|
| |
By default, we create replica-3 file volumes.
And when we have more than 3 Heketi nodes located in unique zones,
we should check that our file volume is located in 3 unique zones,
not bigger. So, fix this bug.
Change-Id: Id82626425473f5e480ad73b0e17b7a0d675ba8ba
|
|
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
|