manila/manila_tempest_tests
Valeriy Ponomaryov 7ba41320f3 Fix 'project_share_type_quotas' DB table unique constraint
It should be possible to use share type quotas in each project/tenant.
But we get error trying to set share types quota in second+ project
for the same share type. It happens so due to the bug in DB schema,
where we don't have 'project_id' in unique constraint.
So, add new DB migration that fixes unique constraint and cover it with
DB and tempest tests.

Change-Id: I1405ced4e12b40904b7227c9f6285e2775005f8a
Closes-Bug: #1722707
2017-10-14 23:22:10 +03:00
..
common Enable some off-by-default checks 2017-08-03 16:13:32 +08:00
services Use tempest-plugin service client registration 2017-07-31 20:41:06 +01:00
tests Fix 'project_share_type_quotas' DB table unique constraint 2017-10-14 23:22:10 +03:00
__init__.py Use Tempest plugin interface 2015-09-05 00:36:33 +00:00
clients.py Use tempest-plugin service client registration 2017-07-31 20:41:06 +01:00
config.py Add share groups and share group snapshots quotas 2017-07-26 11:32:43 +03:00
plugin.py Use tempest-plugin service client registration 2017-07-31 20:41:06 +01:00
README.rst Use Tempest plugin interface 2015-09-05 00:36:33 +00:00
share_exceptions.py [Tempest] Add functional tests for share groups feature 2017-01-23 19:30:33 +00:00
utils.py Enable IPv6 in manila(allow access) 2017-07-17 09:44:41 +08:00

Tempest Integration

This directory contains Tempest tests to cover Manila project.