yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1130686] Re: Don't log lifecycle events as LOG.ERROR

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Thu, 21 Feb 2013 08:51:47 -0000
Reply-to: Bug 1130686 <1130686@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => grizzly-3

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

Title:
  Don't log lifecycle events as LOG.ERROR

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  Using the most recent Nova Grizzly code (9c9aefc or later) I'm now
  seeing lots of the following log ERROR statements in my Nova
  compute.log file on Fedora:

  2013-02-20 08:59:50.100 15105 ERROR nova.compute.manager [-] Lifecycle event 1 on VM 149e691d-092f-4022-a692-759d418f21b8
  2013-02-20 08:59:58.792 15105 ERROR nova.compute.manager [-] Lifecycle event 1 on VM b9e66fa4-940d-453b-b1db-64501aa0c4de

  ---

  As far as I know we shouldn't be logging lifecycle events to the log
  error channel.

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