there also seems to be a lot of queries send to the engine database, this is the problem I had with 70 VMs in compatibility mode as this really slowed the admin portal down while querying running VM's for instance.

From: Sharon Gratch <sgratch@redhat.com>
Sent: 20 August 2019 10:00
To: Florian Schmid; Ryan Barry; Lucia Jelinkova
Cc: users
Subject: [ovirt-users] Re: engine.log flooded with "Field 'foo' can not be updated when status is 'Up'"

Hi,

@Ryan Barry, @Lucia Jelinkova - is the possible to fix Bug 1742924 earlier than oVirt 4.4 release?

If the fix involves only removing the warning from the log, then it seems like a pretty quick fix...

Thanks,

Sharon

On Tue, Aug 20, 2019 at 10:31 AM Florian Schmid <fschmid@ubimet.com> wrote:

Hello Sharon,

I had a look on the bug report and it says, that this fix is targeted for oVirt 4.4. This would be really bad for us, because I have hundreds of VMs, which can't be restarted so easily (over 500) and this would break then our engine...

This would make it impossible for us to upgrade to oVirt 4.3.5 or higher until the Bug is fixed.

Would it be possible to get a manual fix for this?

I would like to upgrade to 4.3.6 when it is out in September or beginning of October.

BR Florian

Von: "Sharon Gratch" <sgratch@redhat.com>
An: "Matthias Leopold" <matthias.leopold@meduniwien.ac.at>
CC: "p staniforth" <P.Staniforth@leedsbeckett.ac.uk>, "users" <users@ovirt.org>
Gesendet: Dienstag, 13. August 2019 19:14:28
Betreff: [ovirt-users] Re: engine.log flooded with "Field 'foo' can not be updated when status is 'Up'"

Hi,

We checked that issue and found out that you are right and this extra logging lines problem is caused by "next run configuration" improvements added to oVirt 4.3.5.

The current behaviour is that for each running VM with next run configuration existed, a warning line of "....Field 'xxx' can not be updated when status is 'Up'" appears in log, per each vm device and whenever the vms list is refreshed.

This definitely may flood the engine log if there are few such VMs.

Can you please file a bug on that?

Thanks,

Sharon

On Tue, Aug 13, 2019 at 5:01 PM Matthias Leopold <matthias.leopold@meduniwien.ac.at> wrote:

Thanks for the feedback, I think my description was a bit clumsy, but at
least someone confirms that he has seen this...
I still hope it's linked to unfinished VM "Custom Compatibility Version"
updates, tomorrow I'll know, when I finally can do the last VM reboots.
My "Administration Portal" is still usable, but nevertheless I think
this is something the upstream developers should look into.

Regards
Matthias

Am 13.08.19 um 12:48 schrieb Staniforth, Paul:
> Hello Mathias,
> I also had this problem, the flood of warning messages was most notably generated when showing all the VMs running from the admin portal dashboard as we had 70 VMs running this generated the following but for all 70 VMs. I was able to restart most of the VMs otherwise the admin portal became unusable.
> I don't recall this being a problem upgrading from 4.1 to 4.2
>
> Regards
> Paul S.
>
> 2019-08-13 11:44:36,771+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'customCompatibilityVersion' can not be updated when status is 'Up'
> 2019-08-13 11:44:36,771+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'exportDate' can not be updated when status is 'Up'
> 2019-08-13 11:44:36,771+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'managedDeviceMap' can not be updated when status is 'Up'
> 2019-08-13 11:44:36,771+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'ovfVersion' can not be updated when status is 'Up'
> 2019-08-13 11:44:36,772+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'balloonEnabled' can not be updated when status is 'Up'
> 2019-08-13 11:44:36,772+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'watchdog' can not be updated when status is 'Up'
> 2019-08-13 11:44:36,773+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'rngDevice' can not be updated when status is 'Up'
> 2019-08-13 11:44:36,774+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'soundDeviceEnabled' can not be updated when status is 'Up'
> 2019-08-13 11:44:36,774+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'consoleEnabled' can not be updated when status is 'Up'
> 2019-08-13 11:44:36,775+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'virtioScsiEnabled' can not be updated when status is 'Up'
> 2019-08-13 11:44:36,776+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [936d48c4-76c6-4363-85f0-7147923bbb2f] Field 'graphicsDevices' can not be updated when status is 'Up'
> 2019-08-13 11:44:39,490+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [0b246c13-223f-4728-b988-5da34139aeb2] Field 'customCompatibilityVersion' can not be updated when status is 'Up'
> 2019-08-13 11:44:39,490+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [0b246c13-223f-4728-b988-5da34139aeb2] Field 'exportDate' can not be updated when status is 'Up'
> 2019-08-13 11:44:39,490+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [0b246c13-223f-4728-b988-5da34139aeb2] Field 'managedDeviceMap' can not be updated when status is 'Up'
> 2019-08-13 11:44:39,490+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [0b246c13-223f-4728-b988-5da34139aeb2] Field 'ovfVersion' can not be updated when status is 'Up'
> 2019-08-13 11:44:39,490+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [0b246c13-223f-4728-b988-5da34139aeb2] Field 'balloonEnabled' can not be updated when status is 'Up'
> 2019-08-13 11:44:39,491+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [0b246c13-223f-4728-b988-5da34139aeb2] Field 'watchdog' can not be updated when status is 'Up'
> 2019-08-13 11:44:39,492+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [0b246c13-223f-4728-b988-5da34139aeb2] Field 'rngDevice' can not be updated when status is 'Up'
> 2019-08-13 11:44:39,493+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [0b246c13-223f-4728-b988-5da34139aeb2] Field 'soundDeviceEnabled' can not be updated when status is 'Up'
> 2019-08-13 11:44:39,493+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [0b246c13-223f-4728-b988-5da34139aeb2] Field 'consoleEnabled' can not be updated when status is 'Up'
> 2019-08-13 11:44:39,494+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [0b246c13-223f-4728-b988-5da34139aeb2] Field 'virtioScsiEnabled' can not be updated when status is 'Up'
> 2019-08-13 11:44:39,495+01 WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default task-855) [0b246c13-223f-4728-b988-5da34139aeb2] Field 'graphicsDevices' can not be updated when status is 'Up'
>
> ________________________________________
> From: Matthias Leopold <matthias.leopold@meduniwien.ac.at>
> Sent: 09 August 2019 19:11
> To: users
> Subject: [ovirt-users] engine.log flooded with "Field 'foo' can not be updated when status is 'Up'"
>
> Hi,
>
> I updated my production oVirt environment from 4.3.3 to 4.3.5 today.
> Everything went fine so far, but there's one annoying phenomenon:
>
> When I log into the "Administration Portal" and request the VM list
> ("/ovirt-engine/webadmin/?locale=en_US#vms") engine.log is flooded with
> lines like
>
> WARN [org.ovirt.engine.core.utils.ObjectIdentityChecker] (default
> task-10618) [54d8c375-aa72-42f8-876e-8777d9d1a08a] Field
> 'balloonEnabled' can not be updated when status is 'Up'
>
> "Field", task and UUID vary and the flood stops after a while. Also
> listing or trying to edit other entities seems to trigger this "storm"
> or loop over and over again to a point that log file size is becoming an
> issue and interface is becoming sluggish. I can also see that CPU usage
> of engine java process goes up. When I log out everything is quiet and
> "VM Portal" is not affected at all.
>
> I have seen lines like that before and know that they are usually OK
> (when changing VM properties), but these logs used to be linked to
> singular events. I suspect that the present behaviour might be linked to
> VMs that have "Pending Virtual Machine changes", which are in most cases
> "Custom Compatibility Version" changes that still stem from the upgrade
> to Cluster Version 4.3. I can't be sure and I can't resolve all these
> pending changes now, but these should not be causing such annoying
> behaviour in the first place.
>
> I resorted to setting engine log level to "ERROR" right now to at least
> stop the log file from growing, but this not a solution. I can still see
> CPU load going up when using the interface. I very much hope that
> someone can explain whats happening and tell me how to resolve this.
>
> thanks a lot
> Matthias
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-leave@ovirt.org
> Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fsite%2Fprivacy-policy%2F&data=02%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7Cf3728d98bdd54ea183fe08d71cf59aee%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637009713497869419&sdata=SYEkpmfrjitOljgpqWuLQKookZACJNd%2BEi%2F9xN%2F6kwA%3D&reserved=0
> oVirt Code of Conduct: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fcommunity%2Fabout%2Fcommunity-guidelines%2F&data=02%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7Cf3728d98bdd54ea183fe08d71cf59aee%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637009713497869419&sdata=z89zQpustu%2BTVXnPZy477G6d3PJf%2FZ6V1SGDRDm6Bsk%3D&reserved=0
> List Archives: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovirt.org%2Farchives%2Flist%2Fusers%40ovirt.org%2Fmessage%2FMKFQRCKHRT6NJUHF7URJTQG753MND6PJ%2F&data=02%7C01%7Cp.staniforth%40leedsbeckett.ac.uk%7Cf3728d98bdd54ea183fe08d71cf59aee%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637009713497869419&sdata=oNe3foQ%2BlF7dxyrwaEN8fYsTUazvJqqjj2d%2FoNBjp%2Bg%3D&reserved=0
> To view the terms under which this email is distributed, please go to:-
> http://leedsbeckett.ac.uk/disclaimer/email/
>

--
Matthias Leopold
IT Systems & Communications
Medizinische Universität Wien
Spitalgasse 23 / BT 88 /Ebene 00
A-1090 Wien
Tel: +43 1 40160-21241
Fax: +43 1 40160-921200
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XWJJL3ESCWCJR7XSTLOHD5NOPUD4NSSZ/

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IEKGPFCSLQODRB64RIDUXOQZPYW4ILJE/