There are two problems: The lease selection should be disabled once high availability is set to false yet this is overriden by the version check, if leases are supported then the field becomes enabled If the lease selection is disabled since it's not supported by the cluster version, toggling high availability will enable the selection even though leases are not supported Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce 1: 1. Try to add a new in a cluster version supporting VM leases 2. Go to High Availability tab Actual results: VM lease selection is available although it shouldn't (HA is not set) Expected results: VM lease selection should be disabled Steps to Reproduce 2: 1. Try to add a new in a cluster version not supporting VM leases 2. Go to High Availability tab (VM leases selection will be disabled) 3. Click on high Availility checkbox Actual results: VM lease selection is not available although it shouldn't (cluster version does not support it) Expected results: VM lease selection should still be disabled
*** Bug 1434381 has been marked as a duplicate of this bug. ***
-------------------------------------- Tested with the following code: ---------------------------------------- rhevm-4.1.3-0.1.el7.noarch vdsm-4.19.16-1.el7ev.x86_64 Tested with the following scenario: Steps to Reproduce 1: 1. Try to add a new VM in a cluster version supporting VM leases 2. Go to High Availability tab Actual results: VM lease selection is disabled Steps to Reproduce 2: 1. Try to add a new VM in a cluster version not supporting VM leases 2. Go to High Availability tab (VM leases selection will be disabled) 3. Click on high Availability checkbox Actual results: VM lease is still disabled Moving to VERIFIED!