After running ./redstack int-tests --group="dbaas.api.configurations" the quota_usages table still show two instances "in use" which eventually causes quota exceeded errors when running integration tests.
Nova list table is empty after run
+----+------+--------+------------+-------------+----------+
| ID | Name | Status | Task State | Power State | Networks |
+----+------+--------+------------+-------------+----------+
+----+------+--------+------------+-------------+----------+
quota_usages table (in_use column) after test run. The in_use values increments after each test run. The current workaround has been manually updating the in_use values back to 0 or ./redstack kick-start.
After running ./redstack int-tests --group= "dbaas. api.configurati ons" the quota_usages table still show two instances "in use" which eventually causes quota exceeded errors when running integration tests.
Nova list table is empty after run -----+- ------- +------ ------+ ------- ------+ ------- ---+ -----+- ------- +------ ------+ ------- ------+ ------- ---+ -----+- ------- +------ ------+ ------- ------+ ------- ---+
+----+-
| ID | Name | Status | Task State | Power State | Networks |
+----+-
+----+-
quota_usages table (in_use column) after test run. The in_use values increments after each test run. The current workaround has been manually updating the in_use values back to 0 or ./redstack kick-start.
| in_use |
+---------
| 1 |
| 1 |
+---------