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

Bug 1440176

Summary:	A template created from a HA VM with leases doesn't keep the lease config (only HA config)
Product:	[oVirt] ovirt-engine	Reporter:	Carlos Mestre González <cmestreg>
Component:	BLL.Storage	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Carlos Mestre González <cmestreg>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1.1.8	CC:	amureini, bugs, stirabos, tnisan
Target Milestone:	ovirt-4.1.3	Flags:	rule-engine: ovirt-4.1+
Target Release:	4.1.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-06 13:10:05 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 Carlos Mestre González 2017-04-07 13:32:05 UTC

Description of problem:
Creating a template from a VM with HA & lease creates a template with HA but no lease (and accordingly, when a VM is created from that template the lease is not there)

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

How reproducible:
100%

Steps to Reproduce:
1. Create a Vm with a boot disk + HA + a lease
2. Press Make Template and make a template
3. Check templates config: no VM lease set, only HA
4. Create a vm from such template

Actual results:
VM has HA but not VM lease

Expected results:
Template and VM with lease

Additional info:
According to our test plan this should work.

Comment 2 Carlos Mestre González 2017-06-01 10:27:07 UTC

verified: 4.1.3-0.1.el7

Comment 3 Carlos Mestre González 2017-06-02 12:08:37 UTC

Hi Tal, I just tested this on 4.2 => 4.2.0-0.0.master.20170531203202.git1bf6667.el7.centos and is still happening, should I open a new BZ for 4.2 to track this issue on that verison until is fixed?

thanks

Comment 4 Allon Mureinik 2017-06-04 12:04:26 UTC

(In reply to Carlos Mestre González from comment #3)
> Hi Tal, I just tested this on 4.2 =>
> 4.2.0-0.0.master.20170531203202.git1bf6667.el7.centos and is still
> happening, should I open a new BZ for 4.2 to track this issue on that
> verison until is fixed?
> 
> thanks

Yes please.

Comment 5 Carlos Mestre González 2017-06-06 08:48:53 UTC

done: https://bugzilla.redhat.com/show_bug.cgi?id=1459072