ed316557e9
It is incorrect to install tempest and manila-tempest-plugin
globally in devstack jobs. So this commit removes the use
of the test plugin's devstack installation hook, and uses
a "tempest-venv" that devstack sets up to run the tests.
To allow zuulv3 style jobs elsewhere [1] use the right
api versions when testing against this stable branch,
we enhance the devstack plugin.sh script to set api
versions as tempest configuration options.
Alongside these changes, we can perform a much needed
test job cleanup by eliminating some jobs we don't have
the bandwidth to maintain:
- manila-tempest-dsvm-postgres-generic-singlebackend
Single backend jobs are not very useful - the job
sets up a single backend in a multibackend style.
We've dropped this from future branches, and we
don't expect this job to catch any regressions that
other jobs will miss.
- manila-tempest-dsvm-generic-no-share-servers
This job's been failing; and wasting CI resources.
We have other DHSS=False reference drivers (CephFS
native/nfs, ZFSOnLinux, LVM) where we test the
driver mode sufficiently.
- manila-tempest-dsvm-glusterfs-nfs-heketi
and manila-tempest-dsvm-glusterfs-native-heketi
these were in the experimental queue, unmaintained
- manila-tempest-dsvm-container-scenario-custom-image
and manila-tempest-dsvm-generic-scenario-custom-image
New zuulv3 style jobs in the manila-image-elements
project replace these jobs [2].
[1] https://review.opendev.org/c/openstack/manila-tempest-plugin/+/725692
[2]
|
||
|---|---|---|
| .. | ||
| grenade-jobs.yaml | ||
| project.yaml | ||