Bug 1953255

Summary:	Plan in "Critical" state caused by existing target VM does not move to "Ready" state when problem is fixed
Product:	Migration Toolkit for Virtualization	Reporter:	Nandini Chandra <nachandr>
Component:	Controller	Assignee:	Jeff Ortel <jortel>
Status:	CLOSED ERRATA	QA Contact:	kpunwatk
Severity:	medium	Docs Contact:	Avital Pinnick <apinnick>
Priority:	medium
Version:	2.0.0	CC:	apinnick, fdupont, istein
Target Milestone:	---
Target Release:	2.1.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-08-26 07:09:08 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 Nandini Chandra 2021-04-25 01:51:48 UTC

Description of problem:
------------------------
I noticed that a plan in Critical state because of existing target VM didn't switch to Ready state after target VM was deleted


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


How reproducible:
-----------------
Always


Steps to Reproduce:
-------------------
1.Create a plan with VMs that already exist on the target
2.Plan status shows 'Critical' Target VM already exists.
3.Delete target VMs


Actual results:
---------------
Plan continues to be in 'Critical' state.


Expected results:
-----------------
Plan should switch to 'Ready' state.


Additional info:
----------------

Comment 1 Jeff Ortel 2021-04-27 20:22:15 UTC

Fixed: https://github.com/konveyor/forklift-controller/pull/232.

Comment 2 Fabien Dupont 2021-06-24 21:51:08 UTC

Please test with the mtv-operator-bundle-2.1.0-5 build / iib:85044.

Comment 3 kpunwatk 2021-08-09 10:17:15 UTC

Verified on MTV build 2.1.0-44 IIB 96817.

1.Create a plan with VM that already exist on the target
2.Plan status shows 'Critical' Target VM already exists.
3.Delete target VM 
4.After deleting can see the migration plan in Ready state and also Plan run successfully

Comment 6 errata-xmlrpc 2021-08-26 07:09:08 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 (Migration Toolkit for Virtualization 2.1.0), 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:3278