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:
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.
It either missed 4.2.2 or supposed to be ON_QA, no?
(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
(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.
Changed to 4.2.3
Verified. ovirt-engine-4.2.3-0.1
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.