Bug 787702

Summary:	When looking at exported templates on export domain, origin is NULL
Product:	[Retired] oVirt	Reporter:	Yair Zaslavsky <yzaslavs>
Component:	ovirt-engine-core	Assignee:	lpeer <lpeer>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	acathrow, amureini, iheim, oourfali, ykaul
Target Milestone:	---	Keywords:	EasyFix
Target Release:	3.3.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	storage
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-10 19:10:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.