Bug 1660644

Summary:	Concurrent LSMs of the same disk can be issued via the REST-API
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Gordon Watson <gwatson>
Component:	ovirt-engine	Assignee:	Ahmad Khiet <akhiet>
Status:	CLOSED ERRATA	QA Contact:	Evelina Shames <eshames>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.6	CC:	akhiet, fkust, gveitmic, mtessun, tnisan
Target Milestone:	ovirt-4.4.0	Keywords:	ZStream
Target Release:	4.3.0	Flags:	lsvaty: testing_plan_complete-
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1695018 (view as bug list)		Environment:
Last Closed:	2020-08-04 13:16:51 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:
Bug Depends On:
Bug Blocks:	1695018

Description Gordon Watson 2018-12-18 21:38:16 UTC

Description of problem:

If an LSM of disk is issued via the REST-API, another LSM of the same disk is allowed and will result in;

  - a "Drive image file could not be found" error
  - the volumes existing in both storage domains
  - no live merge being performed


Doing the same with the VM down, the second 'nove' is not allowed, as it checks that the disk is locked.


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

RHV 4.2.6


How reproducible:

Every time.


Steps to Reproduce:
1. Issue LSM of a disk via REST-API.
2. Issue it again.


Actual results:

Concurrent LSMs are allowed.


Expected results:

The second LSM should fail immediately, i.e. should be blocked until the first has completed.


Additional info:

Comment 5 Sandro Bonazzola 2019-01-28 09:43:59 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 8 Daniel Gur 2019-08-28 13:13:06 UTC

sync2jira

Comment 9 Daniel Gur 2019-08-28 13:17:19 UTC

sync2jira

Comment 10 RHEL Program Management 2019-12-13 11:36:41 UTC

The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 11 RHV bug bot 2019-12-13 13:16:14 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 12 RHV bug bot 2019-12-20 17:45:43 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 13 RHV bug bot 2020-01-08 14:47:53 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 14 RHV bug bot 2020-01-08 15:17:52 UTC

WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 16 RHV bug bot 2020-01-24 19:49:39 UTC

WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Found non-acked flags: '{}', ]

For more info please contact: rhv-devops

Comment 24 errata-xmlrpc 2020-08-04 13:16:51 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHSA-2020:3247