Hide Forgot
Description of problem: VDSM should provide a way to attach a volume (internal/leaf) as a transient disk. A transient disk is a temporary qcow layer based on a (usually internal) volume that is attached to a VM in read-write mode. All changes stored in the transient disk will be lost as soon as the disk is hot-unplugged or when the VM exits. Its primary use is to access in read-write mode a snapshot (read-only volume).
Part of 3.3 Backup API flow
Transient volume is now supported by vdsm. As part of the backup API feature, when we attach a disk snapshot to a dedicated machine with a backup software installed and plug it to this machine, a new transient volume is created by vdsm. This new volume enables vdsm to make changes on the RO attached disk snapshot. Checked during backup API feature testing. Tested on is21 and is23
(In reply to Elad from comment #3) > Transient volume is now supported by vdsm. As part of the backup API > feature, when we attach a disk snapshot to a dedicated machine with a backup > software installed and plug it to this machine, a new transient volume is > created by vdsm. This new volume enables vdsm to make changes on the RO > attached disk snapshot. > > > Checked during backup API feature testing. Tested on is21 and is23 and is22
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0040.html