+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1660644 +++ ====================================================================== 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: (Originally by Gordon Watson)
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. (Originally by Sandro Bonazzola)
Tested on: ovirt-engine-4.3.4.1-0.1.el7.noarch vdsm-4.30.16-3.el7ev.x86_64 The 2nd LSM (during the 1st one) fails as expected. A new bug has been opened [1] as there was a side effect that causes the disk to be unable to move after the failure. This happens when I try the 2nd LSM when the "RemoveSnapshotCommand" appears in the engine log. If I try the 2nd LSM at this point, I get an "Internal Engine Error" and the disk gets stuck (The status is OK but can be moved). All further tries fails with "Cannot move Virtual Disk. Disk ${DiskName} is being moved or copied". [1] https://bugzilla.redhat.com/show_bug.cgi?id=1715478 Moving to VERIFIED as the main issue in this bug works fine.
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, 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/RHEA-2019:1566
sync2jira