Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1063877

Summary:	Missing things in Backup-Restore API documentation
Product:	[Retired] oVirt	Reporter:	Arik <ahadas>
Component:	ovirt-engine-core	Assignee:	Liron Aravot <laravot>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Aharon Canan <acanan>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.4	CC:	acathrow, amureini, bugs, gklein, iheim, tnisan, yeylon
Target Milestone:	---
Target Release:	3.4.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	storage
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1108245 (view as bug list)		Environment:
Last Closed:	2014-06-12 13:08:15 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:
Bug Depends On:
Bug Blocks:	1108245

Description Arik 2014-02-11 15:15:00 UTC

Description of problem:
Looking at: http://www.ovirt.org/Features/Backup-Restore_API_Integration,
2 things are missing:

1. Explain how to get the configuration of the snapshot using REST API, and how should it be used to create VM which is based on this configuration

2. When attaching disk to VM it seems that it is not activated by default, so we need to mention that it should be activated before we can use in from within the guest

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 2014-02-16 08:23:57 UTC

Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.

Comment 2 Sandro Bonazzola 2014-03-04 09:20:04 UTC

This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 3 Sandro Bonazzola 2014-06-11 06:51:05 UTC

This is an automated message:
This bug has been re-targeted from 3.4.2 to 3.5.0 since neither priority nor severity were high or urgent. Please re-target to 3.4.3 if relevant.