This has been removed, which now causes these
tests to fail.
Tempest change: https://review.openstack.org/#/c/448869/
Change-Id: I31310dc9b3834e0bf16618db3e473f17eab2b610
There are several places in the source code where HTTP response
codes are used as numeric values.
Status codes 200, 202, 204, 400, 403, 404, 405 and 413 under
tests/functional, tests/tempest and tests/unit/api are replaced with
symbolic constants from six.moves.http_client thus improves code
readability. More patches will be submitted to address other status
codes.
Partial-Bug: #1520159
Change-Id: Idc4d3ee8469e7a41dda2d33f4e0629442bbbce4c
Tempest provides stable library interfaces under tempest.lib.
This patch switches to use it for data_utils.
Change-Id: I9ec9282268adc80c947e18c34f34dc0fdd82b187
test.idempotent_id is being kept temporary to migrate
to new lib interface. Now idempotent_id is available as Tempest stable
interface decorators and all plugins tests using the old decorator
should be switched to new interface.
In future, Once all plugins are switched to new decorator Tempest
will remove the test.idempotent_id
Change-Id: Ie7789c072b8954de5821777bf3f672cdfa4bceca
Related-Bug: 1616913
Existing methods - wait_for_volume_status,
wait_for_snapshot_status and wait_for_backup_status
were combined into
wait_for_volume_resource_status.
This patch is intended to fix the issue occured
due to above change.
Change-Id: Iaf1fd19a3fdf50aec8aaddffdcbaf6d0466fbd35
Closes-bug:1667448
test.idempotent_id is being kept temporary to migrate
to new lib interface. Now idempotent_id is available as Tempest stable
interface decorators and all plugins tests using the old decorator
should be switched to new interface.
In future, Once all plugins are switched to new decorator Tempest
will remove the test.idempotent_id
Change-Id: I6e24344a809ef397a252fe1fb002b2cad10cd5ba
Related-Bug: 1616913
Tempest tests that are added:
1) test volume snapshot backup
2) test backup create and restore to an existing volume
This test can reproduce the bug that is related.
3) test incremental backup
Co-Authored-By: Oleksii Butenko <obutenko@mirantis.com>
Related-Bug: #1335889
Change-Id: Iff857ee11ed15665315077a0ba22cf31f92efe4b
Instead of registering new groups we can reuse already registered
groups in tempest/config.py.
Changes should be made to the following groups:
a) service_available_group - We don't need this group in plugin code
because it is already being registered in tempest code and service
availability is being checked for in the /tempest/api/volume/base.py
and the test cases in plugin code inherits this base.py
b) cinder group - Instead of registering a new cinder group for plugin
tests we can add plugin specific configuration options in the existing
volume group as the same conf object from tempest is being passed on
to the plugin
Change-Id: Ie0ca52ec389c581ca47db3e9bbb0793a2bb47fdf
Closes-Bug: #1626575
We don't really need this placeholder here now,
test_volume_unicode.CinderUnicodeTest is probably a
sufficient test for this role.
Change-Id: I9dd58c05d08b6bcf2d8880e7856f679f57b0849c
The tempest volume client used to provide a default volume size. This
was changed in I2a0f5841fe82ab003562749a63bc4894225699c5. Tempest tests
now need to provide a size when creating a volume using this client.
Change-Id: Id1a646cfbd11803a796205af8baa0ac783e9ec3a
Closes-bug: #1620613
These tempest tests add coverage for all the API's related to
consistency groups in Cinder. They were originally proposed
for upstream tempest in https://review.openstack.org/#/c/252213/
but were not a good fit since they aren't supported by the
reference driver. They have been modified to work as part
of the in-tree tempest plugins for Cinder now.
The tests are behind a new config option for tempest, which
in turn is part of a new config group called 'cinder'. This
was added to avoid any collisions with the 'volume-features-enabled'
or 'volume' groups already in the upstream tempest tests.
To enable them set the following in tempest.conf
[cinder]
consistency_group = True
Then make sure to run tempest with the 'all-plugin' tox environment.
Don't forget to update policy.json to allow for CG API's to be called..
Change-Id: I772ea13ca156e71620d722eee476f222a8653831
Co-Authored-By: Xing Yang <xing.yang@emc.com>
To avoid conflicts, it needs to be done and
the subdirs 'api' and 'scenario' directly under
the cinder/tests/tempest directory
Closes-Bug: #1577016
Change-Id: I5b8d1411e0917ecb7e70eb5a6b139d75437ba032
Isaac Beckman