Bug 1063891

Summary:	OVF is not exposed for snapshot using REST API
Product:	[Retired] oVirt	Reporter:	Arik <ahadas>
Component:	ovirt-engine-api	Assignee:	Juan Hernández <juan.hernandez>
Status:	CLOSED DUPLICATE	QA Contact:	bugs <bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.4	CC:	acathrow, ahadas, amureini, gklein, iheim, laravot, yeylon
Target Milestone:	---
Target Release:	3.4.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	storage
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-12 16:18:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Arik 2014-02-11 15:27:40 UTC

Description of problem:
Using GET request with All-Content header which is set to true, we should also get the configuration of the VM as OVF.
It doesn't seems to work.
It works well for the snapshots collection (/api/vms/GUID/snapshots) but not for the single snapshot (/api/vms/GUID/snapshots/GUID)

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


How reproducible:
100%


Steps to Reproduce:
1. set header All-Content to true
2. send GET request on /api/vms/<GUID1>/snapshots/<GUID2>
3.

Actual results:
The result doesn't contain the VM configuration (OVF)

Expected results:
The result should contain the VM configuration

Additional info:

Comment 1 Juan Hernández 2014-02-11 15:42:53 UTC

What specific snapshot are you using to test this? May it be the active VM? The active VM doesn't currently include the VM information, and bug 1047965 is opened to fix that.

Any snapshot other than the active VM should return the OVF correctly, at least it does in my environment. Can you please double check?

If this works correctly please close this bug as a duplicate of bug 1047965.

Comment 2 Arik 2014-02-12 16:18:03 UTC


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