Created attachment 1347012 [details] engine log Description of problem: When trying to enable\disable HA VM lease(hotplug) a message is shown: Changes that can be applied immediately: VM Lease -apply later option Changes that require Virtual Machine restart: VM Lease Version-Release number of selected component (if applicable): 4.2.0-0.0.master.20171025204923.git6f4cbc5.el7.centos How reproducible: Always Steps to Reproduce: 1. Create a VM and run it. 2. Enable or disable the HA option, with lease. Actual results: A window message is shown with double meaning. Expected results: Only the next message(or other appropriate): VM Lease -apply later option Additional info: engine log attached
Created attachment 1359472 [details] edit VM to be HA
Created attachment 1359473 [details] edit VM to be HA confirmation window
Hi Liran, It seems like the issue fixed in master 4.2 from commit - 97ca6b571b34c07eb2f6d4686b4e106402c95882. I've attached two screenshots: 1. Change the VM to be HA. 2. Following confirmation window You can see that the 'Changes that require Virtual Machine restart:' was updated to include the 'Resume Behavior' updates instead of the double meaning - VM Lease. Please close the bug in case it solved the issue.
Verified on: Software version:4.2.0-0.5.master.el7 The issue solved and can be seen in Eyal attachments.
Moving back to post until the relevant patch from 4.2 will backport to 4.1.
Created attachment 1360684 [details] edit VM to be HA 4.1
Created attachment 1360685 [details] edit VM to be HA confirmation window 4.1
Seems like the patch that responsible for the fix already found on 4.1 branch - commit - 8a9fe89c15cbfbf3914e6bc505d229943b1067c5 Screenshots of 4.1 were added. Liran, Sorry about this but please verify (this time on 4.1) again.
This bug is a duplication of - https://bugzilla.redhat.com/show_bug.cgi?id=1492471 which target to 4.2 and already verified. Keep this bug open and backport the fix to 4.1.
verified on 4.1.9-0.2.el7
This bugzilla is included in oVirt 4.1.9 release, published on Jan 24th 2018. Since the problem described in this bug report should be resolved in oVirt 4.1.9 release, published on Jan 24th 2018, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.