This adds an initial test for glance image interoperable import
that uses the glance-direct method. It will skip if the server
does not support glance-direct.
Adding feature flag to enable the import tests as devstack on
stable branches cannot support image import feature.
Change-Id: I09e7fb4e7758edd5256ae70ceeea6f143466c3e3
Replace legacy-tempest-dsvm-lvm-multibackend with its native version,
cinder-tempest-lvm-multibackend.
Remove legacy-tempest-dsvm-neutron-dvr-multinode-full, which was defined
as an experimental job in neutron and removed during the ussuri lifecycle.
See https://review.opendev.org/#/c/693630/
It seems neutron-tempest-dvr-ha-multinode-full should cover its use case.
Change-Id: I6edfd00f0c43cd0bfe688db5e43768288dd4c1c1
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
Currently ceph job is n-v, if I remember
correctly it was kept n-v due to its stability.
But it is stable and voting on many projects. With
n-v it is hard to monitor it all the time.
let's make it voting and if any new tests failing we
can add that in the ceph blacklist in advance.
Example: https://review.opendev.org/#/c/724866/
Change-Id: Ic484d233b325c887f0a19f3ec06376d403beb964
'grenade' is zuulv3 native job for py3 (because devstack is default to
py3 since Ussuri) which replace the old 'grenade-py3'
legacy job. 'grenade-py3' job is alias to the new zuulv3 native
'grenade' job but that is only for migration time. Later once
all switch to new job name, we will remvoe the 'grenade-py3' alias
job.
Change-Id: Iea355514ec7cc2a52ed5e88c356bcb1cdeadd639
Now we have stable/ussuri branch ready for devstack
and so does for all service projects.
This commit adds the Tempest testing for stable/ussuri
by adding new jobs running on stable/ussuri version of
openstack.
Depends-On: https://review.opendev.org/#/c/723605/
Change-Id: Ifa7887675d34ab8169347b69a8e1ff723b55e466
tempest-multinode-full is python2 version
of mutlinode testing for stable branches and
supposed to run on python 2 but it was left during
- I75868d5c9b6630fe78958ff89e58a0aced09a6b3
Change-Id: Ibec72b578424cb278006ac810bdd0359ec23de3f
devstack-plugin-ceph-tempest is py2 job and not
supposed to run on master gate. Moving
devstack-plugin-ceph-tempest-py3 from experimental pipeline
to check.
Change-Id: I8a15d919f9902315c4a8d27d73dabbcc5be8d8de
I saw in Neutron queue that default 2h timeout for this job wasn't
enough sometimes. So it's better to keep this job running a bit longer
sometimes rather than recheck everything.
Change-Id: I7c256f1ca5790cd13411d3af78ec97efcfd28b0a
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
This fixes used python version on subnodes in jobs like
tempest-slow-py3 and tempest-multinode-full-py3
Change-Id: I851d2dbcb863f0e21e6cbcbb6b856ce1f3d3f092
Closes-Bug: #1853004
This job is still running python 2.7. As we are dropping py2 support in
Ussuri cycle, lets drop this job now.
There is same job called "grenade-py3" which runs on python 3 already
and this is still used in project's CI.
Change-Id: I6a4ce001d6cbb4455386285c0d0a43be592e57d7
Cinder backup tests suffer from a high failure rate and
given they do not interact with many other services (glance
and swift for the most part it looks like) we should disable
them from running in the tempest-full job which is part of
the integrated-gate project template, which is what this change
does.
My recommendation would be to make sure cinder backup test
coverage is happening in some other non-integrated-gate jobs
which are running on cinder changes already, like the
cinder-tempest-dsvm-lvm-lio-barbican job (which is voting but
not gating on cinder changes).
This should also help with bug 1783405 where tempest-full
can timeout due to backup tests which aren't marked slow.
c-bak was already disabled in tempest-full-py3 because
swift is disabled but this copies the same note to the
tempest-full-py3 job definition.
Change-Id: I9d39d9d7d706ba3fcba5ff352e8c9e31ab4639a2
Related-Bug: #1483434
Related-Bug: #1745168
Related-Bug: #1783405
Related-Bug: #1813217
Now we have stable/train branch ready for devstack
and so does for all service projects.
This commit adds the Tempest testing for stable/train
by adding new jobs running on stable/train version of
openstack.
Change-Id: I0ea8008ad0ef18b9e45c41f9ba40a70fd6d57b6a
This commit sets the tempest-irrelevant-files-2 for the bashate job. We
just need to run the job when we change bash scripts. Currently, bash
scripts are located in the tools/ directory only. So,
"tempest-irrelevant-files-2" is better than "tempest-irrelevant-files".
Change-Id: I0f55ffaa844736056769f1fbeca82fc0cb0a9a86
opensuse-150 nodeset is referring to openSUSE 15.0, which is still in
maintenance but openSUSE 15.1 has been released already. "opensuse-15"
is going to refer to the "latest openSUSE 15.x" build released and
working for OpenStack going forward, so add this nodeset and use
it by default going forward.
This is the remaining work to be done after https://review.opendev.org/#/c/667539
got merged earlier
Change-Id: I3c0e14c606c88b5deecfad71bc156e53335d543e
This commit adds 4 irrelevant files to both "irrelevant-files" and
"irrelevant-files-2". We don't need to run tempest tests with updating
such files because they don't affect tempest tests.
Change-Id: I6f84abc1b9273f38b99678edaff54deb0fd99e0c
This commit removes required projects for the sanity job. It should be
better to remove them since we don't need for sanity checking.
Change-Id: Iad2f9f3d08aa1a422a6a94cd56467a16f683fa3b
This commit introduces bashate[0] which is a code style checker for bash
scripts. We already have some bash scripts in Tempest repo. So, it might
be good to check the style automatically.
Some scripts under the tools directory are also fixed due to the bashate
violation.
Change-Id: I07820f10387552f93a9d8891b58a8c7fcdb83046
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
Using memcached based cache for metadata api to cache data for
instance always after firts metadata request is send can solve
problems with unable to ssh to instance due to not configured
public-key on instance.
In Nova metadata api service data related to one instance should
be cached after it is collected first time. So e.g. CirrOS based
image first sends request to get instance-id and next request is
to get public-key.
If those two requests will be processed by 2 different workers on
Nova's side, it will collect all data for instance twice. And if
this will take more than 10 seconds in case of request to get
public-keys, CirrOS script will fail and not configure public-key
on guest VM.
Using memcached based script will make this cached data available
for each worker so it will be cached always during processing
instance-id request. And this request for instance-id is retried
by CirrOS image in case of failure so this shoudn't cause problems.
Change-Id: I8efedb8c5ae073bd2cb4034369bfcff4b67eb868
Closes-bug: #1836642
Closes-bug: #1808010
This commit removes duplicated irrelevant-files for sanity-check in the
job definition. We have the same entries in the later. So we can remove
the redundancy.
Change-Id: I11e2054758fb9d4292e7cc64b58017c3e462c939
This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train.
See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html
Note: This diverges from the Train goal as it does not drop the
openstack-python35-jobs. As tempest is branchless it needs to continue
supporting Python 3.5.
Change-Id: Ie702ca637afb8229b6e605abcec25550bc9a0673
Story: #2005924
Task: #34240
tempest-full job run all services API and scenario tests (non slow)
and this job is part of Integrated-gate gate template which run on
multiple services (nova, neutron, cinder, glance, placement) check
and gate pipeline.
But there are many unrelated tests run on each project gate. For example,
neutron gate run cinder only tests and fail due to cinder bugs. There is
no point of breaking the neutron gate due to cinder only test failure and
slow down the neutron development phase.
This is what we dicussed in Train PTG in denver to improve the integrated
gate[1] and came up with idea of split the integated-gate template into
much logical way so that only dependent services tests run on their gate.
One way was to move the service only tests to service tempest plugin side
but Tempest is used by interop as well as on production cloud testing so
moving the test is not good idea.
This commit propose the idea of defining the 'Integrated-gate-object-storage'
gate template for swift gate which will run only Swift, Cinder and glance tests.
ML discussion: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005871.html
Next step will be to replace the Integrated-gate-py3 template with new
Integrated-gate-object-storage template on swift gate.
[1] https://etherpad.openstack.org/p/qa-train-ptg
Change-Id: I70851d41174462b83cc8c525cecdb1b3d65e4ec7
tempest-full job run all services API and scenario tests (non slow)
and this job is part of Integrated-gate gate template which run on
multiple services (nova, neutron, cinder, glance, placement) check
and gate pipeline.
But there are many unrelated tests run on each project gate. For example,
neutron gate run cinder only tests and fail due to cinder bugs. There is
no point of breaking the neutron gate due to cinder only test failure and
slow down the neutron development phase.
This is what we dicussed in Train PTG in denver to improve the integrated
gate[1] and came up with idea of split the integated-gate template into
much logical way so that only dependent services tests run on their gate.
One way was to move the service only tests to service tempest plugin side
but Tempest is used by interop as well as on production cloud testing so
moving the test is not good idea.
This commit propose the idea of defining the 'Integrated-gate-compute'
gate template for nova gate which will run only nova, neutron, cinder
and glance tests.
ML discussion: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005871.html
Next step will be to replace the Integrated-gate-py3 template with new
Integrated-gate-compute template on nova gate.
It will also help to disable the non-nova related serviecs and tests which
cannot be disabled from tempest-full job.
[1] https://etherpad.openstack.org/p/qa-train-ptg
Change-Id: I807d4cac6214395df292a6955686ea44677c3481
