Bug 1293944 - Log common locking management actions
Summary: Log common locking management actions
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.0.0-alpha
: 4.0.0
Assignee: Moti Asayag
QA Contact: Pavol Brilla
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-23 15:53 UTC by Moti Asayag
Modified: 2016-07-26 10:59 UTC (History)
4 users (show)

Fixed In Version: ovirt 4.0.0 alpha1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-26 10:59:49 UTC
oVirt Team: Infra
rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
masayag: devel_ack+
lsvaty: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 51349 0 master MERGED core: Print lock acquire message during command execution 2016-01-05 12:42:32 UTC

Description Moti Asayag 2015-12-23 15:53:25 UTC 
Description of problem:
In certain flows (i.e. acquiring wait-lock in command execution), there is no logging in INFO level to complete the overall tracking after a specific lock.

How reproducible:
always

Steps to Reproduce:
1. Run command which requires wait-lock for its execution scope, i.e. deactivate storage domain.

Actual results:
notice no message in engine.log for the acquired lock.

Expected results:
A message for acquiring lock for the specific storage pool.

Additional info:
See CommandBase.acquireLockAndWait() which unlike CommandBase.acquireLockInternal() doesn't report lock acquire result.
Comment 1 Red Hat Bugzilla Rules Engine 2015-12-23 15:55:24 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 2 Lukas Svaty 2016-07-26 10:59:49 UTC 
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA
Note You need to log in before you can comment on or make changes to this bug.