Bug 1696421

New commits detected on ManageIQ/manageiq-v2v/hammer:

https://github.com/ManageIQ/manageiq-v2v/commit/1592bbac430fa8c9d2689ae7a7e0c702ac93b18a
commit 1592bbac430fa8c9d2689ae7a7e0c702ac93b18a
Author:     Mike Turley <mike.turley.umass.edu>
AuthorDate: Wed Apr  3 10:50:03 2019 -0400
Commit:     Mike Turley <mike.turley.umass.edu>
CommitDate: Wed Apr  3 10:50:03 2019 -0400

    Merge pull request #923 from mzazrivec/fix_error_on_in_progress_plans_with_deleted_target_provider

    Migration Plans in Progress page: fix error with deleted target provider

    (cherry picked from commit 8ce214d251b8cb5070b85b85bf6d203cad23ea16)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1696421

 app/javascript/react/screens/App/Overview/components/Migrations/MigrationsInProgressCard.js | 3 +-
 app/javascript/react/screens/App/Overview/helpers.js | 3 +
 2 files changed, 5 insertions(+), 1 deletion(-)

Just FYI , Seeing this issue on 5.10.3 without removing provider .
I hope the PR includes fix for that too .
Not sure what the exact steps are , just created one migration plan which failed .
and navigated to Migration plan page again and it started showing blank.
Can be seen at https://10.16.5.85 .

If you can point me to where exactly can I find the logs for such failure . I will download it and attach.

If the steps are not the same, I'm not sure it's the same bug... To be confirmed.
Mike can you take a look at the appliance, please ?

I rebooted that appliance and the blank page was gone.
New appliance : https://10.8.198.51

Shveta, I'm not able to reproduce the problem on either one of those appliances. Can we get an appliance into the state where the problem is presenting, and then leave it there? I'd like to capture a copy of the manageiq database while it's in that state.

It would also be helpful if you could capture any error messages that appear in the browser's JavaScript console when the page goes blank. (https://webmasters.stackexchange.com/a/77337)

Can you try one more time on 
https://10.8.198.51.

Attaching console error screenshot .
Error is same

Created attachment 1552683 [details]
error

Strangely, I can't reproduce it on that appliance now either, but yes, this is indeed the same error we are handling in the PR above, so it should no longer crash the UI.

I'm still not sure of the underlying problem which causes the target cluster not to be able to be found, especially if it's inconsistent/sporadic like this. My guess is that whatever caused that will also cause the migration to fail, and more details will be evident in the logs. The error is now handled gracefully by the UI, so we shouldn't get any more blank pages.

Fixed .
Verified in 5.10.3.1.20190408182335_d0fa1a0

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, 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/RHSA-2019:0796