Description of problem:
When combining next boot, and current changes, such as memory & comment - the current change not be applied, such as comment.
Version-Release number of selected component (if applicable):
I'd say it's intentional, you set all values immediately or deferred on next run
For update a running VM with a param for next boot (like memory) + param that can be updated now (like comment),
I'd expect the comment to be updated, while VM is still running,
and the memory to be updated after VM next run.
Current behaviour is that the comment update is simply ignored:
it is not updated at current VM run, and not on next VM run.
(In reply to Ilanit Stein from comment #2)
> Current behaviour is that the comment update is simply ignored:
> it is not updated at current VM run, and not on next VM run.
ah, so that's certainly wrong. thanks.
problem is that comment is missing from ovf infrastructure, so its missing from snpashots, export/import and now update of running vm.
if you try the same scenario with memory and description, you will see it works as you expect, and as it should.
Verified on oVirt Engine Version: 3.5.0-0.0.master.20140821064931.gitb794d66.el6
update running vm with comment + memory => now updates comment immediately,
and comment is saved after vm boot.
oVirt 3.5 has been released and should include the fix for this issue.