[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 "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/show_bug.cgi?id=1742924 | 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 < [ mailto:fsch...@ubimet.com | 
fsch...@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" < [ mailto:sgra...@redhat.com | sgra...@redhat.com ] > 
An: "Matthias Leopold" < [ mailto:matthias.leop...@meduniwien.ac.at | 
matthias.leop...@meduniwien.ac.at ] > 
CC: "p staniforth" < [ mailto:p.stanifo...@leedsbeckett.ac.uk | 
p.stanifo...@leedsbeckett.ac.uk ] >, "users" < [ mailto:users@ovirt.org | 
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 < [ 
mailto:matthias.leop...@meduniwien.ac.at | matthias.leop...@meduniwien.ac.at ] 
> wrote: 

BQ_BEGIN
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 
> 

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



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, @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 
mailto:fsch...@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" mailto:sgra...@redhat.com>>
An: "Matthias Leopold" 
mailto:matthias.leop...@meduniwien.ac.at>>
CC: "p staniforth" 
mailto:p.stanifo...@leedsbeckett.ac.uk>>, 
"users" mailto: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 
mailto:matthias.leop...@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  
> 

[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 at 10:31 AM Florian Schmid  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" 
> *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'"
>
> 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.leop...@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'
>> > 

[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 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"  
An: "Matthias Leopold"  
CC: "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 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 < [ 
mailto:matthias.leop...@meduniwien.ac.at | matthias.leop...@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 
> 

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

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

[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 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.leop...@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 

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