Gorka Eguileor 9800d58cb3 Log when waiting to acquire lock ... We currently have no log entry when we start trying to acquire a lock. In general this is ok, but there are cases where it can be problematic, for example if we have a deadlock situation or if a lock takes a very long time to be acquired. In those scenarios looking at the logs we would see the operation proceed normally and suddenly go completely silent without knowing that it's waiting for a lock to be freed. This patch adds a debug log message right before trying to acquire the lock so we can detect those situations. Change-Id: I1354dfb98b0927ae167802ecc4ab1d34f6b4d720		2022-07-07 20:01:48 +02:00
..
add_reno-3b4ae0789e9c45b4.yaml	Add reno for releasenotes management	2016-05-20 17:56:23 +03:00
add-option-for-fair-locks-b6d660e97683cec6.yaml	Add support for fair locks	2018-11-02 10:40:23 -06:00
add-python-exec-kwarg-3a7a0c0849f9bb21.yaml	Add python_exec kwarg to processutils.execute()	2018-01-09 10:22:45 -05:00
drop-python27-support-7d837a45dae941bb.yaml	Drop python 2.7 support and testing	2020-01-30 11:37:22 +00:00
log_acquiring_lock-1b224c0b1562ec97.yaml	Log when waiting to acquire lock	2022-07-07 20:01:48 +02:00
timeout-c3fb65acda04c1c7.yaml	Add support for timeout to processutils.execute	2020-06-24 10:53:21 +02:00