| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I1d497a9b61762e68558026ddc49e5269b0354ce1
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
| |
Change-Id: I29093a09c3f0cc09eaa9c6d94bad882c0bafd91c
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix consists of -
Remove dc name which is passed twice to function
'get_pod_name_from_dc'
In test case 'test_heketi_metrics_heketipod_failure' function
'get_pod_name_from_dc' is called by passing dc name twice,
because of which 'timeout' is passed as dc name instead of
integer value hence raising an exception 'TypeError'.
Change-Id: I6827a8f9bbd847f346ea6b519db97181219f9717
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
| |
Change-Id: I757388d8f9c14549a7ec408868e3b86c92362a22
|
|
|
|
|
| |
Change-Id: I332a66659b5abefb5d5052232ec9b61124860575
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
List of changes -
1. Remove test file 'test_device_info.py' as it contains only one
test case which can be part of test file
'test_heketi_device_operations.py'
2. Change test case name 'test_device_enable_disable' to
'test_heketi_device_enable_disable'
3. Change test case name 'test_device_remove_operation' to
'test_heketi_device_remove'
4. Change test case name 'test_heketi_with_device_removal_insuff_space' to
'test_heketi_device_removal_with_insuff_space'
5. Chnage test case name 'test_heketi_device_delete_operation' to
'test_heketi_device_delete'
6. Move test case 'test_heketi_devices_info_verification' to
'test_heketi_device_operations.py' and rename as
'test_heketi_device_info'
Change-Id: I8ddc9beb7bc697214242212e50c9727ce644f2c1
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
| |
Change-Id: Ibb96e961b1501ef696858a5eec80422471e877fd
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
| |
Create volume and see the pending operations of volume and bricks
in heketidb and verify that after creation count is changed.
Change-Id: I2d73f82bde422fdffc1fbbdc14564a0c8ffa99aa
|
|
|
|
|
|
|
|
|
|
| |
'test_heketi_node_operations' tc tried to use incorrect
'additional_gluster_servers.additional_devices' config option. Change
it to 'additional_gluster_servers.devices', as it is expected by the
configuration.
Change-Id: I2351814bf35a78724f84d954abd7ce780e945328
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
| |
- In test case 'test_heketi_volume_create_with_cluster_node_down'
function glusto-tests 'get_volume_list' function returns 'None'
in case of failure.
- Add assert statement to check whether 'get_volume_list' function
returns expected gluster volume list.
Change-Id: I2b11bb33b1346d88db0501d000f32515db86279d
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
| |
Code creates file volume and tries to delete blockvolume
instead of file
Change-Id: I4c73f388dc10a153f254c479bc8bf127df644916
|
|
|
|
|
|
|
| |
Change code of func _create_distributed_replica_vol to
handle block hosting volume creation as well.
Change-Id: If4b1f48dc8cbe257254a2729599f58f302b403d8
|
|
|
|
|
|
|
|
|
| |
which completely duplicates "test_to_create_and_delete_dist_rep_vol"
in 'test_create_distributed_replica_heketi_volume.py' test module &
fix cleanup code for create_heketi_volume_with_name_and_wait in
openshift-storage-libs/openshiftstoragelibs/baseclass.py module.
Change-Id: I9b3dea28e6330e52caab09311e20b65dd48491b9
|
|
|
|
|
|
|
|
|
|
| |
In the 'test_heketi_node_operations::TestHeketiNodeOperations' class,
if we define 'additional_gluster_servers' option, but do not provide
there any value, then we fail. But, "skip" is expected in such situation.
So, catch "IndexError" exception and make tests be skipped after it.
Change-Id: Idfb1cdfc6941d284a4dc8e670c2eb5510eafe744
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
| |
Add new TCs where TCs verify that volume operations works while node
removal is running.
Change-Id: Id5092761253eb8f221c5fb39cfb95765f3087eea
|
|
|
|
|
|
|
| |
Add new TC remove or delete node from heketi, and verify gluster
peer status, bricks on the new node and heal info.
Change-Id: If4b6006a4a58fd581ac9851b377a82f69ce0f30f
|
|
|
|
|
|
|
|
| |
Add TC where it creates two volumes with the same name via heketi and
verifies that first one gets successfully created and
the second one gets failed.
Change-Id: I36e9bb1ed93b807458fcbdf8d417ada1cbc7b943
|
|
|
|
|
|
|
| |
Add new TC heketi volume creation of size greater than the device size
and verify backup-volfile-servers, replicacount, brickscount etc.
Change-Id: I87cbf0e1d8326ad077f02cf465105aca3f8bdde7
|
|
|
|
|
|
|
|
| |
Move 'topology_volumes_with_bricks' func to the "heketi_ops" module
to be able to use it in other test cases.
Change-Id: I7cca884a4f3fb34ec15bb947d3c39d9226e294d0
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
|
|
|
|
|
|
|
| |
Confirm no inconsistencies occur in targetcli when block
devices are created with one block hosting volume down.
Change-Id: I2a755ef2a88c6e6ca5326be3787ac07c0fb7db26
|
|
|
|
|
| |
Change-Id: I482ac6ebed181546a18595c6a6b21d2115782b3a
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
|
|
|
| |
Fix consists of -
- Remove steps for add device validation.
- Add steps for gluser peer status validation.
- Add steps for endpoints validation.
Change-Id: I773a883b1ea8bb2bc93660db3459fd864fcd1317
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
| |
Change-Id: I4a2ac7b819929c2de6c8ea5520257800d2e134cc
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
|
|
|
|
|
|
|
|
| |
Validate creation of volume with snapshot enabled
and create and delete snapshot created.
Change-Id: I7173ed6fb6659963e29cc0f1b1ede0ce7c6fe2a4
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
|
|
|
|
|
|
|
|
| |
Validate total nodes count in heketi db check is same as
heketi node list.
Change-Id: I6004537c251f8e512afabe88e0fb284624421b8d
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
|
|
|
|
|
|
|
| |
Validate block volumes using heketi db check in heketi blockvolume list are same.
Change-Id: Ibbaf038c05ef347d195140c2ba2c18f2d58c3b5e
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
|
|
|
|
|
|
|
|
|
| |
Define 'check_heketi_db_inconsistencies' config option setting
there 'False' or 'True' values. Default value is 'True'.
If heketi client doesn't support the 'heketi db check' feature, then
'heketi db check' just won't be performed.
Change-Id: I7faff35b15e40d864c0377ae7fee154e217d8eae
|
|
|
|
|
| |
Change-Id: I22410ad8c81ca71ac9c2cbaddd66f086abcdf3c5
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
|
| |
Add library to check db results
Validate count of volumes of heketi and db are same
Change-Id: I6e75f2d8d5f19a94c1dced5a07f9c948b4de9ef4
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
|
|
|
|
|
|
|
|
| |
Validate whether creation of maximum supported
blockvolumes doesn't have any impact to the
functionality of gluster-block.
Change-Id: I2a1503f527da2d1d916e87ce154e88bf9b5e1fa8
|
|
|
|
|
|
|
| |
Add a device, check there are no bricks on the device and verify
the device deletion.
Change-Id: I0e6adafb730e8d82926ce4e1d7b6b3c4799efc1b
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix consists of -
- Use "**kwargs" approach in the "heketi_node_list"
function as it is done in lots of other functions.
- Parse the CLI output in the "heketi_node_list" function
using regex instead of the splitting and stripping strings.
- Combine test cases related to the same feature into one
module - test_heketi_node_operations.py
- Remove redundant checks which already exist in common
libraries.
- Remove unnecessary logging.
Change-Id: I815ddfbbacb765140229e7630ec87a6bbaa6255b
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
| |
Stop glusterd on 2 of the nodes/pods in the cluster containing alteast
5 gluster nodes and verify creation of volume using heketi.
Change-Id: I94570f5bbfa20c19f11f4e14e29d2b1a40612fc5
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
In test case when we use large disk size, heketi takes time to create
volume and due to timeout it gives error.
Add fix in such test cases to check if volume created after getting
an exception, get details of such volumes or raise exception in case
it fails to create volume.
Change-Id: I1c23a8c6558c23edf8947771e4f41a4bd3ffd66a
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
| |
Change-Id: I5886680a0d5666c68c677893e0fb327be0e80760
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
|
| |
Add test case where we set and test Heketi config options
to limit lower/upper allowed volume size
and amount of bricks per volume.
Change-Id: Ifb5cf64bba34dbf4e89f2fe9364263385a04cfa7
|
|
|
|
|
|
|
|
| |
Verify creation of replica 2 volume and validate the bricks
created in gluster backend are same.
Change-Id: I9fcc090e909d9bf578cf8eca6e12e4f785140e3f
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
|
|
|
|
|
|
|
| |
Validate creation of block volume with name
Change-Id: I08ee31201d42a95f8a829eb54ce68421903fdbbf
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
|
|
|
|
|
|
|
| |
Add new TC where we verify given heketi mount point in volume info
is working.
Change-Id: Ia03af9ea6729cdfadf663abe46db7184a8b6fe2c
|
|
|
|
|
|
|
|
| |
validate creation and deletion of
distributed-replicated bhv.
Change-Id: Ia42ace7e5be53fa7a00f88378575205e7fd5ba97
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
|
|
|
|
|
|
|
|
| |
validate block volume creation with
different auth values
Change-Id: I820f65a5aaa5adc6cb58b16b18b6c93b22177d45
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
|
|
|
|
| |
Change-Id: I26c750c68055c6cc50de8015942d0d9725819aaf
|
|
|
|
|
|
|
|
| |
This test case validates bhv options like
features.shard,shard.size,shd max threads,
and performance related ones
Change-Id: I991f13e1b744486281e98813f169630a666eeb59
|
|
|
|
|
|
|
|
| |
Create 3 volumes using heketi-cli command, verify their presence in
heketi topology info, delete 2 volumes and validate their deletions
and presence of 3rd volume in heketi topology info
Change-Id: I78298d2aec21ff8031ff01efd53f11ba31e269c9
|
|
|
|
|
| |
Change-Id: I7ead23c46a472fee70d684c45f32f5e4efb0674f
Signed-off-by: kasturiNarra <knarra@redhat.com>
|
|
|
|
|
|
|
|
| |
It happens that heketi client located out of the Heketi POD may fail
not reaching the server side. So, add back-up approach where we run
Heketi commands on a Heketi POD when main commands fail.
Change-Id: Ie6ae5be82082f34426f9288b02575e3abd4940f5
|
|
|
|
|
|
|
| |
Rename TC modules to appropriate name and move them to correct
component.
Change-Id: I87c9bb7822c17c955dd9c2d780ef08e4d4e0d7ee
|