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

Bug 1554875

Summary:	When importing a VM with a lease using the UI, the property that indicates whether the VM has a lease ignored
Product:	[oVirt] ovirt-engine	Reporter:	Eyal Shenitzky <eshenitz>
Component:	BLL.Storage	Assignee:	Eyal Shenitzky <eshenitz>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Evelina Shames <eshames>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	amureini, bugs, eshenitz, tnisan
Target Milestone:	ovirt-4.2.3	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.2.2.5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-10 06:28:04 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 Eyal Shenitzky 2018-03-13 13:52:07 UTC

Description of problem:

When importing a VM from an export domain using the UI (only), the field which indicates whether the VM has a lease is ignored and prevents the lease from being created on the environment when importing the VM.

Version-Release number of selected component (if applicable):
4.3.0_master from commit - fe6e82f57a329fd358644c1170a4be75af812753

How reproducible:
100%

Steps to Reproduce:
1. Create a VM with lease
2. Export the VM to an export domain
3. Import the VM back to the environment (with different name)

Actual results:
The VM is imported to the environment but without a lease

Expected results:
The VM should import to the environment with a lease


Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2018-04-10 08:46:52 UTC

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 Yaniv Kaul 2018-04-11 13:36:12 UTC

It either missed 4.2.2 or supposed to be ON_QA, no?

Comment 3 Eyal Shenitzky 2018-04-11 13:39:59 UTC

(In reply to Yaniv Kaul from comment #2)
> It either missed 4.2.2 or supposed to be ON_QA, no?

It was ON_QA, a fix was needed so we pushed to 4.2.2.3

Comment 4 Yaniv Kaul 2018-04-11 13:41:57 UTC

(In reply to Eyal Shenitzky from comment #3)
> (In reply to Yaniv Kaul from comment #2)
> > It either missed 4.2.2 or supposed to be ON_QA, no?
> 
> It was ON_QA, a fix was needed so we pushed to 4.2.2.3

Either it's in 4.2.2, and then it's ON_QA, or it missed it and going to appear in 4.2.3, and then the target milestone is incorrect.

Comment 5 Eyal Shenitzky 2018-04-11 13:45:19 UTC

Changed to 4.2.3

Comment 6 Evelina Shames 2018-04-18 08:33:29 UTC

Verified.
ovirt-engine-4.2.3-0.1

Comment 7 Sandro Bonazzola 2018-05-10 06:28:04 UTC

This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.