Bug 1460519 - Origin shows RHV after import of VM with unknown origin
Origin shows RHV after import of VM with unknown origin
Status: NEW
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt (Show other bugs)
Unspecified Unspecified
low Severity low (vote)
: ovirt-4.3.0
: ---
Assigned To: nobody nobody
meital avital
Depends On:
Blocks: TRACKER-bugs-affecting-libguestfs 1459816
  Show dependency treegraph
Reported: 2017-06-11 15:32 EDT by Tomáš Golembiovský
Modified: 2017-10-25 05:38 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: ovirt‑4.3+

Attachments (Terms of Use)

  None (edit)
Description Tomáš Golembiovský 2017-06-11 15:32:51 EDT
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:

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.
Comment 1 Tomas Jelinek 2017-06-12 10:26:56 EDT
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.

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