Bug 1477502 - DR (site to site) - Add template versions to OVF
Summary: DR (site to site) - Add template versions to OVF
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.1
: ---
Assignee: Maor
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-02 09:38 UTC by Maor
Modified: 2017-12-27 23:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-27 23:05:41 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+
ylavi: exception+

Attachments (Terms of Use)

Description Maor 2017-08-02 09:38:31 UTC 
Description of problem:
Add template versions to the entity OVF, so on registration the engine will be able to register the template with its versions

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Yaniv Lavi 2017-12-27 13:22:44 UTC 
Would not doing for 4.2 this mean that any VM would break if the templates has versions?
Comment 2 Maor 2017-12-27 23:05:41 UTC 
template version seems to be part of the OVF after all.
Verified it trough the GUI with success.
Once the storage domain is attached to the setup, we can see two Templates with the same name which exists under the unregistered entities sub tab.
The user should only pick the base volume to be registered and that will cause the Template to be registered with its other version.
Closing this bug as current release.
Note You need to log in before you can comment on or make changes to this bug.