Bug 1858548 - [RFE][V2V][RHV to CNV VM import] No error propagating at early stage of import if something goes wrong
Summary: [RFE][V2V][RHV to CNV VM import] No error propagating at early stage of impor...
Keywords:
Status: CLOSED DUPLICATE of bug 1857784
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: V2V
Version: 2.4.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.5.0
Assignee: Piotr Kliczewski
QA Contact: Daniel Gur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-19 06:22 UTC by Igor Braginsky
Modified: 2020-07-27 10:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-27 10:25:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
UI if VM migration went wrong (44.05 KB, image/png)
2020-07-19 06:22 UTC, Igor Braginsky
no flags Details

Description Igor Braginsky 2020-07-19 06:22:16 UTC
Created attachment 1701662 [details]
UI if VM migration went wrong

Description of problem: When migration from RHV to CNV is performed, no error is shown in UI if something went wrong on very beginning of migration process. UI looks like migration is preparing to start and that confuses user. Name of VM is not clickable and user can't validate VM status without digging into the logs


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


How reproducible: 100%


Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ondra Machacek 2020-07-23 08:00:46 UTC
Filip, can you please take a look, why we don't repot any errors in the log?

Igor, can you please share the PV, PVC, DV, VM and VMImport objects and logs? So we know what happens and why it's not shown in the UI, thanks.

Comment 2 Igor Braginsky 2020-07-23 08:24:19 UTC
That env was redeployed several days ago, I will provide you required info if I will succeed reproducing that problem again.
As I understand, in this case problem occurred before the migration process was started itself, that was failure on binding proper PV, but I'm not sure.

Comment 3 Ondra Machacek 2020-07-23 10:22:53 UTC
Ok, thanks in that case, that might be an duplicate of bug 1857784. If you will succeed with reproducing and can confirm it would be great. We just need to add a condition that the PVC can't bind. And show that in UI.

Comment 4 Filip Krepinsky 2020-07-23 11:43:21 UTC
Please always check with VMImport CR. If there is a failed condition then it should be shown in the UI.

I suppose in this case nothing happens in the CR (please confirm with your env), thus UI shows pending only.

Comment 5 Piotr Kliczewski 2020-07-27 10:25:32 UTC

*** This bug has been marked as a duplicate of bug 1857784 ***


Note You need to log in before you can comment on or make changes to this bug.