Red Hat Bugzilla – Bug 1293944
Log common locking management actions
Last modified: 2016-07-26 06:59:49 EDT
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.
Steps to Reproduce:
1. Run command which requires wait-lock for its execution scope, i.e. deactivate storage domain.
notice no message in engine.log for the acquired lock.
A message for acquiring lock for the specific storage pool.
See CommandBase.acquireLockAndWait() which unlike CommandBase.acquireLockInternal() doesn't report lock acquire result.
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.
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