Description of problem: When importing VM by virt-v2v (either from OVA or via export-domain) that has no Origin specified the import dialog shows correctly 'Origin' as 'N/A'. But after import is finished the VM has it's origin specified as 'RHV'. That is because there is no special value for 'N/A' in the engine code. Version-Release number of selected component (if applicable): oVirt 4.1.2 How reproducible: 100% Steps to Reproduce: 1. Import VM disk image to export domain using: virt-v2v -i disk -o rhev ... 2. Import the VM from export domain Actual results: Origin shows 'RHV' Expected results: Origin should be 'N/A' or something more appropriate.
The reason that the origin is RHV is that in case the origin is not set, engine looks the value up from engine config (key: OriginType). The actually correct solution would be to enrich the OriginType enum by the N/A option and explicitly pass this one from frontend to store it. But this is only a cosmetic issue.
I can reproduce the bug on rhv4.2 Description of problem: Original info is wrong if import guest from ova file on rhv4.2 GUI Version-Release number of selected component (if applicable): ovirt-engine-4.2.3.2-0.1.el7.noarch vdsm-4.20.26-1.el7ev.x86_64 How reproducible: 100% Steps to Reproduce: 1.Copy ova file to host which is registered on rhv4.2 2.Import guest from ova on rhv4.2 3.Found guest's original info is RHV after importing, pls refer to screenshot Actual results: As above description Expected results: Original info should be VMware if import guest from ova file on rhv4.2 GUI Additional info:
Created attachment 1427445 [details] screenshot
Closing because this is cosmetic only with an easy workaround