Bug 1916958

Summary:	Migration plan status in web console does not switch from 'Critical' to 'Ready' after issue is fixed
Product:	Migration Toolkit for Virtualization	Reporter:	Nandini Chandra <nachandr>
Component:	Controller	Assignee:	Jeff Ortel <jortel>
Status:	CLOSED ERRATA	QA Contact:	Igor Braginsky <ibragins>
Severity:	medium	Docs Contact:	Avital Pinnick <apinnick>
Priority:	medium
Version:	2.0.0	CC:	fdupont, istein, jortel
Target Milestone:	---
Target Release:	2.0.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-06-10 17:11:27 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-01-15 23:37:48 UTC

Description of problem:
-----------------------
See https://bugzilla.redhat.com/show_bug.cgi?id=1916954

MTV UI shows that a plan is in 'Critical' state with this message:
Host does not have the Ready condition

After some investigation I found that the host on another VMware provider was not in 'Ready' state.Once I fixed the issue with the host of the other VMware provider, the newly created plans were in 'Ready' state.

The existing plans wouldn't switch from 'Critical' to 'Ready' state.

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


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


Steps to Reproduce:
-------------------
1.Add 2 VMware providers.
2.For VMware provider #1, enter incorrect host credentials so that the host is not in 'Ready' state.
2.Create a migration plan with VMware provider #2 as the source provider.
The migration plan is critical state.
3.Fix issue from step#2 so that the host from VMware provider #1 goes to 'Ready' state.


Actual results:
---------------
Plans don't switch from 'Critical' to 'Ready' state after issue is fixed.


Expected results:
-----------------
Plans should switch from 'Critical' to 'Ready' state after issue is fixed.


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

Comment 1 Jeff Ortel 2021-01-22 17:02:03 UTC

This is a known issue fixed (pull/136) for GA but not included in the BETA per: Fabien Dupont.

https://github.com/konveyor/forklift-controller/pull/136

Comment 2 Fabien Dupont 2021-02-11 12:47:01 UTC

*** Bug 1916954 has been marked as a duplicate of this bug. ***

Comment 6 Nandini Chandra 2021-02-16 21:09:08 UTC

This was moved to ON_QA by Errata Tool. The target release is still 2.0.0, not beta.

Switching it to MODIFIED.

Comment 7 Fabien Dupont 2021-03-31 06:51:53 UTC

This should be part of build 2.0.0-8 / iib:62459.

Comment 8 Jeff Ortel 2021-03-31 15:34:23 UTC

This PR: https://github.com/konveyor/forklift-controller/pull/203 fixes some critical issues related to build 2.0.0-8 / iib:62459.

Comment 9 Igor Braginsky 2021-05-09 18:28:49 UTC

Verified on 2.0.0-12, provider's status is reflected in Plan's status accordingly.

Comment 12 errata-xmlrpc 2021-06-10 17:11:27 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.0.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:2381