Bug 1916954

Summary: Migration plan in 'Critical' state even when source provider host is in 'Ready' state
Product: Migration Toolkit for Virtualization Reporter: Nandini Chandra <nachandr>
Component: GeneralAssignee: Jeff Ortel <jortel>
Status: CLOSED DUPLICATE QA Contact: Aziza Karol <akarol>
Severity: medium Docs Contact: Avital Pinnick <apinnick>
Priority: high    
Version: 2.0.0CC: 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-02-11 12:47:01 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:
Attachments:
Description Flags
screen shot of plan in critical state
none
screen shot of VMware host none

Description Nandini Chandra 2021-01-15 23:18:35 UTC 
Created attachment 1748026 [details]
screen shot of plan in critical state

Created attachment 1748026 [details]
screen shot of plan in critical state

Description of problem:
-----------------------
Migration plans are in 'Critical' state even when source provider hosts are in 'Ready' state.

See attached screen shots.

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


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


Steps to Reproduce:
-------------------
1.
2.
3.


Actual results:
---------------
Migration plans are in 'Critical' state even when source provider hosts are in not in 'Ready' state.


Expected results:
-----------------


Additional info:
Comment 1 Nandini Chandra 2021-01-15 23:19:58 UTC 
Created attachment 1748027 [details]
screen shot of VMware host
Comment 2 Nandini Chandra 2021-01-15 23:24:48 UTC 
Actual results should read this:

Migration plans are in 'Critical' state even though source provider hosts are in 'Ready' state.
Comment 3 Nandini Chandra 2021-01-15 23:39:12 UTC 
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.I've reported
https://bugzilla.redhat.com/show_bug.cgi?id=1916958 to fix this issue.
Comment 4 Jeff Ortel 2021-01-22 17:03:45 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 5 Fabien Dupont 2021-02-03 09:14:45 UTC 
Can this BZ be closed as duplicate of BZ#1916958 ?
Comment 6 Fabien Dupont 2021-02-11 12:47:01 UTC 

*** This bug has been marked as a duplicate of bug 1916958 ***
Comment 7 Red Hat Bugzilla 2023-09-15 00:58:25 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days