This commit adds the releasenote to tag Tempest for Victoria
and needed for version 25.0.0 to release.
Change-Id: I74db083a53ce0801416f8e1e992ea3e9331ea66a
We are going to release Tempest new tag to declare the start of support
for stable/victoria. So that new tag use stable/victoria constraint in
the tox env.
For example, if anyone use Tempest 25.0.0 in future, let's say 1 year
later then tox env also should use the victoria constraint for
compatibility instead of master.
These need to be move back to master constraint, once release is done.
By using master constraint in tox for all the old tag is problem and we
faced the issue of constraint incompatibility due to that and we have to
workaround it all over the devstack, tempest role, grenade to set the
stable constraint via env var.
Further information:
https://docs.openstack.org/tempest/latest/requirement_upper_constraint_for_tempest.html
Change-Id: I1f8c788327b4a1a7f804cf01f8c22609e6646dd9
When Tempest is used in customer site, often we are required to
provide a testcase list including testcase names and descriptions.
Now no this kind of doc is available, so we can add descriptions
with the format of doc string for every testcase, so later we
can generata such a testcase description list.
There are hundreds of testcases missing descriptions, so we can
add them gradually, and limit the modified files in one patch
for the convenience of reviewing.
Change-Id: I5bf95ca579b731ca4baefb590edb8e265126ce4f
partially-implements: blueprint testcase-description
We have recently observed that ssh-keygen by default
create OPENSSH format for keys and paramiko got the
support for decrypting it from paramiko 2.7.0[1]
We have recenlty seen failures in whitebox plugin but
considering this can also be observe in tempest as well
it's good to update the version here too.
[1]: http://www.paramiko.org/changelog.html
Change-Id: I3603bbc9787e99fe864a4ec63d49fea6b90a45a8
Nova is removing the XenAPI virt driver. There are a number of APIs that
only work with this virt driver so those are being removed at the same
time. Once removed, they will return a HTTP 410 response, regardless of
the microversion.
Add a feature flag that allows us to skip these tests on clouds that no
longer provide these APIs. It default to False (skip). We will set this
to True (do no skip) on stable branches of nova.
Change-Id: I0ae3f7a81ca7b56f56871e61bcf196ca572ae6d6
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
A volume attached to multiple servers has multiple attachment structures
that are distinguished by their "attachment_id" field, not the "id" one.
So when setting up a waiter watching for an attachment being removed,
the "attachment_id" field must be passed. Thus, when attaching a volume,
it is necessary to wait until the attachment shows up in the volume's
data and then use the "attachment_id" field of that record to pass to
the waiter invoked at tear-down time.
Change-Id: I9ab9f786b23061dd3a6a3482ab9739ba504d2bc0
Closes-Bug: 1894724
Change I2ab6ecfeb0c48c7ef4a0fc94e670d43dbc3f6650 added response
schemas for volume backup responses. The schema specifies the 'name'
as type string in the response for create-backup and update-backup,
but the name is not required in the create request and the cinder
backup service does not supply one. This element should be string
or null.
Change-Id: I032e54a2065859d4ebc0969faccf68494fe745bc
Closes-bug: #1894844
This commit makes to use os.path.join instead of using the Unix path
character '/'. This change is not mandatory since we don't support
Windows environments as Tempest execution and, it seems Windows supports
'/' as a path separator. However, using both os.path.join and '/' is a
bit awkward.
Change-Id: I117acb281c352179d526808009e761335bb314fc
and add missing docstrings
Earlier implementation of this api just detached the
volume and wait for the volume to be in 'available'
state.
But the scenario manager don't really verify the state
of the volume. Tempest plugins do verify the state.
Implements: blueprint tempest-scenario-manager-stable
Signed-off by: Soniya Vyas<svyas@redhat.com>
Change-Id: I023177c09cf035bbb29941cc5d4bb4cc6c60ed1c
This patch addresses following facts:
1. common manager methods among plugins should be
defined in Tempest.
2. methods should be consistent with names and
parameters.
3. Add docstring about method usage and parameter.
Implements: blueprint tempest-scenario-manager-stable
Signed-off by: Soniya Vyas<svyas@redhat.com>
Change-Id: I191c8861c9ec29b78c9c8ad12ff2ddf3ffbf4db1
This is to add response schema validation for volume manage.
As gmann pointed out in https://review.opendev.org/#/c/616783/,
the response of volume_manage is same as that of show_volume,
so here we use common_show_volume directly.
Change-Id: I5e26d0cca87c303ebb9a2fe93ad0b13b73eb41a6
partially-implements: blueprint volume-response-schema-validation
