Allowing BaseV2ComputeTest based test classes to specify
volume|placement_min_microversion and volume|placement_max_microversion.
Change-Id: If69f0456dc40b923b550bc648caaf0cb1a16e086
Stable branches till stable/rocky is using python
version <py3.6. Tempest test those branch in venv
but Tempest tox use the master upper-constraint[1]
which block installation due to dependencies
require >=py3.6. For exmaple, oslo.concurrency 4.0.0
is not compatible for <py3.6.
As we pin Tempest for EM stable brach, we should be
able to use stable constraint for Tempest installation
as well as while running during run-tempest playbook.
tox.ini is hard coded to use master constraint[1] which force
run-tempest to recreate the tox env and use the master constraint.
Devstack can set stable u-c to use via env var but this is
not enough as Tempest role run-tempest recreate the tox
env with master u-c.
- https://review.opendev.org/#/c/705089/4/lib/tempest
Currently we are fixing run-tempest to use stable constraint
till stable/rocky which use distro having <py3.6.
Ideally, we can change compatible branch constraint in tox.ini
while doing release tag for Tempest. But that can be done
for future tags only.
[1] bc9fe8eca8/tox.ini (L14)
Change-Id: I4268049ff91e5527e4b95fd8a70fa53ba27d56ed
If3ff71dbe636ef98072b15f6599e6e641c222f30 had switched this to python3.6
but this breaks on distros where 3.6 is no longer provided by default,
such as Fedora.
Closes-Bug: #1861308
Change-Id: I0e0b9e88eea2499cb1b9727a7787c050c869c819
Tempest, its plugins and their dependencies in ussuri
cycle are python-requires>=py3.6 which makes distro not
having python 3.6 to do hack to install py3.6 etc.
We cannot do >py3.6 in basepython so one way is to drop the
py3.5 support and basepython to py3 so that it can choose
the available py version in env.
It time to drop the py3.5 from Tempest. Last supported version of
Tempest for py3.5 is 23.0.0.
oslo drop py2 so we need to remove the py2 unit test job which
is failing and blocking gate.
There is seoarate work to drop the py2 things from Tempest in
compplete set.
Change-Id: I872dbb57df46d1193c0d409bb00d56f372d295fe
Related-Bug: 1861308
As per tempest design, if tempest conf is not having any region for
a service then identity region should be used. In case of placement
the default value is "RegionOne" which is considered as placement
region if region missing in tempest conf. In order to have identity
region to be used as default we need to change to empty string for
placement service. Empty string can be seen being used in other
services like volume, image etc.
Please check the below link for the logic of default region
https://github.com/openstack/tempest/blob/master/tempest/config.py#L1435
Change-Id: I2a1045cd0f9eb830493b2b4287ccee46223f3c59
This change adds a specific waiter for tracking the removal of
attachments from a volume. This should allow callers to track the
detaching of multiattached volumes from instances while the volume
remains in an `in-use` state.
Related-bug: #1858841
Change-Id: I85917f683d2bc81fdf3f6d3351bf56fdb649740e
Use of os-tenant-name or OS_TENANT_NAME is deprecated.
Instead of it, os-project-name is expected to be used.
This patch depends on below mentioned patch, since
devstack still uses the deprecated argument.
Depends-on: I624e1dc57a3d3533322fb298c01f70241d0400ed
Signed-off by: Soniya Vyas<svyas@redhat.com>
Change-Id: I3b926f8abb6fce3d2eab93310ce3959c68aa9a6d
The review drops usage of skip_path() filter in the related tests
and uses raw_request() instead.
Normally a swift url is organised as host:port/info and
host:port/v1/AUTH_<tenant-id>, see
https://docs.openstack.org/api-ref/object-store/
But RadosGW API is organised as host:port/swift/info and
host:port/swift/v1/AUTH_<tenant-id>, see
https://docs.ceph.com/docs/master/radosgw/config-ref/#swift-settings
Close-bug: 1799981
Change-Id: I6a932639a05defe0f04c600afcc35a19662937af
This patch removes CONF.compute.volume_device_name dependency and
use modified list_disks method to get the newly attached
device name and use that for mkfs rather than the user supplied
device name which is based on assumtion.
Also modfied test_attach_detach testcase and unit test
for remote_client accordingly.
Change-Id: I862d1ba55f45b09385057a51b0b52a851c19287e
Closes-Bug: #1852807
While OpenStack is in transition to drop py2, many
lib or dependency of Tempest or its plugins cannot
be installed on python 2.7.
To install Tempest on py3 evnv, let's change the basepython
as python 3 for tox env.
Defining basepython as python3.6 for all venv using
.tox/tempest.
Depends-On: https://review.opendev.org/#/c/703476/
Depends-On: https://review.opendev.org/#/c/703679/
Closes-Bug: 1860033
Change-Id: If3ff71dbe636ef98072b15f6599e6e641c222f30
Chipping away at the referenced bug, this commit uses the
create_default_network class-level variable introduced via [1] to
trigger setup_credentials to create a default network for another test
case in which the problem was observed.
[1] Ia34fe3b41261de02918713c2a948e6c56554bf6f
Partial-Bug: #1844568
Change-Id: Ic500aff5adda66328c292c936eaa097253360ea4
Tempest is branchless and support many OpenStack stable branches
and python versions. Users of Tempest should have a clear doc about
what all openstack releases and python versions are supported.
Change-Id: Idc76e07efdd3710a59c773c564ca532419989ed5
Tempest 23.0.0 has been released [1].
This commit adds a new page for 23.0.0 release notes.
[1] https://review.opendev.org/#/c/703521/
Change-Id: If9ffb5c90c427ed3e31e9b6bcb5f6aeca483d110
This relesenote also mark end of support for Queens release
in Tempest as Queens is in EM state[1].
[1] https://releases.openstack.org/
Change-Id: I64bd02b6ccef9e18d9b55f656fe3c224e1aba6d9
Chipping away at the referenced bug, this commit uses the
create_default_network class-level variable introduced via [1] to
trigger setup_credentials to create a default network for
a handful more test cases in which the problem was observed.
[1] Ia34fe3b41261de02918713c2a948e6c56554bf6f
Partial-Bug: #1844568
Change-Id: Ic38c74c245fddf29826e6ca0cc469f919076355e
Chipping away at the referenced bug, this commit introduces a
class-level variable on BaseV2ComputeTest that triggers
setup_credentials to create a default network, and sets it for several
classes where the problem has been observed. The class variable is so we
can whack-a-mole with one line instead of four whenever this problem
pops up.
Change-Id: Ia34fe3b41261de02918713c2a948e6c56554bf6f
Partial-Bug: #1844568
Those tests are related to Nova-Cinder and Nova-Glance interactions
and there is no need to run them on e.g. Neutron gate.
So this patch adds both groups of API tests to be blacklisted in
integrated networking template.
Change-Id: I500b4514f64c89e55d946b5958098511318ea358
