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

2019-09-02 Thread Florian Schmid
Betreff: Re: [ovirt-users] Re: engine.log flooded with "Field 'foo' can not be updated when status is 'Up'" Hi, [ mailto:rba...@redhat.com | @Ryan Barry ] , [ mailto:ljeli...@redhat.com | @Lucia Jelinkova ] - is the possible to fix [ https://bugzilla.redhat.com

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

2019-08-20 Thread Staniforth, Paul
aul S. From: Sharon Gratch 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<mailto:rba...@redha

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

2019-08-20 Thread Sharon Gratch
ember or beginning > of October. > > BR Florian > > > -- > *Von: *"Sharon Gratch" > *An: *"Matthias Leopold" > *CC: *"p staniforth" , "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'"

2019-08-20 Thread Florian Schmid
: "p staniforth" , "users" 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 logg

[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 th

[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 VM

[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 not

[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 s