| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
BZ-1632873 was fixed, hence, unskip test cases which were
skipped due to this BZ. Also, make it run only on containerized
Gluster clusters.
Change-Id: Iee49a303c4f191652d1c94c18e830e6d2fb4e381
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It happens, that Heketi commands hang.
So, to avoid cancelling of whole test runs, add
timeouts for Heketi commands.
By default, timeout is 120 sec (2 min).
If it is needed to change default value, then
define following config option:
common:
heketi_command_timeout: 180
Change-Id: I79f33daa05bde9a37245e94e66042944c6cd9242
|
|
|
|
|
|
| |
Because BZ-1609703 was fixed.
Change-Id: I86e7690e8a190d9f913fb0140780a0bcbcce1e72
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For case when it is needed to provide info for bugreport
or debug in general.
It can be run anytime, separately from the deployment logic.
Example command for running this new playbook:
$ tox -e ocp3.11 -- ansible-playbook -i 127.0.0.1, \
playbooks/gather_logs.yaml \
-e config_filepath=/path/to/the/cns-automation-config.yaml \
-e output_artifacts_dir=../cluster_logs_ocp310_ocs311/
NOTE: 'tox -e ocp3.11' can be omitted only in case you enable
'yedit' (yaml edit) module by other means.
Change-Id: Icb6bf442c07d8d949c930747e8131231a2ff112c
|
|
|
|
|
|
|
|
|
|
| |
To enable or disable CRI-O just define following option:
openshift_use_crio = true/false
In the "ocp-on-vmware.ini" config file.
Change-Id: Ibd3843d8aa13bfacb0d927142786dc5599e65315
|
|
|
|
|
|
|
|
| |
When VMWare hypervisor is under heavy load,
node boot up may be slower than 3 minutes.
So, increase timeout from 3 to the 6 minutes.
Change-Id: I27f0166d6c4221f7a647d55df704f429bf9d6dcc
|
|
|
|
|
|
|
|
| |
As of now, it raises exception when our command doesn't fail, but has
empty output. It is bug.
So, fix it by checking only return code being non-zero.
Change-Id: I6c029e17220d6ae7eb184348d84c189ba03274c8
|
|
|
|
| |
Change-Id: Ib596c79ea3e7c3dd6c83c533e708313f3c4ecc2f
|
|
|
|
| |
Change-Id: If79bab256041a75b6388bdabd9ed0aec56d0340f
|
|
|
|
|
|
|
| |
"wait_for_pod_be_ready" and "enable_pvc_resize" hide errors details
when errors appear. So, fix it by printing full error info.
Change-Id: I250ff723c0453fd487f8c1810cdd2c1d7d2ec16f
|
|
|
|
|
|
|
|
| |
Rename test module to remove P0 from its name.
Which will let us comsume same files for adding other priority test
cases as well.
Change-Id: I66cbb34ba7ecee1130b7d55952310955a9fe8722
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Add 2 test cases, where one verifies creation of an app pod on the
Gluster node and another on the separate node
Change-Id: I99dfc5db7fa74d0f69115cfed470f72e66b1a256
|
|
|
|
| |
Change-Id: I519ce5c26f7bd6480a48512744626ba812524413
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Following modules:
- deployment/playbooks/library/vmware_folder.py
- deployment/playbooks/library/vmware_resource_pool.py
Were broken by '2035d7e6' commit with pep8 fixes.
It was broken due to the change of the import module logic which led to
the absence of required modules imports.
So, fix it by using 'expected' import approach - importing
functions directly, not modules.
Change-Id: Ib1f9db410a8aa0171fea0e7017e29148167baf65
|
|
|
|
| |
Change-Id: I95154066af3e574059199ced18239f7e34c95335
|
|
|
|
|
|
|
| |
Changing assertion logic. Now, instead of checking fstab file,
we check brick paths presence on Gluster PODs and nodes.
Change-Id: I00ed0cb5ef18b67ad0f112276120624c0c0b0763
|
|
|
|
|
|
|
| |
In case of error on CRS node we get incorrect error message.
Instead of command error we get another kind of an error.
Change-Id: Ibfd21d518c220951a981f23daa5d32b1963061f2
|
|
|
|
|
|
|
|
|
|
|
|
| |
Right now, we use single prefix for all the test cases of
'test_gluster_services_restart' python test module.
It is fragile approach, because if first test fails to delete
heketi or gluster volume, then all other test cases fail too,
but should not do it.
So, use unique prefixes for each of the test cases in this module,
to make failure be unique per test.
Change-Id: I1cc68ffc0553f79d0b0623335a2aaf985feabade
|
|
|
|
|
|
|
| |
User's home dir in CRS logic was hardcoded as "root".
So, fix it by calculating home dir of the current user.
Change-Id: Ib586fa605390126eb3a2efaf8c93856e52676aaf
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before, 'heketi_version.py' module didn't consider version of the
'heketi server' package on the Heketi POD. But it is more valueable than
depend on the client only. So, make all the requested version
comparisons be applied to the server's version.
Interaction with the module's logic stays the same, just one behavioral
thing changes: now, if client version is older than server's one, we
raise exception.
Change-Id: I317102556d4a5f51607c3b9da93da0d4a3b74f7f
|
|
|
|
|
|
| |
To let system services start up in time.
Change-Id: I4b4781119656c9fdc75017a28c80c20bdd0eae21
|
|
|
|
| |
Change-Id: I5f25b1dfce5d3298295939f59c3ff435ae7c6d8a
|
|
|
|
|
|
|
|
| |
For the moment, if subscription manager fails, we continue
deployment, but it is mistake. We just spend redundant time
before we try to install anything.
Change-Id: Ib95c00a3c605b98f3cd6b7998d4b482533a5d491
|
|
|
|
| |
Change-Id: I51056965a55f73b0cb4b7dac8f1d4234f2f66528
|
|
|
|
|
|
|
|
|
|
| |
Before, we were installing latest heketi-client version on master nodes.
But, in case we install old OCS/CNS we may end up with false
impression that we have new features, when it is not so.
So, read heketi-client package version from Heketi POD and install
exactly the same version on the master nodes.
Change-Id: Ic4e9edd7f6ef614d28c061712473aaf9b9f652e2
|
|
|
|
| |
Change-Id: I40b7ea79d1f7dbc82db825f6ced4447a157361e6
|
|
|
|
| |
Change-Id: I91f916e31bb23197dd972a17dd3a5ee62ee04b77
|
|
|
|
|
|
| |
These two files were missed due to improper .gitignore file data.
Change-Id: I49f396c1c1d37fcbd4257bf35aaee75f41b099bc
|
|
|
|
| |
Change-Id: I67a6306fa6cd2b5c5c886efbdbdd5a7134b3225e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add end-to-end deployment tool of OpenShift and OpenShift Container
Storage on top of VMWare.
Added code is modified version of the
'reference-architecture/vmware-ansible' dir from the following repo:
https://github.com/vponomaryov/openshift-ansible-contrib
Read 'deployment/README.rst' file for more details about the
deployment tool.
Change-Id: Ic96f252ff786cc1ecf24d27f0ec47e324131e41b
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In some cases, it is useful to stop test execution after first failure.
Not only stop it, but also skip all the scheduled cleanups.
It will allow us to keep a cluster in the best state for a root cause
debugging.
Just define 'common.stop_on_first_failure' option to True value
in the config file. It will make the test runner stop after first
failure skipping all the scheduled cleanups and pending test cases.
Change-Id: I963eb038a11a8e2088a84f7ba4838870ea3e657a
|
|
|
|
|
| |
Change-Id: I7f4fea8f197294f2df8bba19c8c0f0422b62892a
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
|
|
|
|
|
|
| |
To be able to perform safe Heketi client package version comparisons.
Change-Id: I64f0a55f988fc1446b133556c395f0640d65ada1
|
|
|
|
|
|
|
|
| |
In case of network problems, "curl" command may stuck in
a retry-loop. So, add explicit time-limit as 10 seconds to avoid
endless waiting of the functions which use it.
Change-Id: Ia2d94358e8f978cb73360535167c703da2636874
|
|
|
|
|
| |
Change-Id: I9ab3c6bea56a02f76ce818ee095ffe4afc0e64c0
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
|
| |
Trying to create pvc with defined arbiter file size and
verifying that when we are expanding volume it is expanding
according to avg file size
Change-Id: I5c39339f70702bf685c237ae16e21f54384e51db
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This test case talks to the Gluster PODs directly. It is not
compatible with Standalone Gluster clusters.
So, fix this test by reusing special common function,
which allows us to abstract from Gluster cluster deployment type.
Change-Id: Ib131984ac0a4623d1d847f9961be26da573d8513
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Removing this code as it is in additional library file, requires to
pass config through config file and requires to upload the scripts.
Also it contains hardcoded credentials.
Will add new function in openshift_ops.py library similar to
"oc_create_app_dc_with_io" with new updated template.
Change-Id: I7cfce3fe23b222d40bff1c829afa97f2ffcb621d
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
"heketi-cli" requires quotes for "--gluster-volume-options" arg.
Without it command will fail. So, add missing quotes to make it work.
Change-Id: I17fddfe653dceaa3c6b56f2a473ca7798de02698
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
|