Description of problem: Edit running VM with parameters, that will be applied on next run, for example memory, and also change vcpu socket number, and choose to apply later. VM General tab, at the bottom, vm will show the new value, that shouldn't have yet applied, unlike other "Next boot" parameters, like memory, that still show previous value, in the general tab. Also Read VM via REST, also show the new socket number. Version-Release number of selected component (if applicable): ovirt-engine 3.5-rc1 How reproducible: 100%
the "apply later" only refer to hot plug where possible, so currently its only cpu. if you change name/description/etc.. it will apply immediately, always. (like in previous versions) if you change memory/boot order/etc.. it will be applied when vm is down (in previous versions, it was blocked) currently, only for cpu user can choose if to apply immediately (hot-plug) or on next-run. if i understand correctly, this is not a bug, right?
This bug might be related to bug 1128442
Ok i did not understand correctly the description, its indeed another effect of the problem in bug 1128442 the problem is that the number of sockets is marked in the backend as always editable, and therefor the config is saved immediately, and the dialog doesn't open for it.
*** Bug 1128442 has been marked as a duplicate of this bug. ***
verified in vt3
oVirt 3.5 has been released and should include the fix for this issue.