Description of problem: Currently creation of VM leases in data centers with version lower that 4.1 resulting in VDSM calls to a non existing verb Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
While a patch disabling the feature in the UI was introduced (see trackers), the feature should be first and foremost disabled in the backend both for the UI and more important the REST API calls
Arik, I've disabled it for all flows aside for import VM as in that flow it's a reasonable scenario to export a VM with lease from 4.1 setup and import it to a 4.0 setup. I thought to import without adding the lease and issue an audit log about it, what do you think?
(In reply to Tal Nisan from comment #2) > Arik, I've disabled it for all flows aside for import VM as in that flow > it's a reasonable scenario to export a VM with lease from 4.1 setup and > import it to a 4.0 setup. > I thought to import without adding the lease and issue an audit log about > it, what do you think? Makes sense.
-------------------------------------- Tested with the following code: ---------------------------------------- ovirt-engine-4.1.0.3-0.0.master.20170123115434.git8a69605.el7.centos.noarch vdsm-4.19.2-1.el7.centos.x86_64 Tested with the following scenario: Steps to Reproduce: 1. create new vm in 4.0 cluster 2. configure this vm High available and create vm lease Actual results: can't create the vm with vm lease, VM leases are not supported for this virtual machine compatibility version. Expected results: Moving to VERIFIED!