Bug 1467804 - Issuing multiple concurrent LSM with different disks fails
Issuing multiple concurrent LSM with different disks fails
Status: NEW
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage (Show other bugs)
future
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ovirt-4.2.0
: ---
Assigned To: Benny Zlotnik
Raz Tamir
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-05 04:14 EDT by Benny Zlotnik
Modified: 2017-07-05 04:27 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: ovirt‑4.2+


Attachments (Terms of Use)
A script to reproduce (1.47 KB, text/x-python)
2017-07-05 04:14 EDT, Benny Zlotnik
no flags Details

  None (edit)
Description Benny Zlotnik 2017-07-05 04:14:19 EDT
Created attachment 1294489 [details]
A script to reproduce

Description of problem:
Issuing multiple concurrent LSM with different disks will fail when attempting to remove one of the auto-generated snapshots. It will not be possible to remove the remaining snapshots manually as well after this, as the snapshot was not created properly.

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


How reproducible:
100%

Steps to Reproduce:
1. Create a VM
2. Add 2 disks to the VM and run the VM
3. Issue to move commands using the REST API, an example script is attached

Actual results:
One of the disk will move and have its auto-generated snapshot removed correctly,
The other will move but the removal of its auto-generated snapshot will fail.

Expected results:
Both should succeed

Additional info:
This is not the same issue as https://bugzilla.redhat.com/1460694 in which we move the same disk twice.

This bug is caused by a race condition in the validation stage of the creation of the snapshot.

Note You need to log in before you can comment on or make changes to this bug.