Description of problem: VdsNotRespondingTreatmentCommand executes SetStoragePoolStatusCommand which releases the VDS_FENCE lock. The lock is again released by VdsNotRespondingTreatmentCommand resulting in warning message in the logs.
Version-Release number of selected component (if applicable): 4.3
Steps to Reproduce:
1. Have Domain in Up status
2. Shutdown engine
3. Stop vdsm
4. Start engine
VDS_FENCE lock is relased twice
2018-04-24 09:07:05,312-04 WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engine-Thread-6) [1435f925] Trying to release exclusive lock which does not exist, lock key: '53cfa6c3-ecd6-4796-84cb-5c53d7c2a77fVDS_FENCE'
VDS_FENCE lock should be release only once
Verified on ovirt-engine-184.108.40.206-0.1.el7.noarch
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.
Since the problem described in this bug report should be
resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.