We need to move 'gabbi_tempest_path' var to gabbi-tempest plugin jobs side
which is the only place it is being used. This var is specific to gabbi-tempest
not used for any other devstack-tempest jobs so defining it in devstack-tempest
base job is not the correct way. We might face issue like bug#1821072 again in
future which can end up blocking all gate jobs.
Below patch is moving this var to gabbi-tempest plugin.
- https://review.opendev.org/#/c/705339/
Change-Id: Id96e9b3f1271fce50aae982fdf12871693107e1d
Closes-Bug: #1861592
The patch implements a new flag which will fail a job when any
resources were leaked - that can be used for verification that
tests are cleaning their resources after they are finished.
Change-Id: I212cdce9713c80491153b0bbdb313e75c1f96f1d
The patch adds a new ansible role called tempest-cleanup which will
allow us to test tempest cleanup in the gate jobs.
Change-Id: I2cef2da6fee13e622da07b890da88850fe420152
Devstack IPv6 base job 'devstack-IPv6' setup the IPv6 setting
to deploy the services to listen on IPv6 address.
Tempest 'devstack-tempest-ipv6' job derived from 'devstack-IPv6'
job adds the playbooks to run the tests.
As part of Train community goal 'Support IPv6-Only Deployments',
we will expand the 'devstack-tempest-ipv6' job to do
IPv6-only deployments verification.
This commit define the new roles of 'ipv6-only-deployments-verification'
which will be invoked as part of run phase of 'devstack-tempest-ipv6' job.
This role will do IPv6-only setting and deployments verification via
tools/verify-ipv6-only-deployement.sh
IPv6 verification script can be extended further to perform more checks
and via project specific test case. Those tests will run as part of project
specific child jobs.
The 'devstack-tempest-ipv6' job will be used as parent for project specific
IPv6-only job. Those child job can extend the project specific IPv6 verification
by defining new playebook for post-run. That way the base verification
done in 'devstack-tempest-ipv6' will still run in addition to project specific
verificaiton and tests run.
Verification structure will be:
- 'devstack-IPv6' deploy the service on IPv6
- 'devstack-tempest-ipv6' run will verify the IPv6-only setting and listen address
- Child jobs derived from 'devstack-tempest-ipv6' will run the IPv6 related test case or
any further IPv6 deployment verification.
This commit also adds the new job 'tempest-ipv6-only' which will run smoke
and ipv6 related tests present in Tempest. This job will be used to run
on 6 services (Nova, Neutron, Cinder, Keystone, Glance, Swift) deployed
by devstack.
Story: #2005477
Task: #35923
Change-Id: Ie1e5e5e02ee45ab7a4aae0f35bdb42afc2c3fe2e
Seems this variable is setup from gabbi-tempest, but other jobs also use
devstack-tempest.
Change-Id: I45c582d9d9b34a1c5ab75455e42077902cbb850e
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
The gabbi-tempest plugin uses an environment variable,
GABBI_TEMPEST_PATH, to identify directories in which to
find the gabbi [1] tests that will be run. This will be
used by a forthcoming zuul job [2] (hosted by the plugin)
that will automate gabbi-based service testing as described
in https://anticdent.org/gabbi-in-the-gate.html .
By setting the environment in the devstack-tempest playbook
we avoid needing to duplicate the playbook: we can use
it directly and have less risk of plays diverging. The
calling job (which doesn't allow the "environment" key)
sets a "var" which then sets the environment variable.
[1] https://gabbi.readthedocs.io
[2] https://review.openstack.org/611678
Needed-By: https://review.openstack.org/611678
Change-Id: I5aa890baa489f434b95d21e4e618f5202ac550e4
This patchset ports tempest-scenario-all to zuul v3.
The current job setup is the same as the legacy job setup,
except that the current job setup uses dynamic credentials
whereas the legacy setup used pre-provisioned credentials [0].
[0] 67081bf4d5/playbooks/tempest-scenario-multinode-lvm-multibackend/run.yaml (L34)
Change-Id: Icb2708686cf204a4a4b29ed23e7efa09f14455a5
'tempest-scenario-multinode-lvm-multibackend' job used to run
- all scenario test including slow tests with lvm multi-backend setup
- live migration and migration tests
This commit make scenario job only run the scenario tests and exclude
migration and live migration tests out of it.
coverage of those tests are there in below jobs
- migration tests run as part of - 'neutron-tempest-multinode-full'
- live migration tests run as part of - 'nova-live-migration'
This helps to provide a generic job to run the scenario tests in parallel
including slow tests so that project like nova, cinder, neutron etc can
use this job ti run on their main pipeline.
- http://lists.openstack.org/pipermail/openstack-dev/2018-May/130418.html
Change-Id: Ibddd633a3fdccb11100f5bc150c4595147402237
Rewrite the base tempest multinode job as zuulv3.
The job is currently hosted in the neutron repo as
neutron-tempest-multinode-full.
Full job name history:
* neutron-tempest-multinode-full
* legacy-tempest-dsvm-neutron-multinode-full
* gate-tempest-dsvm-neutron-multinode-full-ubuntu-xenial-nv
With this patch, devstack-tempest can be used as a basis for both
single and multinode jobs.
Depends-on: https://review.openstack.org/561187
Depends-on: https://review.openstack.org/561251
Depends-on: https://review.openstack.org/564220
Depends-on: https://review.openstack.org/572313
Change-Id: If448ae20bca6e221b4a10646c69ba014656438ad
"legacy-tempest-dsvm-neutron-scenario-multinode-lvm-multibackend" job
is tempest job which run all scenario tests including slow tests
and migration tests as non voting job.
This commit migrate this job to tempest in-tree and later we can
modify this to zuulv3 native.
This is first step to make slow tests running on tempest as voting
and on project side also.
Details- http://lists.openstack.org/pipermail/openstack-dev/2018-May/130418.html
Change-Id: I6bc7503347ca2f110e4a0a5b404e612168b3a417
Currently there is a zuul-jobs role only used in this tempest job while
other jobs mostly use fetch-subunit-output role.
This changes tries to consolidate towards the most used role, to be able
to clean up zuul-jobs a bit.
Change-Id: I404760ba34767660f8816f48712e13dccad67440
Depends-On: https://review.openstack.org/548406
stage-output is already invoked in the devstack job.
Rather than running the role again in Tempest post, extend the
list of files to be staged and extensions to be converted to txt.
Change-Id: I0844700f1c770809cba5a2e0e39737fd6827896f
Depends-on: https://review.openstack.org/540485/
Stage dir used to be /opt/stack but now devstack changed to
use ansible user dir as a stage dir (which is the default
value) so the override is not needed anymore.
Change-Id: Id531271da326413c5a88947d9a8b3ac4da68c47d
Use the process-test-results role from zuul-jobs to generate the
subunit file and html report.
Depends-on: Id6149d4e265ab9f0ab6d8faeffdec651c63dc056
Change-Id: Ib8a43a7d6e4afdca6b2e30d3e7be58b1ac771436
Stage three tempest conf and log files for archival using the
stage-output role.
Depends-on: Id45a50821539985710da7172a9185fd91e803603
Change-Id: Id67dbf3df5af52e848b8d378bc13aaa1c02cdd29
Setup the initial folder and play to run tempest.
This simply runs tempest full for now, with not support for config
options.
Change-Id: I5a76dd23900a1b5fb1764fafd837d69baf9ed8b1
Depends-on: Iffe54fbccbccd68db08f79a1b51dd7f76dbff408
Ghanshyam