yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1161031] Re: Logging configured incorrectly

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Sean Dague <sean@xxxxxxxxx>
Date: Fri, 19 Sep 2014 11:07:43 -0000
Reply-to: Bug 1161031 <1161031@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** No longer affects: nova/grizzly

-- 
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/1161031

Title:
  Logging configured incorrectly

Status in OpenStack Compute (Nova):
  Fix Released
Status in The Oslo library incubator:
  Fix Released

Bug description:
  To allow users to provide logging configuration options, the setup
  must be run before it gets the logger to ensure it does not always
  just default to the root logger.

  So this order is important- 
      logging.setup('nova')
     LOG = logging.getLogger('nova.all')

  Some of the nova components are configuring logging incorrectly by reversing the order-
      LOG = logging.getLogger('nova.all')
      logging.setup('nova')

  
  Here are the nova components that need the order fixed to support this: 
  - nova-all
  - nova-compute
  - nova-dhcpbridge
  - nova-baremetal-deploy-helper

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1161031/+subscriptions