| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
The test verifies block volume expand feature works and reflecting new
size in client side.
Change-Id: I0c5b5c7c4437888e077ff00b7cf37b3f857d04a0
Signed-off-by: Nitin Goyal <nigoyal@redhat.com>
|
|
|
|
|
| |
Change-Id: Idd21f2d0cfb2a1171e4e8464646684ac9164ad0e
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
| |
Change-Id: I5db480da820c82b7b15f90ed70a4f60643079cb0
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
| |
Change-Id: Ie1f01771518e82eec378564ddde34ae0fb7f0ac6
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix consists of -
In case small size disk is present in cluster TC
'test_create_max_num_blockhostingvolumes' uses blockvolume size
as 0 due to default BV count, which leads to failure of BV creation.
To fix issue set BV size to 1 and BHV count to free size in case,
mod operation returns 0.
Change-Id: Ia5c656e215498acdc86383c9a771a0094de70716
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
| |
Change-Id: If4293d3987b9de55845eea95ddd3f5e309ea810a
Signed-off-by: Sushil Gupta <susgupta@redhat.com>
|
|
|
|
|
| |
Change-Id: I43ebf7f489f0e80f33992edc7cea6a54dcc8a531
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
| |
Change-Id: Ia5a0d5a8ac9319628f9a3d4d00d0f70876fe3281
Signed-off-by: susgupta <susgupta@redhat.com>
|
|
|
|
|
| |
Change-Id: I1d497a9b61762e68558026ddc49e5269b0354ce1
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
| |
Change-Id: I29093a09c3f0cc09eaa9c6d94bad882c0bafd91c
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
| |
Change-Id: Ibb96e961b1501ef696858a5eec80422471e877fd
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
| |
Code creates file volume and tries to delete blockvolume
instead of file
Change-Id: I4c73f388dc10a153f254c479bc8bf127df644916
|
|
|
|
|
|
|
| |
Confirm no inconsistencies occur in targetcli when block
devices are created with one block hosting volume down.
Change-Id: I2a755ef2a88c6e6ca5326be3787ac07c0fb7db26
|
|
|
|
|
|
|
|
| |
Validate whether creation of maximum supported
blockvolumes doesn't have any impact to the
functionality of gluster-block.
Change-Id: I2a1503f527da2d1d916e87ce154e88bf9b5e1fa8
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
Validate creation of block volume with name
Change-Id: I08ee31201d42a95f8a829eb54ce68421903fdbbf
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
|
|
|
|
|
| |
Change-Id: I7ead23c46a472fee70d684c45f32f5e4efb0674f
Signed-off-by: kasturiNarra <knarra@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Move all the files of 'cns-libs/cnslibs/common' dir
to the 'openshift-storage-libs/openshiftstoragelibs',
because 'common' is the only dir there, which doesn't really makes sense.
And "cns" is old project name, so, replace it with
"openshift-storage-libs".
Also, fix all the imports of these libs.
Change-Id: Ife00a73554e73b21b214b15016b0c8dbbf423446
|
|
Move all the files of 'tests/functional/common/' dir
to the 'tests/functional/', because 'common' is the only
dir there, which doesn't really makes sense.
Do the same about 'tests/functional/common/heketi/heketi_tests'
and 'tests/functional/common/heketi/'.
Change-Id: I1fa55e2e7bf09e9b9115629b06e1fd160e291a36
|