From e32d1ac7a29fa9dd7e84541fbd9f8a0510fc9c16 Mon Sep 17 00:00:00 2001 From: Julia Kreger Date: Thu, 2 Feb 2023 15:50:28 -0800 Subject: [PATCH] Set lockutils default logging While developing some internal metrics collection capability, and the realization that a lock was needed, we realized that the lock activity itself would be a bit noisy. And image actions also get lock logging, and it is just really noisy, but not super helpful for troubleshooting. So, set it to WARNING instead. Discussion wise, see: https://review.opendev.org/c/openstack/ironic-lib/+/865311 Change-Id: I3ab14ee5b5cc063784d26e3c760f1422c692060d --- ironic/conf/opts.py | 3 +++ .../notes/lockutils-default-logging-8c38b8c0ac71043f.yaml | 8 ++++++++ 2 files changed, 11 insertions(+) create mode 100644 releasenotes/notes/lockutils-default-logging-8c38b8c0ac71043f.yaml diff --git a/ironic/conf/opts.py b/ironic/conf/opts.py index fd2e515345..846949893d 100644 --- a/ironic/conf/opts.py +++ b/ironic/conf/opts.py @@ -89,5 +89,8 @@ def update_opt_defaults(): 'openstack=WARNING', # Policy logging is not necessarily useless, but very verbose 'oslo_policy=WARNING', + # Concurrency lock logging is not bad, but exceptionally noisy + # and typically not needed in debugging Ironic itself. + 'oslo_concurrency.lockutils=WARNING', ] ) diff --git a/releasenotes/notes/lockutils-default-logging-8c38b8c0ac71043f.yaml b/releasenotes/notes/lockutils-default-logging-8c38b8c0ac71043f.yaml new file mode 100644 index 0000000000..6ef3fd5467 --- /dev/null +++ b/releasenotes/notes/lockutils-default-logging-8c38b8c0ac71043f.yaml @@ -0,0 +1,8 @@ +--- +other: + - | + The default logging level for the ``oslo_concurrencty.lockutils`` + module logging has been changed to ``WARNING``. By default, the debug + logging was resulting in lots of noise. Operators wishing to view debug + logging for this module can tuilize the ``[DEFAULT]default_log_levels`` + configuration option.