[ovirt-users] Re: engine.log flooded with "Field 'foo' can not be updated when status is 'Up'"

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 < [ mailto:matthias.leopold@meduniwien.ac.at | matthias.leopold(a)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 -- [ mailto:users@ovirt.org | users(a)ovirt.org ] To unsubscribe send an email to [ mailto:users-leave@ovirt.org | users-leave(a)ovirt.org ] Privacy Statement: [ https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi... | https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi... ] oVirt Code of Conduct: [ https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi... | https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovi... ] List Archives: [ https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o... | https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.o... ] To view the terms under which this email is distributed, please go to:- [ http://leedsbeckett.ac.uk/disclaimer/email/ | http://leedsbeckett.ac.uk/disclaimer/email/ ]