With tempest change [1] the multiattach tests are enabled in tempest-full, tempest-full-py3 and tempest-slow job configurations. This was to allow dropping the nova-multiattach job and still retain test coverage in the upstream gate.

There are 3rd party CI jobs that are basing their job configs on these tempest job configs, and as a result they will now fail if the storage backend driver does not support multiattach volumes and the job configuration does not override and set:

ENABLE_VOLUME_MULTIATTACH: false

in the tempest job config, like was done in the devstack-plugin-ceph-tempest jobs [2].

Let me know if there are any questions.

[1] https://review.openstack.org/#/c/606978/ [2] https://review.openstack.org/#/c/634977/