Mohammed Naser 730936e535 Use unique consumer_id when doing online data migration ... If there are multiple consumers having allocations to the same resource provider, with different classes, it will attempt multiple INSERTs with the same consumer_id which is not allowed because of the database constraints. This patch adds a simple GROUP BY in order to ensure that the database server only provides us with unique values to avoid trying to INSERT duplicate values. Change-Id: I1acba5e65cd562472f29e354c6077f82844fa87d Closes-Bug: #1798163		2018-10-16 15:30:38 -04:00
..
__init__.py	Move placement test cases from db to placement	2018-03-22 13:27:44 +08:00
test_allocation_candidates.py	Use uuidsentinel from oslo.utils	2018-09-05 09:08:54 -05:00
test_base.py	Use uuidsentinel from oslo.utils	2018-09-05 09:08:54 -05:00
test_consumer.py	Use unique consumer_id when doing online data migration	2018-10-16 15:30:38 -04:00
test_project.py	Use uuidsentinel from oslo.utils	2018-09-05 09:08:54 -05:00
test_reshape.py	Use uuidsentinel from oslo.utils	2018-09-05 09:08:54 -05:00
test_resource_class_cache.py	[placement] Move resource_class_cache into placement hierarchy	2018-08-03 14:55:49 +01:00
test_resource_provider.py	Use uuidsentinel from oslo.utils	2018-09-05 09:08:54 -05:00
test_user.py	Use uuidsentinel from oslo.utils	2018-09-05 09:08:54 -05:00