in webadmin have a running VM: - edit the VM and change the memory (this will change also the min allocated memory) - save - the dialog asking if the memory change is supposed to be hotplugged or not will pop up (correct) - press cancel and close the dialog - open it again - edit the memory (this will change also the min allocated memory) - change the min allocated memory back to the same as it is was defined on the VM - press ok - no dialog pops up (problem) Additional info: - the issue seems to be in the VmListModel.updateVM() which asks for the getVmChangedFieldsForNextRun(). This call returns only fields which can not be hotplugged (for example the min allocated memory). The checks which ask for the memory hotplug are in the callback and only in case the returned set of changed fields is not empty. This is I'd say incorrect, the check about the hotpluggable fields should be performed regardless of the fact if there are fields which are not hotpluggable.
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.
changing Physical Memory Guaranteed to previous value doesn't affect showing the confirmation dialog verified in ovirt-engine-webadmin-portal- 4.1.0-0.4.master.20170115141203.git30e806b.el7.centos.noarch