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

2019-09-02 Thread Florian Schmid
Hi, are there any news on this? I'm too scary about upgrading our installation! BR Florian Von: "Sharon Gratch" An: "Florian Schmid" , "Ryan Barry" , "Lucia Jelinkova" CC: "users" Gesendet: Dienstag, 20. August 2019 11:00:41 Betreff: Re: [ovirt-users] Re: engine.log flooded with

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

2019-08-20 Thread Staniforth, Paul
Hello, 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. Regards, Paul S.

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

2019-08-20 Thread Sharon Gratch
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

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

2019-08-20 Thread Florian Schmid
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

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

2019-08-17 Thread Matthias Leopold
https://bugzilla.redhat.com/show_bug.cgi?id=1742924 Am 13.08.19 um 19:14 schrieb Sharon Gratch: 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

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

2019-08-13 Thread 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

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

2019-08-13 Thread Sharon Gratch
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

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

2019-08-13 Thread Matthias Leopold
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