Bug 1066406 - High Availability flag should be included for template when exporting/importing from Export Domain
Summary: High Availability flag should be included for template when exporting/importi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.4
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
: 3.5.0
Assignee: Jiri Moskovcak
QA Contact: Lukas Svaty
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-18 10:29 UTC by Lukas Svaty
Modified: 2016-02-10 19:41 UTC (History)
6 users (show)

Fixed In Version: ovirt-3.5.0-alpha1
Clone Of:
Environment:
Last Closed: 2014-10-17 12:23:30 UTC
oVirt Team: SLA
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 24863 0 None MERGED engine: keep the HA flag when exporting/importing VM template Never
oVirt gerrit 25000 0 None ABANDONED engine: keep the HA flag when importing/exporting VM template Never

Description Lukas Svaty 2014-02-18 10:29:04 UTC 
What is the nature and description of the request? 
We would really like the correct High Availability setting to be included in the template metadata so it is correctly reflected upon import.
Comment 1 Doron Fediuck 2014-02-19 08:16:31 UTC 
Why is this a high priority bug? 
Is it a regression or a blocker?
Was it reported by someone who is using oVirt?
Comment 2 Jiri Moskovcak 2014-02-19 12:44:48 UTC 
isn't this dupe of: https://bugzilla.redhat.com/show_bug.cgi?id=1026857 ?? Which should be already fixed..
Comment 3 Jiri Moskovcak 2014-02-19 12:46:37 UTC 
Oops, I was too fast, it's for VM, not for template, so we want to be able to export/import the HA flag even in the templates?
Comment 4 Lukas Svaty 2014-02-19 13:00:22 UTC 
Doron: high priority copied from BZ#1026857

Jiri: i see no reason why import should save the correct the options about the HA in VMs and not in templates
Comment 5 Sandro Bonazzola 2014-10-17 12:23:30 UTC 
oVirt 3.5 has been released and should include the fix for this issue.
Note You need to log in before you can comment on or make changes to this bug.