Created attachment 1317665 [details] logs from engine and host Description of problem: While a high availability VM that has a lease on the storage is in snapshot preview, or after snapshot restore, the VM cannot be started, its lease is reported as invalid state forever. Version-Release number of selected component (if applicable): ovirt-engine-4.2.0-0.0.master.20170823165744.git116f435.el7.centos.noarch vdsm-4.20.2-104.git5f512b9.el7.centos.x86_64 How reproducible: Always, encountered in automation during execution of https://polarion.engineering.redhat.com/polarion/redirect/project/RHEVM3/workitem?id=RHEVM-18162 Steps to Reproduce: 1. Create a VM with a disk a lease on the storage (both on NFS in my case) 2. Create a snapshot for the VM containing the disk and the VM configuration (default) 3. Preview / Preview+commit the snapshot 4. Start the VM Actual results: The VM cannot be started: 2017-08-24 15:17:37,171+03 WARN [org.ovirt.engine.core.bll.RunVmCommand] (default task-15) [54e74743-cd5d-4883-8ca2-4e15ca0018e4] Validation of action 'RunVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_VM_LEASE Expected results: HA VM with a lease on the storage should be runnable in snapshot preview and after snapshot restore Additional info: logs from engine and host
If the fix is reasonable, this probably deserves a zstream patch too
Tal - any updates on this?
Not currently, it's in the queue
(In reply to Tal Nisan from comment #3) > Not currently, it's in the queue Is this a blocker for oVirt GA? It is marked as such and has urgent severity. Where is it in the Q?
(In reply to Yaniv Kaul from comment #4) > (In reply to Tal Nisan from comment #3) > > Not currently, it's in the queue > > Is this a blocker for oVirt GA? It is marked as such and has urgent > severity. Where is it in the Q? This is neither urgent nor a blocker.
A workaround will be to edit the VM to remove the lease and then select the lease storage domain again to create a new one
Eyal - I think you filled in the doctext in the environment box by mistake.
Verified. ovirt-enginge: 4.2.2.1-0.1.el7 vdsm: 4.20.19-1.el7ev.noarch
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.