Bug 787702 - When looking at exported templates on export domain, origin is NULL
Summary: When looking at exported templates on export domain, origin is NULL
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3.4
Assignee: lpeer
QA Contact:
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-06 15:07 UTC by Yair Zaslavsky
Modified: 2016-02-10 16:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-10 19:10:41 UTC
oVirt Team: Storage

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Yair Zaslavsky 2012-02-06 15:07:01 UTC 
Description of problem:

Following https://bugzilla.redhat.com/786673  , I noticed that OVF for VM template does not include "originType" , and as a result of the fix to the mentioned bug, the empty CTOR for VmStatic does not fill the originType.
The code does not set it anywhere in the query that retrieves the VM templates on the export domain, so the UI gets the origin type as null.
I think the OVF writing should be fixed to include origin type and we should figure out what to do with missing origin types for already existing OVFs (existing VM templates on export domains).


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Itamar Heim 2012-12-10 19:10:41 UTC 
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.
Note You need to log in before you can comment on or make changes to this bug.