Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1965328

Summary: Add VM validation rules so that the web console displays an explanation for a hanging migration plan
Product: Migration Toolkit for Virtualization Reporter: Ilanit Stein <istein>
Component: GeneralAssignee: Sam Lucidi <slucidi>
Status: CLOSED ERRATA QA Contact: Ilanit Stein <istein>
Severity: medium Docs Contact: Avital Pinnick <apinnick>
Priority: medium    
Version: 2.0.0CC: apinnick, fdupont, istein
Target Milestone: ---   
Target Release: 2.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-09 19:20:45 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:

Description Ilanit Stein 2021-05-27 13:22:28 UTC 
Description of problem:
There are cases that the migration plan is pending something and not progressing, without any reason displayed. 
The plan is displayed as "running" and the VMs in the plan are displayed in "Transfer Disk" stage, though this stage was never reached.

The proposed solution is adding a Provider & VM validations.

Provider validations (handled by Bug 1965326):
=============================================
Jeff Ortel: 
"Seems like we should add validations to the provider to:
1. Ensure CNV is installed
2. Ensure the vddk image is installed.
3. …,
The validation (failure) would result in critical conditions which would prevent the provider from being READY which will block migrations.
This seems better than adding a non-VM-specific validation step to the VM pipeline which would result in the same testing being run (over and over) and failing each VM."

This will be handled by:
Bug 1965326 - Add Provider validations to avoid a migration plan running with no progress and no exposed reason

VM validations:
==============
Fabien Dupont: 
I would still keep a VM-specific validation step that verifies that the VM can be migrated. From a visual perspective, it would allow to display a failed state for the individual VM.

This will be handled by this current bug

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

Additional info:
Would be good to include here this validation too, if possible: 
Ensure required storage is available.
CDI importer DataVolume reports "pending" in such a case.
Comment 1 Fabien Dupont 2021-10-07 10:04:11 UTC 
Please verify with build 2.2.0-20 / iib:113682.
The test is that a new "Initialization" step is visible in the UI.
Comment 2 Ilanit Stein 2021-10-11 15:19:24 UTC 
Verified on MTV-2.2.20-20.
The initialization step appears in UI, and in case initialization fails - for example no vddk-init-image set, it will not progress to the next step - Disk copy
Comment 5 errata-xmlrpc 2021-12-09 19:20:45 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 (MTV 2.2.0 Images), 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-2021:5066