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: ----------------
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
*** Bug 1916954 has been marked as a duplicate of this bug. ***
This was moved to ON_QA by Errata Tool. The target release is still 2.0.0, not beta. Switching it to MODIFIED.
This should be part of build 2.0.0-8 / iib:62459.
This PR: https://github.com/konveyor/forklift-controller/pull/203 fixes some critical issues related to build 2.0.0-8 / iib:62459.
Verified on 2.0.0-12, provider's status is reflected in Plan's status accordingly.
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