Description of problem: When registering a VM with a lease from a data domain, the VM registered to the data-center but the VM lease doesn't create. The VM appeared to be with the lease but the lease doesn't exist. Version-Release number of selected component (if applicable): master-4.3.0 - from commit 2b737f5ee74668ab201aec7c118444382e2f6365 How reproducible: 100% Steps to Reproduce: 1. Create a VM with disk and lease based on storage domain 'A' 2. Deactivate and detach storage domain 'A' 3. Attach storage domain 'A' back to the data-center 4. register the VM from step 1 Actual results: VM registered back to the data-center, The VM appeared to have a lease, but the lease doesn't exist. Expected results: VM should be registered and the lease should create on one of the storage domains Additional info:
*** This bug has been marked as a duplicate of bug 1524455 ***
(In reply to Eyal Shenitzky from comment #1) > > *** This bug has been marked as a duplicate of bug 1524455 *** Eyal, this bug is about registering a VM from a *data* domain, while bug 1524455 is about importing from an *export* domain. Can you explain where the code paths converge?
The fix for bug 1524455 should also solve the issue above (https://gerrit.ovirt.org/#/c/88314). should I set the bug to be dependent on bug 1524455 instead of closing it?
(In reply to Eyal Shenitzky from comment #3) > The fix for bug 1524455 should also solve the issue above > (https://gerrit.ovirt.org/#/c/88314). > should I set the bug to be dependent on bug 1524455 instead of closing it? I think so. The usecase here is different, and QE should verify both flows (regardless of whether the same patch solves both issues)
Verified with the following code: ------------------------------------------ ovirt-engine-4.2.2.5-0.1.el7.noarch vdsm-4.20.23-1.el7ev.x86_64\ Verified with the following scenario: ------------------------------------------ Steps to Reproduce: 1. Create a VM with disk and lease based on storage domain 'A' 2. Deactivate and detach storage domain 'A' 3. Attach storage domain 'A' back to the data-center 4. register the VM from step 1 Expected results: VM is registered and the lease exists on the storage domain Moving to verified
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 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.