| 2014-10-15 00:34:59 |
Edmond Kotowski |
bug |
|
|
added bug |
| 2014-10-15 00:39:45 |
Edmond Kotowski |
attachment added |
|
trove-api.log https://bugs.launchpad.net/trove/+bug/1381279/+attachment/4236453/+files/trove-api.log |
|
| 2014-10-15 01:02:19 |
Edmond Kotowski |
description |
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.
| in_use |
+---------
| 1 |
| 1 |
+--------- |
After running ./redstack int-tests --group="dbaas.api.configurations" the quota_usages table still shows the config instance "in use" which eventually causes quota exceeded errors when the value is 5 when running integration tests.
If the configuration tests fail and does not make it to the test test_delete_configuration_instance then a the config instance will never be cleaned up.
Nova list will show the _config instance:
| TEST_2014-10-14 17:05:17.452594_config | ACTIVE | Running |
Fix would be to add a test tear down that will clean up the _config instance even if an error or exception gets raised in the test class. |
|
| 2014-10-15 01:02:39 |
Edmond Kotowski |
description |
After running ./redstack int-tests --group="dbaas.api.configurations" the quota_usages table still shows the config instance "in use" which eventually causes quota exceeded errors when the value is 5 when running integration tests.
If the configuration tests fail and does not make it to the test test_delete_configuration_instance then a the config instance will never be cleaned up.
Nova list will show the _config instance:
| TEST_2014-10-14 17:05:17.452594_config | ACTIVE | Running |
Fix would be to add a test tear down that will clean up the _config instance even if an error or exception gets raised in the test class. |
After running ./redstack int-tests --group="dbaas.api.configurations" the quota_usages table still shows the config instance "in use" which eventually causes quota exceeded errors when the value is 5 when running integration tests.
If the configuration tests fail and does not make it to the test test_delete_configuration_instance then the config instance will never be cleaned up.
Nova list will show the _config instance:
| TEST_2014-10-14 17:05:17.452594_config | ACTIVE | Running |
Fix would be to add a test tear down that will clean up the _config instance even if an error or exception gets raised in the test class. |
|
| 2014-12-12 22:56:04 |
Edmond Kotowski |
trove: status |
New |
Incomplete |
|
| 2014-12-12 22:56:11 |
Edmond Kotowski |
trove: status |
Incomplete |
Invalid |
|
| 2014-12-12 22:56:29 |
Edmond Kotowski |
trove: status |
Invalid |
New |
|
| 2014-12-12 22:56:54 |
Edmond Kotowski |
trove: status |
New |
Invalid |
|
| 2014-12-12 22:57:00 |
Edmond Kotowski |
trove: status |
Invalid |
New |
|
| 2015-02-03 09:30:33 |
Nikhil Manchanda |
trove: status |
New |
Triaged |
|
| 2015-02-03 09:30:36 |
Nikhil Manchanda |
trove: importance |
Undecided |
Low |
|
| 2015-02-03 09:30:39 |
Nikhil Manchanda |
trove: milestone |
|
ongoing |
|
| 2015-02-07 00:45:04 |
Edmond Kotowski |
trove: assignee |
|
Dan Ritchie (dan-ritchie) |
|
| 2016-04-05 12:23:10 |
Amrith Kumar |
trove: assignee |
Dan Ritchie (dan-ritchie) |
|
|
