Bug 2057459

Summary: [RHV][Warm] Migration fails during precopy/cutover while a snapshot operation is executed on the source VM
Product: Migration Toolkit for Virtualization Reporter: Maayan Hadasi <mguetta>
Component: GeneralAssignee: Arik <ahadas>
Status: CLOSED MIGRATED QA Contact: Maayan Hadasi <mguetta>
Severity: medium Docs Contact: Richard Hoch <rhoch>
Priority: high    
Version: 2.3.0CC: ahadas, bzlotnik, istein, jortel
Target Milestone: ---   
Target Release: Future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2062575 (view as bug list) Environment:
Last Closed: 2023-01-02 17:37:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2062575    
Attachments:
Description Flags
plan.yaml none

Description Maayan Hadasi 2022-02-23 12:47:03 UTC
Created attachment 1862946 [details]
plan.yaml

Description of problem:
Warm migration fails on the following error in the case that another snapshot operation (create/delete) is executed on the RHV source VM:

Fault reason is "Operation Failed". Fault detail is "[Cannot create Snapshot. The VM is performing an operation on a Snapshot. Please wait for the operation to finish, and try again.]". HTTP response code is "409". HTTP response message is "409 Conflict".


Version-Release number of selected component (if applicable):
MTV 2.3.0-32 / iib:178080
CNV 4.10.0-686 / iib:178572


How reproducible:
100%


Steps to Reproduce:
1. Start a warm migration plan using RHV VM
2. Create a snapshot on the source VM near the next precopy or the cutover time


Actual results:
Migration fails


Expected results:
MTV should wait for the snapshot operation to finish in order to run the next precopy/cutover


Attachments:
plan.yaml

Comment 2 Arik 2023-01-02 17:37:35 UTC
This specific case, in which there is another create-snapshot operation going on, is not that likely/interesting but the migration really shouldn't fail when create-snapshot cannot be triggered (it can also happen, e.g., when the vm is migrated, possibly automatically by RHV)