Stop logging unnecessary warning on context create
The context was previously logging at the 'warn' level when unknown
kwargs were being passed to its __init__(). Since the agents were
passing tenant=None with each rpc request, this was generating an
unreasonable amount of log chatter that would not be useful to an
operator. The fix is to log at the debug level instead so that
the operators don't see the output by default but developers can
still choose to.
Reviewed: https:/ /review. openstack. org/58692 github. com/openstack/ neutron/ commit/ 5b61df1f539d78c f9d164a142d731e 471aa18d4e
Committed: http://
Submitter: Jenkins
Branch: master
commit 5b61df1f539d78c f9d164a142d731e 471aa18d4e
Author: Maru Newby <email address hidden>
Date: Wed Nov 27 07:57:48 2013 +0000
Stop logging unnecessary warning on context create
The context was previously logging at the 'warn' level when unknown
kwargs were being passed to its __init__(). Since the agents were
passing tenant=None with each rpc request, this was generating an
unreasonable amount of log chatter that would not be useful to an
operator. The fix is to log at the debug level instead so that
the operators don't see the output by default but developers can
still choose to.
Change-Id: I5c328f628c597e b949c1fe67b2312 0d2b5d1c7da
Related-Bug: #1254530
Partial-Bug: #1255441