Bug 1460694

Summary:	It's possible to issue multiple concurrent LSM commands on the same disk
Product:	[oVirt] ovirt-engine	Reporter:	Benny Zlotnik <bzlotnik>
Component:	BLL.Storage	Assignee:	Benny Zlotnik <bzlotnik>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lilach Zitnitski <lzitnits>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	future	CC:	amureini, bugs, ratamir, tnisan
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 10:47:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Benny Zlotnik 2017-06-12 12:20:35 UTC

Description of problem:
As a result of the patch[1], it is possible to issue multiple LSM commands causing the creation of multiple auto-generated snapshots

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Start a move via the REST API
2. Immediately start another

Actual results:
Multiple snapshots are created

Expected results:
The subsequent calls to the move command should fail until the first is finished

Additional info:
1 - https://gerrit.ovirt.org/#/c/77504/

Comment 1 Lilach Zitnitski 2017-07-13 07:02:54 UTC

--------------------------------------
Tested with the following code:
----------------------------------------
ovirt-engine-4.2.0-0.0.master.20170711205308.git8e7af78.el7.centos.noarch
vdsm-4.20.1-176.gitecbab6b.el7.centos.x86_64

Tested with the following scenario:

Steps to Reproduce:
1. Start a move via the REST API
2. Immediately start another

Actual results:
Second move failed to start

Expected results:

Moving to VERIFIED!

Comment 2 Sandro Bonazzola 2017-12-20 10:47:18 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.