openstack.common.log gives a mechanism to configure logging and, by
default, we will set up a handler on root logger. Using pecan to also
configure a handler on the 'ironic' logger means every log message gets
logged to console twice.
It seems that the pecan logging configuration stuff is redundant with
our existing logging configuration infrastructure.
Change-Id: Iec0630b0e842e3b6a90021bf552d9b857c5a0552
(cherry picked from commit e6a083fc5acb6f3ad03cc1df0943e4e746629128)
Reviewed: https:/ /review. openstack. org/31196 github. com/openstack/ ceilometer/ commit/ ff94b0e6ed99469 fec6830b0fb5c0a a3ee667195
Committed: http://
Submitter: Jenkins
Branch: stable/grizzly
commit ff94b0e6ed99469 fec6830b0fb5c0a a3ee667195
Author: Mark McLoughlin <email address hidden>
Date: Tue May 28 11:18:13 2013 +0100
Don't use pecan to configure logging
Fixes bug #1184941
openstack. common. log gives a mechanism to configure logging and, by
default, we will set up a handler on root logger. Using pecan to also
configure a handler on the 'ironic' logger means every log message gets
logged to console twice.
It seems that the pecan logging configuration stuff is redundant with
our existing logging configuration infrastructure.
Change-Id: Iec0630b0e842e3 b6a90021bf552d9 b857c5a0552 ad03cc1df0943e4 e746629128)
(cherry picked from commit e6a083fc5acb6f3