_get_network_by_name() is made public by this commit as
the tempest.scenario.manager interface is meant to be
consumed by tempest plugins.
Implements: blueprint tempest-scenario-manager-stable
Signed-off by: Soniya Vyas<svyas@redhat.com>
Change-Id: Ia102acea773bd80d933a7e0a19b447f91134f81f
_create_network() is made public by this commit as
the tempest.scenario.manager interface is meant to be
consumed by tempest plugins.
Implements: blueprint tempest-scenario-manager-stable
Signed-off by: Soniya Vyas<svyas@redhat.com>
Change-Id: I3f6b8e274f9b57ae8d1389a188636660854971e3
_cleanup_volume_type is made public by this commit as
the tempest.scenario.manager interface is meant to be
consumed by tempest plugins.
Implements: blueprint tempest-scenario-manager-stable
Signed-off by: Soniya Vyas<svyas@redhat.com>
Change-Id: Ia2116e9d1738276ae1edf566e6f5b9760d416ab9
The volume creation uses default volume type from the backend. In
case of multiple backend, at the moment there is no option to test
volume test cases with volume type which is not default volume type.
Add a new config volume_type in tempest.conf.
Change the code to create volumes with volume_type mentioned in
the config.
Make sure when volume_type is not specified then volume will be
created with default volume type.
Change-Id: I1b4601e2ce6c83ec727b6dea65c67cacbfcfe957
Neutron recently enhanced CIDR overlap checks for all the subnets
attached to router including external [1]. This breaks tempest
scenario ipv6 tests which is fixed in tempest by the following
commit [2]. However the fix mentioned in [2] cannot be ported
back to tempest 23.0.0 as rocky is in EM stage.
To fix this, the public IPv6 network CIDR is changed to use
different subnet on the tempest-slow job.
Closes-Bug: #1914037
[1] https://review.opendev.org/q/Id5d8ac09a38c656619f88a6f87b8f384fe4c55a8
[2] 4ad346e649
Change-Id: I62a746cc871434e8488b19bc2ef5bbcfcf4f0be6
swift was disabled in tempest-full-py3 as
it was not ready on python3. But since ussuri
or train swift run fine on py3 and we have
tempest storage integrated py3 job also running on
swift gate.
This commit enable swift for ussuri onwards.
Change-Id: I63159e5e8c0c8b6751ea481577b4c4637a7f25b5
As a part of the scenario/manager.py stabilization tracked by
the below BP the patch adds kwargs argument for create_volume_snapshot
method so that the consumers are able to pass additional parameters
if needed.
Implements: blueprint tempest-scenario-manager-stable
Change-Id: Ib58a6125b34adb932e1f282ebab6a79a6906dd73
Before [1] we didn't have conditionals for tempest_black_regex
being set or not, therefore it had a default value of empty
string set in the role's defaults. However after [1] we do
have such conditionals which make setting the default value
unnecessary - especially when we're asking if the var is
defined - it will be always defined.
Therefore this patch removes the default setting of
tempest_black_regex and tempest_exclude_regex.
The patch also removes 'Set tempest_exclude_regex' task
introduced by [1] as it appears unnecessary as well. This
task simply copied tempest_black_regex value to
tempest_exclude_regex. However there are 2 tasks below which
do the same logic plus more - they build CLI arguments for
tempest where depending on which ansible var is used the
appropriate CLI arg is chosen - tempest_black_regex is set,
--black-regex will be passed to tempest (for backward
compatibility) and if tempest_exclude_regex is set,
--exclude-regex will passed to tempest.
The patch creates a new temporary ansible var which will be used
only internally. The role will store in it the CLI argument
chosen dynamically which is passed to tempest later. Before we
reused the tempest_exclude_regex variable for that, however that
causes problems whent the var is set on a role level as set_fact
won't override such var.
[1] https://review.opendev.org/c/openstack/tempest/+/768583
Change-Id: I3e45741057e7a95b282b03bab4695f46c62d5271
devstack-tempest and devstack-tempest-ipv6 jobs
are base jobs and other Tempest job like tempest-full-py3
or Tempest-ipv6-only are derived from those base job so running
tempest jobs are enough.
We do not need to run base jobs as such.
Change-Id: I2526b3bd5dc0d9a46ed15cefd941a3bbd55e6a49
Devstack depends-on patch enable the way to install the things
in parallel, let's try it in tempest-full-parallel job which
run all the scenario tests in parallel with API tests.
This can help to check the stability of devstack parallel logic
as well as to see how much improvement it add in runtime. If
tempest-full-parallel job run faster then it will be
bigger step to run back the scneario tests in parallel.
Depends-On: https://review.opendev.org/c/openstack/devstack/+/771505
Change-Id: I1da50a89fb7617364249b04efcf207e7728f7de7