We have a bug in dynamic creds creation where project creds
with different roles are created under a new projects. Creds
of different role of projects must be created within the same
project.
Fixing the creation of 'project_admin', 'project_member',
'project_reader', 'primary' creds in same projects. All the alt
creds will be created under same projects. but main and alt creds
will use different project, for example, 'project_alt_member'
and 'project_member' creds will be created in different project.
'admin' creds will continue be in new project as many test
use it as legacy admin.
Closes-Bug: #1964509
Change-Id: I9af005e2900195c42ecbbf7434facae2d3952f30
While debugging the ``rescue`` test functionality with ironic's
tempest plugin, we discovered that if the environment suggests the
agent is available, then we may enter a situation where the test
can fail because paramiko prefers ssh over password authentication.
This is important, because for rescue functionality in particular,
it is password authentication based without the use of SSH keys,
as a temporary password is generated by the services and provided
to the user requesting to rescue the instance/node.
Instead of trying to make an assumption that password being present
means we should just disable the agent, explicitly allow the caller
to specify it.
Change-Id: Iefb6cb5cb80eb2b9a4307912c4d6d07c684ed70a
Adding placement service in 'enforce_scope' config
so that we can switch the placement scope and new defaults
and test them.
Change-Id: Ie9a4c22dee892eae84f35af2b6b5ff2098225495
This adds tests for the currently untested locations support in
images. A feature must be enabled for this to work, so a feature
flag is added to control it.
Change-Id: I779c959096b3aa9cc3d0fbf1e3c506a22d0a49fb
This is so to configure which hashlib algorithm should be used for
the temp_url tests, defaulting to sha256 but preserving the
ability to use sha1 for compatibility with other Swift implementations.
Change-Id: Ia4923d47870fcb914a33adecb7155763ec1d0b2f
This marks the end of support for stable/victoria
which is EM now[1]. This remove the stable/victoria
jobs and also adds relesenote to mark the end of
support of Victoria.
[1] https://releases.openstack.org/
Change-Id: Ia63cdc682a32a2bcfd748f924368db6028b64d8c
This patch adds the ability to measure network downtime during live
migration process.
A fixture has been added to start and stop a background pinger
process and also read status from it.
The downtime measurement has 0.2 seconds granularity.
In order to reduce overall traffic the ping payload size set to
minimal value.
Change-Id: I83c6a5d49f5d4da05deb677907e5048ecdd2242b
Nova has remvoed the API extensions concept since
stein release
- https://blueprints.launchpad.net/nova/+spec/api-extensions-merge-stein
Nova cannot be configured to enable/disable extension now
and all extensions are enabled by default. Stein is not
supported by the Tempest master so it is safe to remove the
config optionn as well as the checks from tests.
Change-Id: I05c0a3b23d0824e1eb9a79353dcf2976c6bcf602
As the version of cirros used in OpenStack CI does not support SHA-2
signatures for ssh, any connection from a FIPS enabled machine will fail
in case validation.ssh_key_type is set to rsa (the default until now).
Using ecdsa keys helps us avoid the mentioned issue.
From now on, the validation.ssh_key_type option will be set to ecdsa
by default for testing simplicity.
This change shouldn't have any drastic effect on any tempest consumer,
in case rsa ssh type is required in a consumer's scenario,
validation.ssh_key_type can be overridden to rsa.
Relevant-Bug: #1960692
Change-Id: If9becae119e2a5dc51d4911a0ac9759fbcf24998
This marks the end of support for stable/ussuri
which is EM now[1]. This remove the stable/ussuri
jobs which are failing due to bug#1968798 and also
adds relesenote to mark the end of support of Ussuri.
[1] https://releases.openstack.org/
Change-Id: Ieeb4da8859d44470c5cb67a62f2dcfd7786daf3a
In FIPS mode, using RSA keys for ssh is fine as long as SHA-1 is
not used for the signature algorithm. Unfortunately, the version
of cirros used in OpenStack CI does not have a version of dropbear
that supports SHA-2 signatures. So, any connections from a FIPS
enabled machine will fail as the cirros instance will only support
ssh-rsa (SHA-1 signatures).
To get around this, we add a new option to specify the key type
(validation.ssh_key_type). This will allow the addition of other
key types in future if needed.
Tempest now supports 'rsa' and 'ecdsa' key types.
We also add a fips job to the experimental queue to test the usage
of the new key type.
Change-Id: Ib59eb8432fa1a2813b3047955157d1b3d24a55f8
There is a non-negligible number of tests in tempest that need accounts
generated by account-generator with a concurrency of at least 2. Running
these tests with accounts generated with the current default value for
concurrency makes them therefore fail.
This change sets the default value for concurrency to 2 and updates
the documentation for --concurrency parameter.
Closes-Bug: #1948935
Change-Id: Iada980beff9db3c8cd02c84d0d7602264b66ddf8
We have moved the API microversion fixture to
tempest.lib.common.api_microversion_fixture location.
This commit deprecates the old fixture so that we can
remove them in Z cycle.
Change-Id: If38aa21a4cd99d2a5fe4a5c3b41214cd54f97f8d
As a preparation to test Network QoS minimum bandwidth and minimum
packet rate rules together this patch the necessary packet rate API
client to tempest lib.
blueprint: qos-minimum-guaranteed-packet-rate
Change-Id: I1c5c82e8178462652c36533093958c82b5130a55
Use common method to delete objects and containers after Swift
testing. The used method ensures proper deletion before continuing;
simply listing and deleting sometimes raises exeptions due to delayed
executions.
Also fixes a docstring to reflect current behaviour.
Change-Id: Ieaaba496028de741f3e506dac800b151aa833333
Tempest 29.0.0 has been released [1].
This commit adds a new page for 29.0.0 release notes and for
2 previous releases (as we forgot to add them before).
[1] https://review.opendev.org/c/openstack/releases/+/808035
Change-Id: I51e8906a89bae107a4fe162fcc785130edaa3565
"QoS Limit Bandwidth" APIs must be used in Octavia-Tempest-Plugin
to add missing QoS based tests.
Note: this patch fixes the "expected status" code for
Update Minimum Bandwidth, that was set to default 200 instead of 202.
Change-Id: I30d9d823c972e560a0a48e24e44fb16bcc353c5a
This relesenote mark the end of support of Train release
in Tempest as it is in EM state[1].
[1] https://releases.openstack.org/
Change-Id: I437eda1acc88ac6f84b8c01d81e04afb4df1d40e
Volume tests had hardcoded value (1) in case they were creating
a second volume with a different size than the first one
(CONF.volume.volume_size). This is a problem for systems which
have a chunk size other than 1. The patch is adding a new opt
CONF.volume.volume_size_extend which allows customization of an
extended volume size.
Closes-Bug: 1917299
Change-Id: Ic8ae486224cd2a470f4f9bbad62d4d6715cc63ac
Ghanshyam Mann