Submitter: Jenkins
Branch:    master

commit 735f710ae0c0e0037970796beacd3527e2a8ca8a
Author: Sean Dague <>
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
    Closes-Bug: #1615676
    Change-Id: I89fe5c5b3d762f3a3238b587685df85d15ee56c4

** 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):
  Fix Released
Status in os-vif:
  In Progress

Bug description:
  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:
Post to     :
Unsubscribe :
More help   :

Reply via email to