7581e99a05
The volume multiattach tests originally required special devstack configuration in Queens for the Ubuntu Cloud Archive, but that is no longer necessary. This change enables the volume multiattach tests in the tempest-full(-py3) and tempest-slow jobs so we can drop the nova-multiattach job, which is mostly redundant coverage of the tempest.api.compute.* tests, and reduce the total number of jobs we run against nova/cinder/tempest changes. Due to intermittent bug 1807723 when running the test_volume_swap_with_multiattach test with two compute services, that test is conditionally skipped if there is more than one compute. This is probably no great loss in test coverage for now given swapping multiattach volumes is likely rarely used (see bug 1775418). Related ML thread: http://lists.openstack.org/pipermail/openstack-dev/2018-October/135299.html Depends-On: https://review.openstack.org/634977 Change-Id: I522a15ba3dbfee5d8ef417e43288a12319abf6ff
11 lines
513 B
YAML
11 lines
513 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
The ``tempest-full``, ``tempest-full-py3`` and ``tempest-slow`` zuul v3
|
|
job configurations now set ``ENABLE_VOLUME_MULTIATTACH: true`` in the
|
|
``devstack_localrc`` variables section. If you have a plugin job
|
|
configuration that inherits from one of these jobs and the backend cinder
|
|
volume driver or nova compute driver do not support volume multiattach then
|
|
you should override and set this variable to
|
|
``ENABLE_VOLUME_MULTIATTACH: false`` in your job configuration.
|