Author: Sean Dague <s...@dague.net>
Date: Wed Sep 21 11:11:21 2016 -0400
move os_vif.initialize() to nova-compute start
os_vif.initialize() was previously executed during module load. This
means it was entirely possible that it was run before things like
logging were actually set up in the expected way. Move this back into
execution time instead of load time to ensure that logging is actually
Changes need to be made to tests which make assumptions about os_vif
objects to manually initialize os_vif when it will be used. os_vif
objects can't be created until it is initialized, so some delayed
object creation is also done in test_vif.py.
** 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).
os-vif log messages corrupt and pollute test output
Status in OpenStack Compute (nova):
Status in os-vif:
When running unit tests with tox, os-vif logging pollutes the output
of the testr runner and on multi-core machines, nearly always corrupts
the output stream like so:
os-vif logging setup should be examined to ensure it is being
processed like all other modules that behave properly with testr.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp