yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #65422
[Bug 1701035] Re: Standard traits are not always available in tests
Reviewed: https://review.openstack.org/478564
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ff6c50335e880bc9bd8c4ba81f2323a352bfba70
Submitter: Jenkins
Branch: master
commit ff6c50335e880bc9bd8c4ba81f2323a352bfba70
Author: EdLeafe <ed@xxxxxxxxx>
Date: Wed Jun 28 16:44:08 2017 +0000
Add a reset for traits DB sync
Some functional tests were failing, due to standard traits not being
found. The cause was that there is a flag that ensures that these
standard traits are only loaded once from the os_traits module to the
DB. The test fixtures, though, would clean up the DB between runs, and
the traits would never be re-loaded. This patch fixes that by directly
resetting this flag in the base test code.
Closes-bug: #1701035
Change-Id: I5dc0220310986c5b9fe5b71013c573c3d98cb9aa
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1701035
Title:
Standard traits are not always available in tests
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Several tests use the Database fixture, which cleans up the DB tables
after the tests are run. Some functional tests for traits, though,
were failing because standard traits were not found in the DB. Traits
have a flag so that standard traits from the os_traits library are
only loaded once at startup. So the problem is that one test would use
the fixture, loading the standard traits, and then clean up by
removing the db entries. The next test would use the fixture, but
since the flag had been set by the first test, the standard traits
were not re-loaded, causing failures.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1701035/+subscriptions
References