Description of problem: VMs with 'NEXT_RUN' configuration snapshots cause engine.log lines like WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-123) [some UUID] Field 'foo' can not be updated when status is 'Up' not only once when VM configuration change is entered but also whenever VM list is refreshed subsequently (and maybe other occasions) in Administration Portal Version-Release number of selected component (if applicable): ovirt-engine-4.3.5.5-1.el7.noarch How reproducible: change property of VM that cannot be applied immediately refresh VM list Steps to Reproduce: 1. change property of VM that cannot be applied immediately 2. refresh VM list 3. look at engine.log Actual results: set of lines like WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-123) [some UUID] Field 'foo' can not be updated when status is 'Up' is visible in engine.log Expected results: no logs relating to VMs with 'NEXT_RUN' configuration snapshots visible in engine.log Additional info: I saw this in two oVirt installations that were upgraded from 4.3.3 to 4.3.5 when there are a lot of VMs with 'NEXT_RUN' configuration snapshots (like in the aftermath of a major version upgrade where every VM has to upgrade compatibility version) this behaviour can cause considerable load on the engine host and engine.log size can grow rapidly when using the Administration Portal I'm on holiday next week and can't provide further information until 2019-08-26, but I think the situation is rather obvious and the bug was confirmed on the mailing list
Hi, I have already asked in the mailing list, if there will be a patch available also for 4.3.X? But no answer for over one week now. It would be impossible for me to upgrade to 4.3.5 until this problem is fixed. If you don't want to release an official patch, then please give me a howto to fix that manually. BR Florian
Hi, are there any news on this, if this patch may be available earlier than 4.4? I see, that there is already a patch available, but not merged! BR Florian
Hi Florian, this should also get to 4.3.x stream, see https://gerrit.ovirt.org/#/c/103170/ Lucia
After changing properties of several different guest VMs which require restart to take affect, I see in engine.log as follows: 2020-03-03 14:16:21,350+02 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-5) [f32e41e9-954f-4 264-af6c-2383e5c3e045] ObjectIdentityChecker.isUpdateValid:: Not updatable field 'memSizeMb' was updated 2020-03-03 14:14:20,422+02 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-5) [acb6b91e-c56a-4 184-8acd-935c39ca4e3e] ObjectIdentityChecker.isUpdateValid:: Not updatable field 'timeZone' was updated Refresh doesn't case these warnings to multiply. Warnings appeared only once, thus no more multiplying warnings in log appeared. Moving to verified. Tested on: NFS deployment on these components: rhvm-appliance.x86_64 2:4.4-20200123.0.el8ev rhv-4.4.0 sanlock-3.8.0-2.el8.x86_64 qemu-kvm-4.2.0-12.module+el8.2.0+5858+afd073bc.x86_64 vdsm-4.40.5-1.el8ev.x86_64 libvirt-client-6.0.0-7.module+el8.2.0+5869+c23fe68b.x86_64 ovirt-hosted-engine-setup-2.4.2-2.el8ev.noarch ovirt-hosted-engine-ha-2.4.2-1.el8ev.noarch Linux 4.18.0-183.el8.x86_64 #1 SMP Sun Feb 23 20:50:47 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 8.2 Beta (Ootpa) Engine is Software Version:4.4.0-0.17.master.el7 Red Hat Enterprise Linux Server release 7.8 Beta (Maipo) Linux 3.10.0-1123.el7.x86_64 #1 SMP Tue Jan 14 03:44:38 EST 2020 x86_64 x86_64 x86_64 GNU/Linux
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.