Bug 1571300

Summary:	VdsNotRespondingTreatment releases VDS_FENCE lock twice
Product:	[oVirt] ovirt-engine	Reporter:	Ravi Nori <rnori>
Component:	BLL.Infra	Assignee:	Ravi Nori <rnori>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Matyáš <pmatyas>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	bugs, lsvaty, lveyde, mperina, rnori
Target Milestone:	ovirt-4.2.3	Flags:	rule-engine: ovirt-4.2+ rule-engine: blocker+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.2.3.4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-10 06:29:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ravi Nori 2018-04-24 13:23:42 UTC

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


How reproducible:


Steps to Reproduce:
1. Have Domain in Up status
2. Shutdown engine
3. Stop vdsm
4. Start engine

Actual results:

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'


Expected results:

VDS_FENCE lock should be release only once

Comment 1 Yaniv Kaul 2018-04-30 07:33:29 UTC

Severity?

Comment 2 Petr Matyáš 2018-05-04 15:25:32 UTC

Verified on ovirt-engine-4.2.3.5-0.1.el7.noarch

Comment 3 Sandro Bonazzola 2018-05-10 06:29:07 UTC

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.