[placement] Flush RC_CACHE after each gabbit sequence
Each gabbi yaml file is supposed to be an isolated sequence. The
fixtures were already making sure that the database was wiped, and the
traits sync was reset, but not making sure the _RC_CACHE used to cache
mappings between resource class strings and ids was flushed.
This change clears the _RC_CACHE in the APIFixture stop_fixture method.
For sake of information:
Before fixing the issue it was confirmed by running the two gabbi files
indicated in the bug report, in sequence, in a single process:
Reviewed: https:/ /review. openstack. org/486805 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=997ba030940 62799349e827502 6462c549d3989a
Committed: https:/
Submitter: Jenkins
Branch: master
commit 997ba0309406279 9349e8275026462 c549d3989a
Author: Chris Dent <email address hidden>
Date: Tue Jul 25 01:59:52 2017 +0100
[placement] Flush RC_CACHE after each gabbit sequence
Each gabbi yaml file is supposed to be an isolated sequence. The
fixtures were already making sure that the database was wiped, and the
traits sync was reset, but not making sure the _RC_CACHE used to cache
mappings between resource class strings and ids was flushed.
This change clears the _RC_CACHE in the APIFixture stop_fixture method.
For sake of information:
Before fixing the issue it was confirmed by running the two gabbi files
indicated in the bug report, in sequence, in a single process:
Where runthese contains (with fully qualified package name prefixes):
test_ placement_ api.allocation- bad-class_ allocate_ some_of_ it_standard. test_request placement_ api.resource- class-in- use_delete_ resource_ class.test_ request
test_
Change-Id: Icb3beef7964887 f29bf8cca95ac7d bae1511876d
Closes-Bug: #1706207