| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Changing assertion logic. Now, instead of checking fstab file,
we check brick paths presence on Gluster PODs and nodes.
Change-Id: I00ed0cb5ef18b67ad0f112276120624c0c0b0763
|
|
|
|
|
|
|
|
|
|
|
| |
Renamed cns_baseclass.py to baseclass.py with updated BaseClass.
Merged HeketiBaseClass to BaseClass with appropriate changes.
Updated delete_volumes and delete_block_volumes methods used in
test case method with heketi_delete_volume and heketi_blockvolume-
delete.
Change-Id: I8f623f1692cd863dc8ff041f7e8525ee0dc84f7b
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
|
|
| |
Add Heketi version checks to the test cases and Heketi libraries.
In case of incompatible Heketi version in a setup,
test cases will be skipped and direct usage of Heketi libraries
will cause them to raise the NotImplementedError exceptions.
Change-Id: I462e76f615165140f2a8c7e796c1c582b8f4dc91
|
|
|
|
|
|
|
|
| |
This library is helpfull for diagnosing output of gluster and heketi
and it compare both the outputs and the test case verify this feature
is working properly.
Change-Id: Ice607003f32db2bce2f540a7651024b66b071634
|
|
|
|
|
| |
Change-Id: I9ab3c6bea56a02f76ce818ee095ffe4afc0e64c0
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This test case expects that Gluster cluster has the same amount of
volumes as Heketi does. But, it is wrong expectation.
We may either create gluster volumes without Heketi or have
mismatches after some other Heketi failures.
So, fix this test case by comparing starting and resulting amount of
volumes in Gluster and Heketi.
Change-Id: I322c922fbdf102ccc5fb9f2145eef7b3f1d1a80a
|
|/
|
|
|
|
|
|
|
|
| |
For the moment, we have 3 different test cases which use
'additional_devices' config option. All of them will fail in case
of specific structure of config.
So, make those test cases be smart enough to understand absence of
such option data and skip test cases with useful info about it.
Change-Id: Id31de7e20188041d2148edf37b3f8c95645c5e52
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This test case has fragile logic. It doesn't assume
we expect new block hosting volumes to be created when we calculate
the size for block volume.
So, fix it by doing 2 things:
- Use total block hosting volume size, not it's 'free space'.
- Get info of block hosting vol if block vol gets created unexpectedly,
and read it's size. If the size is bigger than block vol's size, then
pass the test.
Here, we assume that existing, during calculation,
block hosting volumes were not the biggest possible and
autocreation is enabled in addition to the presence of
the available size on the Heketi devices.
Change-Id: Ic7d5325b1144dce0e56999617f3c6d7c0829e42d
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Because it was very fragile and skipped due to bug.
So, after bug was fixed we need to enable it back.
But, also, considering it's stability, it required complete change of
logic. So, it is rewritten completely and moved to more appropriate
module where we have other test cases which perform device operations.
Change-Id: I1b8c18c8ea883f83861e81e97c534459d7588175
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It was skipped some time ago due to the bug. Now this bug is fixed.
So, we need to unskip it. So, do it, in addition to the required
refactor.
Change-Id: I7c426e9cd3dc38ed48e5b91870bc10bd63998694
|
|\| | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Current 'test_add_device_heketi_cli' [CNS-877] tc completely duplicates
another existing tc - 'test_device_remove_operation' [CNS-766].
Being, on it's turn, very fragile and requiring refactor.
So, remove this test as it makes no sense neither to keep it skipped nor
to refactor it.
Change-Id: I40cf7b3d015d1345f0ac2a89569dd64cd67711d3
|
|/
|
|
|
|
|
|
|
|
|
|
| |
In some rare cases we get following error trying to create distributed
volume:
- Insufficient suitable allocatable extents for
logical volume tp_foo: 25344 more required.
So, fix such situation by catching exception with such message and
retrying with smaller volume size.
Change-Id: I015a4547347858cd8aff9e566e3dc662a94b6b83
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now, it is possible to run glustolibs commands
on both deployment types: containerized and standalone.
It is possible using 'auto_get_gluster_endpoint' as target for
lib function in addition to the '@podcmd.GlustoPod()' decorator.
Example:
"""
from glustolibs.gluster.volume_ops import get_volume_list
from cnslibs.common import heketi_libs
from cnslibs.common import podcmd
class TestExample(heketi_libs.HeketiBaseClass):
@podcmd.GlustoPod()
def test_get_vol_list_either_on_node_or_on_pod(self):
volumes = get_volume_list('auto_get_gluster_endpoint')
"""
Also, delete all the current usages of 'deployment_type' config option,
and delete the option as unneeded anymore.
Change-Id: I281f287c432a5a9efefda588be436ee285188697
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This test is broken in several places.
So, fix it and also remove redundant steps.
Change-Id: I7a9f2c077dda35a8a477fa27882cddf79ec69ac5
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| | |
Removing several unused options and replacing couple of them
with built-in values.
Change-Id: I458f0eae6a68ddcb2711d454c81cdcee8142673a
|
|/
|
|
|
|
|
|
|
|
| |
Which uses improper vars in block of code where we disable
redundant nodes. It is just not executed in case we use
3-node Gluster cluster.
So, fix var usages making this test be compatible with 4+ node GLuster
clusters.
Change-Id: Id9ac9ae9b614c492c0f39573c0224378f887fee5
|
|
|
|
| |
Change-Id: I7d05c73f468634300ad8571fd9b1b4855adac632
|
|
|
|
|
|
|
|
|
|
|
|
| |
Doing following:
- Remove dead code with usage of Heketi python lib.
Because it is not used and not tested.
- Remove unused functions in general.
- Make existing functions raise exceptions with CLI error message
instead of returning 'False' boolean value hiding info about
original errors.
Change-Id: I1f0def567dd77425397ff2c8ba13f9c0640af5bc
|
|
|
|
|
|
| |
Remove unused/dead code from base classes.
Change-Id: Ib355e0282541c60297c1b240f7ff8df3f06d9d69
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
CNS-1246 - test case for veryfying cluster count of heketi metrics
CNS-1247 - test case for veryfying nodes count of heketi metrics
Change-Id: Id6c6bdb9bf212b4c302ff56e2f68b5e6e4348143
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
List of changes:
- Fixed bug, where test didn't fail in case volume brick was not
found in fstab file. It was only logging message related to it.
- Fixed bug, where we searched for all the brick paths in one single
Gluser POD, such thing should have been failing always. Above
mentioned bug has hidden this one.
- Fixed bug, where test was failing in case we didn't have passwordless
SSH connection between test-runner and heketi-client nodes.
- Added Heketi volume cleanup for case our test fails before the
step with Heketi volume deletion.
- Removed redundant copy operations of fstab files. Instead, used
'cat' shell command for getting inner data of fstab files.
Change-Id: I76c6a59ab9f40cc5e94923fcc82e5e15f640714a
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If 'test_blockvolume_create_no_free_space' tc fails, then
we get too few info about the error. So, add more data to the
error message. In addition, add 2 sec sleep to avoid races getting
list of block hosting volumes.
Change-Id: I53cdff368b4f9813a31226921d0554e98790c7a1
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Do following improvements:
- Calculate distributed replica vol size dynamically based on the
current free space on the heketi devices.
- Add check for amount of bricks.
- Cleanup volume more correctly.
- Check free space after deletion considering the size of deleted vol.
- Rename module.
- Move module out of "heketi_tests" to the parent dir called "heketi".
Change-Id: I42fdfadc97157595857e5a106760391281f59a1a
|
|/
|
|
|
|
|
|
|
|
| |
By doing following:
- Pick up only online nodes with only online devices.
- Create volume to make sure we have some usages in any of a node
devices.
- Check that node hasn't been deleted at the end of the test.
Change-Id: I73154642c9034f84b6748c5cd9df43b67eb01006
|
|\ |
|
| |
| |
| |
| |
| | |
Change-Id: I5ce399b39201dfb09d4ad459a039d938596a71e4
Signed-off-by: Ashmitha <asambast@redhat.com>
|
|/
|
|
|
|
|
|
|
|
| |
CNS-1243 - Heketi_metrics_generate
CNS-1244 - Heketi_metrics_validating_VolumeCount_on_creation
CNS-1245 - Heketi_metrics_validating_VolumeCount_on_deletion
CNS-1262 - Heketi-metrics_validating_heketi_pod failure
Change-Id: Idb863d1ceaf555dfc2a9cff863b97cda65a816f6
Signed-off-by: nigoyal <nigoyal@redhat.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
We expect some set of data in the heketi device info API response.
So, get list of devices and check that their data satisfy our criteria.
Change-Id: I984f993ad7d0adca1b9a722cf0193b6db3d486b7
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This test cases test the functionality of device
enable from heketi-cli
Signed-off-by: Madhu Rajanna <mrajanna@redhat.com>
Change-Id: Id0b3779eb5130e7d2d14ee6722a8b1c54fc9d830
Signed-off-by: Madhu Rajanna <mrajanna@redhat.com>
|
| |
| |
| |
| | |
Change-Id: I97c949614ca70ea3e732c8c2ca70022d062ad04c
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Change-Id: I00586ecd7ac2270721194542c07f51d2ca5ef807
Signed-off-by: Madhu Rajanna <mrajanna@redhat.com>
|
| |
| |
| |
| |
| |
| |
| | |
Validate behaviour of the system when we try to create block volume
of size bigger than we have available free space.
Change-Id: I754e09f7fc27ce9b7ac2b01dda163ce20573e963
|
|/
|
|
|
|
|
|
|
|
| |
Blocked by BZ-1629889.
When referenced bug is fixed completely we should refactor this
test first, making it not dependent on the specific volume sizes
as it is now.
Change-Id: I1d4c4a0605fd800fa8450f92dab7b50e29856a5e
|
|
|
|
|
|
|
|
| |
Making its 'test_volume_creation_no_free_devices' test
be aware of the actual available free space, which will make it work
much more reliably.
Change-Id: I2555ffeaad825b16ffee7ded067eab92d40519e4
|
|\ |
|