quota_usages table still show instances "in use" after dbaas.api.configuration int tests run

Bug #1381279 reported by Edmond Kotowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Triaged
Low
Unassigned

Bug 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 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.

Revision history for this message
Edmond Kotowski (ekotowski) wrote :

API logs from 2 test runs.

description: updated
description: updated
Changed in trove:
status: New → Incomplete
status: Incomplete → Invalid
status: Invalid → New
status: New → Invalid
status: Invalid → New
Changed in trove:
status: New → Triaged
importance: Undecided → Low
milestone: none → ongoing
Changed in trove:
assignee: nobody → Dan Ritchie (dan-ritchie)
Amrith Kumar (amrith)
Changed in trove:
assignee: Dan Ritchie (dan-ritchie) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.