Internal lock release not logged when using lockutils.lock
Bug #1312813 reported by
Salvatore Orlando
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| oslo-incubator |
Fix Released
|
Low
|
Salvatore Orlando | ||
Bug Description
When using the synchronized decorator, the release of the lock is logged in the finally block:
https:/
However, when using directly lockutils.lock, no release message is printed.
Adding a release message might be useful for debug purposes.
Revision history for this message
| Openstack Gerrit (openstack-gerrit) wrote Fix merged to oslo-incubator (master) | #1 |
| Changed in oslo: | |
| status: | New → Fix Committed |
| Changed in oslo: | |
| assignee: | nobody → Salvatore Orlando (salvatore-orlando) |
| importance: | Undecided → Low |
| Changed in oslo: | |
| milestone: | none → juno-1 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 0f495ee138ad33b
Author: Salvatore Orlando <email address hidden>
Date: Fri Apr 25 08:56:59 2014 -0700
Emit a log statement when releasing internal lock
The log statement, with debug severity, is added to the lock
function in order to ensure lock release is logged also when
using lockutils.lock
Change-Id: I362cc743f49ddb
Closes-Bug: 1312813