[ovirt-users] Re: hosted engine setup, iSCSI no LUNs shown

[Simone Tiraboschi]

Hi,
can you please share /var/log/vdsm/vdsm.log from the deployment time?

On Tue, Aug 20, 2019 at 6:35 PM  wrote:

> I'm trying to setup the hosted engine on top of iSCSI storage. It
> successfully logs in and gets the target, however the process errors out
> claiming there are no LUNs. But if you look on the host, the disks were
> added to the system.
>
> [ INFO  ] TASK [ovirt.hosted_engine_setup : iSCSI discover with REST API]
> [ INFO  ] ok: [localhost]
>   The following targets have been found:
> [1] iqn.2001-04.com.billdurr.durrnet.vm-int:vmdata
> TPGT: 1, portals:
> 192.168.47.10:3260
>
>   Please select a target (1) [1]: 1
> [ INFO  ] Getting iSCSI LUNs list
> ...
> [ INFO  ] TASK [ovirt.hosted_engine_setup : Get iSCSI LUNs]
> [ INFO  ] ok: [localhost]
> [ ERROR ] Cannot find any LUN on the selected target
> [ ERROR ] Unable to get target list
>
> Here's what the config in targetcli looks like
> [root@vm1 ~]# targetcli ls
> o- / .
> [...]
>   o- backstores ..
> [...]
>   | o- block .. [Storage
> Objects: 2]
>   | | o- p_iscsi_lun1 .. [/dev/drbd0 (62.0GiB) write-thru
> activated]
>   | | | o- alua ... [ALUA
> Groups: 1]
>   | | |   o- default_tg_pt_gp ... [ALUA state:
> Active/optimized]
>   | | o- p_iscsi_lun2 . [/dev/drbd1 (310.6GiB) write-thru
> activated]
>   | |   o- alua ... [ALUA
> Groups: 1]
>   | | o- default_tg_pt_gp ... [ALUA state:
> Active/optimized]
>   | o- fileio . [Storage
> Objects: 0]
>   | o- pscsi .. [Storage
> Objects: 0]
>   | o- ramdisk  [Storage
> Objects: 0]
>   o- iscsi 
> [Targets: 1]
>   | o- iqn.2001-04.com.billdurr.durrnet.vm-int:vmdata 
> [TPGs: 1]
>   |   o- tpg1 .. [gen-acls,
> no-auth]
>   | o- acls ..
> [ACLs: 0]
>   | o- luns ..
> [LUNs: 2]
>   | | o- lun0 . [block/p_iscsi_lun1 (/dev/drbd0)
> (default_tg_pt_gp)]
>   | | o- lun1 . [block/p_iscsi_lun2 (/dev/drbd1)
> (default_tg_pt_gp)]
>   | o- portals 
> [Portals: 1]
>   |   o- 192.168.47.10:3260
> ... [OK]
>   o- loopback .
> [Targets: 0]
>   o- srpt .
> [Targets: 0]
>
> The two LUNs show up on the host after the hosted engine setup tries to
> enumerate the LUNs for the target
> [root@vm1 ~]# lsscsi
> [0:0:0:0]storage HP   P420i8.32  -
> [0:1:0:0]diskHP   LOGICAL VOLUME   8.32  /dev/sda
> [0:1:0:1]diskHP   LOGICAL VOLUME   8.32  /dev/sdb
> [0:1:0:2]diskHP   LOGICAL VOLUME   8.32  /dev/sdc
> [11:0:0:0]   diskLIO-ORG  p_iscsi_lun1 4.0   /dev/sdd
> [11:0:0:1]   diskLIO-ORG  p_iscsi_lun2 4.0   /dev/sde
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/MGPCIAT7QTH7A7EHIC2RBDTZTH6HB4IH/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/G67SIUEDKDJUR7Z3XW2AM4GFZFQZ4GW4/

[ovirt-users] engine-setup is failing in fedora30

[Gobinda Das]

Hi,
 I am facing issue to do engine-setup in fedora30.

[godas@godas ovirt-engine]$ $HOME/ovirt-engine/bin/engine-setup
[ INFO  ] Stage: Initializing
  Setup was run under unprivileged user this will produce
development installation do you wish to proceed? (Yes, No) [No]: Yes
[ INFO  ] Stage: Environment setup
  Configuration files:
['/home/gobinda/ovirt-engine/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf']
  Log file:
/home/gobinda/ovirt-engine/var/log/ovirt-engine/setup/ovirt-engine-setup-20190821121001-bkc6we.log
  Version: otopi-1.8.1_master
(otopi-1.8.1-0.0.master.20190228094531.git1953bdc.fc30)
[ INFO  ] Stage: Environment packages setup
[ INFO  ] Stage: Programs detection
[ INFO  ] Stage: Environment setup (late)
[ INFO  ] Stage: Environment customization

  --== PRODUCT OPTIONS ==--


  --== PACKAGES ==--


  --== NETWORK CONFIGURATION ==--

[WARNING] Failed to resolve godas.lab.eng.blr.redhat.com using DNS, it can
be resolved only locally

  --== DATABASE CONFIGURATION ==--


  --== OVIRT ENGINE CONFIGURATION ==--

  Perform full vacuum on the engine database engine@localhost?
  This operation may take a while depending on this setup health
and the
  configuration of the db vacuum process.
  See https://www.postgresql.org/docs/10/sql-vacuum.html
  (Yes, No) [No]:

  --== STORAGE CONFIGURATION ==--


  --== PKI CONFIGURATION ==--


  --== APACHE CONFIGURATION ==--


  --== SYSTEM CONFIGURATION ==--


  --== MISC CONFIGURATION ==--


  --== END OF CONFIGURATION ==--

[ INFO  ] Stage: Setup validation

  --== CONFIGURATION PREVIEW ==--

  Default SAN wipe after delete   : False
  Host FQDN   :
godas.lab.eng.blr.redhat.com
  Set up Cinderlib integration: False
  Engine database host: localhost
  Engine database port: 5432
  Engine database secured connection  : False
  Engine database host name validation: False
  Engine database name: engine
  Engine database user name   : engine
  Engine installation : True
  PKI organization: lab.eng.blr.redhat.com
  Set up ovirt-provider-ovn   : False
  Configure WebSocket Proxy   : True
  Configure VMConsole Proxy   : True

  Please confirm installation settings (OK, Cancel) [OK]: OK
[ INFO  ] Checking the Engine database consistency
[ INFO  ] Stage: Transaction setup
[ INFO  ] Stage: Misc configuration (early)
[ INFO  ] Stage: Package installation
[ INFO  ] Stage: Misc configuration
[ INFO  ] Upgrading CA
[ INFO  ] Configuring WebSocket Proxy
[ INFO  ] Backing up database localhost:engine to
'/home/gobinda/ovirt-engine/var/lib/ovirt-engine/backups/engine-20190821121010.0iip56rw.dump'.
[ INFO  ] Creating/refreshing Engine database schema
  Unregistering existing client registration info.
[ INFO  ] Generating post install configuration file
'/home/gobinda/ovirt-engine/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf'
[ ERROR ] Failed to execute stage 'Misc configuration': a bytes-like object
is required, not 'str'
[ INFO  ] Rolling back database schema
[ INFO  ] Clearing Engine database engine
[ INFO  ] Restoring Engine database engine
[ INFO  ] Restoring file
'/home/gobinda/ovirt-engine/var/lib/ovirt-engine/backups/engine-20190821121010.0iip56rw.dump'
to database localhost:engine.
[ ERROR ] Engine database rollback failed: cannot use a string pattern on a
bytes-like object
[ INFO  ] Stage: Clean up
  Log file is located at
/home/gobinda/ovirt-engine/var/log/ovirt-engine/setup/ovirt-engine-setup-20190821121001-bkc6we.log
[ INFO  ] Generating answer file
'/home/gobinda/ovirt-engine/var/lib/ovirt-engine/setup/answers/20190821121039-setup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed

I*t was working before but the moment i pulled latest master code the issue
started.*

-- 


Thanks,
Gobinda
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/TNCLKNANFXON5R5TBUWWWLYTBCVHUVXG/

[ovirt-users] Re: When I added the ovirt-node to the ovirt-engine through the web management interface, I get the following error: Host 172.16.41.100 installation failed. Failed to configure managemen

[wangyu13476969128]

hi  Hongyu Du：

This  blog:
https://www.linuxtechi.com/enable-nested-virtualization-kvm-centos-7-rhel-7/

My virtual machine is stuck in XenServer.

There is not kvm_intel or kvm_amd  in /sys/module  directory.

[root@ovirt-node1 ~]# cat /sys/module/kvm
cat: /sys/module/kvm: No such file or directory

How should I do it next?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/5HZXCXBHB7UOLAKKNTZX4G6CHOJQIKB2/

[ovirt-users] Re: When I added the ovirt-node to the ovirt-engine through the web management interface, I get the following error: Host 172.16.41.100 installation failed. Failed to configure managemen

[du_hon...@yeah.net]

hi
please follow this blog
https://www.linuxtechi.com/enable-nested-virtualization-kvm-centos-7-rhel-7/



Regards
Hongyu Du
 
From: wangyu13476969128
Date: 2019-08-21 11:32
To: users
Subject: [ovirt-users] Re: When I added the ovirt-node to the ovirt-engine 
through the web management interface, I get the following error: Host 
172.16.41.100 installation failed. Failed to configure management network on 
the host. Host 172.16.41.100 does not comply with the cluster cluster-kvm 
networks, the following networks are missing on host: 'ovirtmgmt'
Hi Hongyu Du:
How can I check if my virtual machine supports nx?
 
[root@ovirt-node1 bin]# cat /proc/cpuinfo |grep nx
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush acpi mmx fxsr sse sse2 ht syscall nx pdpe1gb rdtscp lm 
constant_tsc rep_good nopl eagerfpu pni pclmulqdq ssse3 fma cx16 pcid sse4_1 
sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
hypervisor lahf_lm abm 3dnowprefetch intel_ppin ssbd ibrs ibpb stibp fsgsbase 
tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap 
clflushopt clwb xsaveopt xsavec xgetbv1 pku ospke spec_ctrl intel_stibp 
flush_l1d
 
The "nx"  in  /proc/cpuinfo . 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/BQ4RCF3ODSVCPDSNXV5FBNLQSCRIG5UU/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/QRB3SXZA3ATYJESSOLQOFWNLJP5HE22D/

[ovirt-users] Re: When I added the ovirt-node to the ovirt-engine through the web management interface, I get the following error: Host 172.16.41.100 installation failed. Failed to configure managemen

[wangyu13476969128]

Hi Hongyu Du:
How can I check if my virtual machine supports nx?

[root@ovirt-node1 bin]# cat /proc/cpuinfo |grep nx
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush acpi mmx fxsr sse sse2 ht syscall nx pdpe1gb rdtscp lm 
constant_tsc rep_good nopl eagerfpu pni pclmulqdq ssse3 fma cx16 pcid sse4_1 
sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
hypervisor lahf_lm abm 3dnowprefetch intel_ppin ssbd ibrs ibpb stibp fsgsbase 
tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap 
clflushopt clwb xsaveopt xsavec xgetbv1 pku ospke spec_ctrl intel_stibp 
flush_l1d

The "nx"  in  /proc/cpuinfo . 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/BQ4RCF3ODSVCPDSNXV5FBNLQSCRIG5UU/

[ovirt-users] Re: When I added the ovirt-node to the ovirt-engine through the web management interface, I get the following error: Host 172.16.41.100 installation failed. Failed to configure managemen

[du_hon...@yeah.net]

hi wangyu
your virtual machine need support nested  virtual

Regards
Hongyu Du
 
From: wangyu13476969128
Date: 2019-08-21 09:34
To: users
Subject: [ovirt-users] Re: When I added the ovirt-node to the ovirt-engine 
through the web management interface, I get the following error: Host 
172.16.41.100 installation failed. Failed to configure management network on 
the host. Host 172.16.41.100 does not comply with the cluster cluster-kvm 
networks, the following networks are missing on host: 'ovirtmgmt'
Thanks very much for Kaustav Majumder!
 
Follow the steps you taught me：
 
1. Server1 install ovirt-engine
2. Server2 install ovirt-node
3. Set bridge network using the link on ovirt-node (
https://www.ovirt.org/develop/developer-guide/vdsm/installing-vdsm-from-r...
)
4. Add ovirt-node to ovirt-engine
 
Server 1  is  a  Dell R740 Server.
Server 2  is  a  virtual machine.
 
The OS of Server1  is  4.3.5.5-1.el7
The OS of Server2  is ovirt-node-ng-installer-4.3.5-2019073010.el7.iso
 
In Step 3:  
 
When I use command "yum install -y vdsm vdsm-cli"  on ovirt-node.
 
It show :
"
http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-7/noarch/repodata/repomd.xml:
 [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
Excluding 46 updates due to versionlock (use "yum versionlock status" to show 
them)
Nothing to do
"
 
Then I check the version of vdsm :
 
[root@ovirt-node1 ~]# rpm -qa|grep vdsm
vdsm-http-4.30.24-1.el7.noarch
vdsm-hook-fcoe-4.30.24-1.el7.noarch
vdsm-yajsonrpc-4.30.24-1.el7.noarch
vdsm-python-4.30.24-1.el7.noarch
vdsm-hook-vmfex-dev-4.30.24-1.el7.noarch
vdsm-hook-ethtool-options-4.30.24-1.el7.noarch
vdsm-api-4.30.24-1.el7.noarch
vdsm-common-4.30.24-1.el7.noarch
vdsm-network-4.30.24-1.el7.x86_64
vdsm-jsonrpc-4.30.24-1.el7.noarch
vdsm-hook-vhostmd-4.30.24-1.el7.noarch
vdsm-hook-openstacknet-4.30.24-1.el7.noarch
vdsm-4.30.24-1.el7.x86_64
vdsm-gluster-4.30.24-1.el7.x86_64
vdsm-client-4.30.24-1.el7.noarch
 
 
Then I add ovirt-node1 to ovirt-engine: 
It report:
 
Host ovirt-node1 installation failed. Failed to configure management network on 
the host.
 
VDSM ovirt-node1 command Get Host Capabilities failed: Internal JSON-RPC error: 
{'reason': "invalid argument: KVM is not supported by '/usr/libexec/qemu-kvm' 
on this host"}
 
So my question is what's the problem ?  How can I slove this problem ?
 
Thank you very much!
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/52IQL7UQMA6VRZ4W7GXCZ5KU7RA7FBI2/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/HV7VJAOCNPVDPM5CJYMBNXHGLEH4FBSJ/

[ovirt-users] Re: When I added the ovirt-node to the ovirt-engine through the web management interface, I get the following error: Host 172.16.41.100 installation failed. Failed to configure managemen

[wangyu13476969128]

The content of  vdsm.log  on  ovirt-node 1  is :

libvirtError: invalid argument: KVM is not supported by '/usr/libexec/qemu-kvm' 
on this host
2019-08-21 09:17:48,329+0800 INFO  (jsonrpc/3) [jsonrpc.JsonRpcServer] RPC call 
Host.getCapabilities failed (error -32603) in 0.07 seconds (__init__:312)
2019-08-21 09:17:49,004+0800 INFO  (jsonrpc/4) [api.host] START getAllVmStats() 
from=:::172.16.90.10,43280 (api:48)
2019-08-21 09:17:49,005+0800 INFO  (jsonrpc/4) [api.host] FINISH getAllVmStats 
return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} 
from=:::172.16.90.10,43280 (api:54)
2019-08-21 09:17:49,005+0800 INFO  (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC call 
Host.getAllVmStats succeeded in 0.01 seconds (__init__:312)
2019-08-21 09:17:49,348+0800 INFO  (jsonrpc/5) [api.host] START 
getCapabilities() from=:::172.16.90.10,43280 (api:48)
2019-08-21 09:17:49,355+0800 INFO  (jsonrpc/5) [api.host] FINISH 
getCapabilities error=invalid argument: KVM is not supported by 
'/usr/libexec/qemu-kvm' on this host from=:::172.16.90.10,43280 (api:52)
2019-08-21 09:17:49,355+0800 ERROR (jsonrpc/5) [jsonrpc.JsonRpcServer] Internal 
server error (__init__:350)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in 
_handle_request
res = method(**params)
  File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 194, in 
_dynamicMethod
result = fn(*methodArgs)
  File "", line 2, in getCapabilities
  File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method
ret = func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1371, in 
getCapabilities
c = caps.get()
  File "/usr/lib/python2.7/site-packages/vdsm/host/caps.py", line 94, in get
machinetype.compatible_cpu_models())
  File "/usr/lib/python2.7/site-packages/vdsm/common/cache.py", line 43, in 
__call__
value = self.func(*args)
  File "/usr/lib/python2.7/site-packages/vdsm/machinetype.py", line 142, in 
compatible_cpu_models
all_models = domain_cpu_models(c, arch, cpu_mode)
  File "/usr/lib/python2.7/site-packages/vdsm/machinetype.py", line 97, in 
domain_cpu_models
domcaps = conn.getDomainCapabilities(None, arch, None, virt_type, 0)
  File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", 
line 131, in wrapper
ret = f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in 
wrapper
return func(inst, *args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3852, in 
getDomainCapabilities
if ret is None: raise libvirtError ('virConnectGetDomainCapabilities() 
failed', conn=self)
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/ZFE5UW273VONSLBYHTXZJCC3KT32HOBD/

[ovirt-users] Re: VDSM ovirt-node-2 command Get Host Capabilities failed: Internal JSON-RPC error: {'reason': "invalid argument: KVM is not supported by '/usr/libexec/qemu-kvm' on this host"}

[wangyu13476969128]

Hi  Sandro Bonazzola:
 Where is the path to the SOS report file  
of  ovirt-node-2 host?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/BWFPHW725HB2LX6MIVTVZBWD7IVMTIEE/

[ovirt-users] Re: When I added the ovirt-node to the ovirt-engine through the web management interface, I get the following error: Host 172.16.41.100 installation failed. Failed to configure managemen

[wangyu13476969128]

Thanks very much for Kaustav Majumder!

Follow the steps you taught me：

1. Server1 install ovirt-engine
2. Server2 install ovirt-node
3. Set bridge network using the link on ovirt-node (
https://www.ovirt.org/develop/developer-guide/vdsm/installing-vdsm-from-r...
)
4. Add ovirt-node to ovirt-engine

Server 1  is  a  Dell R740 Server.
Server 2  is  a  virtual machine.

The OS of Server1  is  4.3.5.5-1.el7
The OS of Server2  is ovirt-node-ng-installer-4.3.5-2019073010.el7.iso

In Step 3:  

When I use command "yum install -y vdsm vdsm-cli"  on ovirt-node.

It show :
"
http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-7/noarch/repodata/repomd.xml:
 [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
Excluding 46 updates due to versionlock (use "yum versionlock status" to show 
them)
Nothing to do
"

Then I check the version of vdsm :

[root@ovirt-node1 ~]# rpm -qa|grep vdsm
vdsm-http-4.30.24-1.el7.noarch
vdsm-hook-fcoe-4.30.24-1.el7.noarch
vdsm-yajsonrpc-4.30.24-1.el7.noarch
vdsm-python-4.30.24-1.el7.noarch
vdsm-hook-vmfex-dev-4.30.24-1.el7.noarch
vdsm-hook-ethtool-options-4.30.24-1.el7.noarch
vdsm-api-4.30.24-1.el7.noarch
vdsm-common-4.30.24-1.el7.noarch
vdsm-network-4.30.24-1.el7.x86_64
vdsm-jsonrpc-4.30.24-1.el7.noarch
vdsm-hook-vhostmd-4.30.24-1.el7.noarch
vdsm-hook-openstacknet-4.30.24-1.el7.noarch
vdsm-4.30.24-1.el7.x86_64
vdsm-gluster-4.30.24-1.el7.x86_64
vdsm-client-4.30.24-1.el7.noarch


Then I add ovirt-node1 to ovirt-engine: 
It report:

Host ovirt-node1 installation failed. Failed to configure management network on 
the host.

VDSM ovirt-node1 command Get Host Capabilities failed: Internal JSON-RPC error: 
{'reason': "invalid argument: KVM is not supported by '/usr/libexec/qemu-kvm' 
on this host"}

So my question is what's the problem ?  How can I slove this problem ?

Thank you very much!
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/52IQL7UQMA6VRZ4W7GXCZ5KU7RA7FBI2/

[ovirt-users] Re: Hyperconverged setup ovirt 4.3.x using ansible?

[adrianquintero]

Thanks, I am researching and looks promising...
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/YIKKPLNZNBORMIRXUOMFTUW62INFJBQI/

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

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

[ovirt-users] hosted engine setup, iSCSI no LUNs shown

[billyburly]

I'm trying to setup the hosted engine on top of iSCSI storage. It successfully 
logs in and gets the target, however the process errors out claiming there are 
no LUNs. But if you look on the host, the disks were added to the system.

[ INFO  ] TASK [ovirt.hosted_engine_setup : iSCSI discover with REST API]
[ INFO  ] ok: [localhost]
  The following targets have been found:
[1] iqn.2001-04.com.billdurr.durrnet.vm-int:vmdata
TPGT: 1, portals:
192.168.47.10:3260

  Please select a target (1) [1]: 1
[ INFO  ] Getting iSCSI LUNs list
...
[ INFO  ] TASK [ovirt.hosted_engine_setup : Get iSCSI LUNs]
[ INFO  ] ok: [localhost]
[ ERROR ] Cannot find any LUN on the selected target
[ ERROR ] Unable to get target list

Here's what the config in targetcli looks like
[root@vm1 ~]# targetcli ls
o- / . [...]
  o- backstores .. [...]
  | o- block .. [Storage Objects: 2]
  | | o- p_iscsi_lun1 .. [/dev/drbd0 (62.0GiB) write-thru activated]
  | | | o- alua ... [ALUA Groups: 1]
  | | |   o- default_tg_pt_gp ... [ALUA state: Active/optimized]
  | | o- p_iscsi_lun2 . [/dev/drbd1 (310.6GiB) write-thru activated]
  | |   o- alua ... [ALUA Groups: 1]
  | | o- default_tg_pt_gp ... [ALUA state: Active/optimized]
  | o- fileio . [Storage Objects: 0]
  | o- pscsi .. [Storage Objects: 0]
  | o- ramdisk  [Storage Objects: 0]
  o- iscsi  [Targets: 1]
  | o- iqn.2001-04.com.billdurr.durrnet.vm-int:vmdata  [TPGs: 1]
  |   o- tpg1 .. [gen-acls, no-auth]
  | o- acls .. [ACLs: 0]
  | o- luns .. [LUNs: 2]
  | | o- lun0 . [block/p_iscsi_lun1 (/dev/drbd0) (default_tg_pt_gp)]
  | | o- lun1 . [block/p_iscsi_lun2 (/dev/drbd1) (default_tg_pt_gp)]
  | o- portals  [Portals: 1]
  |   o- 192.168.47.10:3260 ... [OK]
  o- loopback . [Targets: 0]
  o- srpt . [Targets: 0]

The two LUNs show up on the host after the hosted engine setup tries to 
enumerate the LUNs for the target
[root@vm1 ~]# lsscsi
[0:0:0:0]storage HP   P420i8.32  -
[0:1:0:0]diskHP   LOGICAL VOLUME   8.32  /dev/sda
[0:1:0:1]diskHP   LOGICAL VOLUME   8.32  /dev/sdb
[0:1:0:2]diskHP   LOGICAL VOLUME   8.32  /dev/sdc
[11:0:0:0]   diskLIO-ORG  p_iscsi_lun1 4.0   /dev/sdd
[11:0:0:1]   diskLIO-ORG  p_iscsi_lun2 4.0   /dev/sde
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/MGPCIAT7QTH7A7EHIC2RBDTZTH6HB4IH/

[ovirt-users] Re: ovirt node install

[thomas]

same result on 4.3.6-rc1, and the manual update to ovirt-node-ng-nodectl noarch 
 4.4.0-0.20190820.0.el7 fixes it there.

Didn't try it on the 'production' 4.3.5 variant, but would assume it works 
there, too.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/ROBJOTLKWFACTAOTQ2SKF6YYJER6YYLR/

[ovirt-users] Re: ovn networking

[Miguel Duarte de Mora Barroso]

On Mon, Aug 19, 2019 at 12:47 PM Staniforth, Paul
 wrote:
>
> Thanks Miguel,
>  I'm using openvswitch-ovn-common-2.11.0-4.el7.x86_64

I hoped this would be gone in version 2.11, but, seems like the
openvswitch build hasn't been updated for quite some time
(2019-03-20).

Unfortunately I cannot provide an ETA on a newer OVS build.

>
> I'll just ignore as I don't want to create any dependency problems.
>
> Regards,
>Paul S.
>
> 
> From: Miguel Duarte de Mora Barroso 
> Sent: 16 August 2019 12:09
> To: Staniforth, Paul
> Cc: users@ovirt.org
> Subject: Re: [ovirt-users] ovn networking
>
> On Wed, Aug 14, 2019 at 9:09 AM Staniforth, Paul
>  wrote:
> >
> > Hello
> >
> >   I the latest release of the engine 4.3.5.5-1.el7
> >
> > ovn-nbctl  show
> >
> > ovn-sbctl  show
> >
> >
> > both seem to work but produce the errors
> >
> >
> > net_mlx5: cannot load glue library: libibverbs.so.1: cannot open shared 
> > object file: No such file or directory
> > net_mlx5: cannot initialize PMD due to missing run-time dependency on 
> > rdma-core libraries (libibverbs, libmlx5)
> > PMD: net_mlx4: cannot load glue library: libibverbs.so.1: cannot open 
> > shared object file: No such file or directory
> > PMD: net_mlx4: cannot initialize PMD due to missing run-time dependency on 
> > rdma-core libraries (libibverbs, libmlx4)
> >
> >
> > should libibverbs be a dependency?
>
> It shouldn't, since has no use in the engine node - other than
> silencing those errors.
>
> Which OVS / OVN version are you using ?
>
> >
> > Paul S.
> > To view the terms under which this email is distributed, please go to:-
> > http://leedsbeckett.ac.uk/disclaimer/email/
> >
> > ___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-le...@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%7Cc27b535313664fe3b0f508d7223a2bfc%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637015505546807557&sdata=DafifdFwfFumf10G6KxdAm2GxZNo%2BL%2FuQlNcT0c9Pxc%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%7Cc27b535313664fe3b0f508d7223a2bfc%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637015505546817549&sdata=O3l6rooWKILYsyPAQWDPKuwQFyoOLFG7IbT7j5YiPZ4%3D&reserved=0
> > List Archives: 
> > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovirt.org%2Farchives%2Flist%2Fusers%40ovirt.org%2Fmessage%2FJ4T4YFAVYOMASVV3ACCNVFGF3YSAT3N4%2F&data=02%7C01%7CP.Staniforth%40leedsbeckett.ac.uk%7Cc27b535313664fe3b0f508d7223a2bfc%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637015505546817549&sdata=WCOzfW2gI3H5a8E85WLDo2zsW0AEvTKlcqWdKa74AJ4%3D&reserved=0
> To view the terms under which this email is distributed, please go to:-
> http://leedsbeckett.ac.uk/disclaimer/email/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/OJBLUKJFBESRCCIMAMUFNSLAA7ZC4V65/

[ovirt-users] Re: numa pinning for high performance

[Sharon Gratch]

Hi,

Sorry for the late reply.

The recommended setting for High Performance VMs is generally depended on
many parameters and on what your VM is required to do (I/O or compute
load), but generally and based on the setting that you sent then I have few
comments for configuration tuning:

   - *Host's NUMA pinning topology* - can you please send your host's NUMA
   topology? I can see that the host is set to have 2 NUMA nodes (2 sockets)
   with 20 CPUs in each NUMA node, but how those CPUs are divided among the
   NUMA nodes?

An example for host's NUMA topology can be:
NUMA node0 CPU(s):   0-19
NUMA node1 CPU(s):   20-39


   - *Virtual NUMA pinning topology* - currently I can see that you set
   your VM to run with 8 virtual NUMA nodes while your host is configured to
   run with only 2 physical NUMA nodes. I recommend you to change the "NUMA
   Node Count" value to 2 since there is no reason to set number of virtual
   NUMA nodes bigger than the number of physical NUMA nodes.

Then, please click on "NUMA pinning" button in UI and pin virtual NUMA0 to
"Socket 0" and virtual NUMA1 to "Socket 1" or vice versa (the order depends
on your CPU pinning settings which is detailed in next bullet).

   - *CPU pinning topology* - your current CPU pinning is set to:
   "0#0_1#1". This means that virtual CPU0 is pinned to physical CPU0 and
   virtual CPU1 is pinned to physical CPU1. But what about other VM's six
   VCPUs?

Therefore, I recommend you to set your "CPU pinning topology" field such
that each one of the 8 virtual CPUs is pinned to a physical CPU:
The first four virtual CPUs CPU0-vCPU3 will be pinned to 4 physical CPUs
within the first host's NUMA node (i.e. CPUs in Socket 0).
And the other group of four virtual CPUs vCPU4-vCPU7 will be pinned to four
CPUs in second host's NUMA node(i.e. CPUs in Socket 1).

   - There are other recommended settings for VM performance improvements
   like setting *Huge pages* for the VM (via the "Custom Properties" tab)
   but that requires your host to support huge pages as well.

Regards,
Sharon


On Thu, Aug 15, 2019 at 1:14 AM Vincent Royer  wrote:

> Haha, oh.  Don't I feel dumb.  So all the settings are good then?
>
> On Wed, Aug 14, 2019, 2:07 PM Oliver Riesener <
> oliver.riese...@hs-bremen.de> wrote:
>
>> Hi Vincent,
>>
>> nice setup. ;-)
>>
>> The column %guest with (800% or 20% of all) locks good for me.
>> The rest cores are %idle.
>>
>> Best regards
>>
>> Oliver
>>
>>
>>
>> Am 14.08.2019 um 10:04 schrieb Vincent Royer :
>>
>> Is there a good place to learn about cpu pinning and the various settings?
>>
>> I've built a test VM and am trying to understand
>>
>> - I've given it 2 cpus, 4 cores each, 1 thread per core.
>> - The VM is pinned to a specific host with passthrough cpu enabled
>> - numa pinning, first 4 cores on physical socket 1 and the next 4 on
>> physical socket 2
>> - The host has two sockets each with 20 core cpus
>>
>> I would expect to see a load applied on 8 of the 40 cores on the host
>> during testing. Instead it seems like 32 of 40 cores are working at 100%.
>> What are the effects of this on the performance of the vm?
>>
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>> 
>>
>>
>>
>>
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@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/WMHTN7KU5X5MSUE6FZLVBE77DYY4TJAR/
>>
>>
>> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/E737HH5FXLYOQQAMCIN5WMVYU4WOO65D/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/VM7EIY6S2PL5EJKC3O6T5NYIG2D2J5R4/

[ovirt-users] Re: Need to enable STP on ovirt bridges

[Curtis E. Combs Jr.]

I can see, just through a series of searches, that you can configure ovirt
to use a variety of things. I've configured many VMWare clusters before, so
having a (Cisco calls them) trunked port or (what other people call them)
ports in "tagged mode" would be nice, but like I was saying: I can't even
speak directly to the co-lo people, much less ask them to set a port to
access multiple VLANs.

So, going at this just by trying to follow the docs, I simply add a
"network" in the GUI and stick the port on it in "Setup Host Networks". On
each host, I named the "network" the same so that it satisfies the
requirement for Live Migration. So, 3 hosts, 2 networks per-host. Network 1
is named "ovirtmgmt", the other is named "int-1gb-10.15.11". I thought that
this was required because a VM must attach to the same networks if it is to
migrate because of load balancing, failover or just to migrate. So, two
links, two networks - VMs can use the switch to access the local network
and the wider network with the same configuration.

As you can imagine, having the ports become un-linked without STP and
having them work properly with it, seemed to indicate that STP was the
issue. If STP is not the true culprit, then I really don't know what else
it can be...but in either case, it seems like there really should be an
option in the interface to enable or disable it, considering the bridge
utilities literally have it as a first-level option and it's probably one
of the more common networking configurations

Again, if there's some other way to do this, please, please do let me know.

Thanks again, Tony!
cecjr

On Tue, Aug 20, 2019 at 4:51 AM Curtis E. Combs Jr. 
wrote:

> Oh, I'm just using the standard Linux bridges. I believe in ovirt
> nomenclature they're called "legacy bridges". This is not by any real
> choice but just what is created by default, I believe. In the first link
> you sent, they are calling them "Linux legacy networking model" - though I
> only have 2 options when I make a new switch - the default and (it says)
> "openvswitch (experimental)"
>
> On Tue, Aug 20, 2019 at 4:47 AM Tony Pearce  wrote:
>
>> No - no recommendations from me to use either. I took it that you were
>> using ovs bridge as I was not aware of another bridge. The only other
>> option I was aware of if what I am using, vlan interfaces and kernel vlan
>> tags. If you could share a link to what you're using, I would be keen to
>> read up on it to know more.
>>
>> *Tony Pearce*
>>
>>
>> On Tue, 20 Aug 2019 at 16:27, Curtis E. Combs Jr. 
>> wrote:
>>
>>> Tony,
>>>
>>> Well, thank you for that, but I'm not using openvswitchs, I'm just using
>>> regular bridges. Are you suggesting that I do?
>>>
>>> From what I can see in the interface they have "(experimental)" marked
>>> on them and we'd like to see production with this at some point.
>>>
>>> None of my ports are trunking between VLANs - they only have one in
>>> untagged mode - and there's only 2 VLANs here, one per-port.
>>>
>>> Thanks again!
>>> cecjr
>>>
>>>
>>>
>>> On Mon, Aug 19, 2019 at 10:36 PM Tony Pearce  wrote:
>>>
 A couple of links I found helpful, thought I'd send them over
 http://therandomsecurityguy.com/openvswitch-cheat-sheet/

 https://ovirt.org/develop/release-management/features/network/openvswitch/native-openvswitch.html

 With STP off, if the network is detecting a loop then it will have to
 block a link. With STP on I guess it's allowing the network to remain
 forwarding and the blocking to occur elsewhere. 👍


 Tony Pearce

 On Tue, 20 Aug 2019 at 10:12, Curtis E. Combs Jr. 
 wrote:
 >
 > Cool, I can capture some packets tomorrow when I'm in the office and
 > see how that compares...
 >
 > But, yea, it's a hassle to get them to respond IF they do, so the only
 > real options I'm going to have are what I can do with my servers from
 the OS. No
 > physical access. No nice DC guy to help me out.
 >
 >
 > On Mon, Aug 19, 2019 at 10:06 PM Tony Pearce 
 wrote:
 > >
 > > :) They might be using Cisco's per-vlan spanning tree on the network
 > > side. It is possible to capture the packets coming in from the
 network
 > > and confirm that.
 > >
 > > Attached screenshot of wireshark for you for reference.
 > >
 > > Glad you're all working :)
 > >
 > > Regards
 > >
 > > Tony Pearce
 > >
 > >
 > >
 > > On Tue, 20 Aug 2019 at 09:52, Curtis E. Combs Jr. <
 ej.alb...@gmail.com> wrote:
 > > >
 > > > Hey Tony!
 > > >
 > > > I only know the basics of Spanning Tree. At the current moment the
 > > > only way to get migrations to work at all without breaking the
 whole
 > > > oVirt cluster is to have it on. After changing it according to
 Paul's
 > > > instruction, it works like it has never worked before. Every
 migration
 > > > event was successful. Whereas before and even 

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

[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'
>> > 2019-08-13

[ovirt-users] Re: Need to enable STP on ovirt bridges

[Curtis E. Combs Jr.]

Oh, I'm just using the standard Linux bridges. I believe in ovirt
nomenclature they're called "legacy bridges". This is not by any real
choice but just what is created by default, I believe. In the first link
you sent, they are calling them "Linux legacy networking model" - though I
only have 2 options when I make a new switch - the default and (it says)
"openvswitch (experimental)"

On Tue, Aug 20, 2019 at 4:47 AM Tony Pearce  wrote:

> No - no recommendations from me to use either. I took it that you were
> using ovs bridge as I was not aware of another bridge. The only other
> option I was aware of if what I am using, vlan interfaces and kernel vlan
> tags. If you could share a link to what you're using, I would be keen to
> read up on it to know more.
>
> *Tony Pearce*
>
>
> On Tue, 20 Aug 2019 at 16:27, Curtis E. Combs Jr. 
> wrote:
>
>> Tony,
>>
>> Well, thank you for that, but I'm not using openvswitchs, I'm just using
>> regular bridges. Are you suggesting that I do?
>>
>> From what I can see in the interface they have "(experimental)" marked on
>> them and we'd like to see production with this at some point.
>>
>> None of my ports are trunking between VLANs - they only have one in
>> untagged mode - and there's only 2 VLANs here, one per-port.
>>
>> Thanks again!
>> cecjr
>>
>>
>>
>> On Mon, Aug 19, 2019 at 10:36 PM Tony Pearce  wrote:
>>
>>> A couple of links I found helpful, thought I'd send them over
>>> http://therandomsecurityguy.com/openvswitch-cheat-sheet/
>>>
>>> https://ovirt.org/develop/release-management/features/network/openvswitch/native-openvswitch.html
>>>
>>> With STP off, if the network is detecting a loop then it will have to
>>> block a link. With STP on I guess it's allowing the network to remain
>>> forwarding and the blocking to occur elsewhere. 👍
>>>
>>>
>>> Tony Pearce
>>>
>>> On Tue, 20 Aug 2019 at 10:12, Curtis E. Combs Jr. 
>>> wrote:
>>> >
>>> > Cool, I can capture some packets tomorrow when I'm in the office and
>>> > see how that compares...
>>> >
>>> > But, yea, it's a hassle to get them to respond IF they do, so the only
>>> > real options I'm going to have are what I can do with my servers from
>>> the OS. No
>>> > physical access. No nice DC guy to help me out.
>>> >
>>> >
>>> > On Mon, Aug 19, 2019 at 10:06 PM Tony Pearce 
>>> wrote:
>>> > >
>>> > > :) They might be using Cisco's per-vlan spanning tree on the network
>>> > > side. It is possible to capture the packets coming in from the
>>> network
>>> > > and confirm that.
>>> > >
>>> > > Attached screenshot of wireshark for you for reference.
>>> > >
>>> > > Glad you're all working :)
>>> > >
>>> > > Regards
>>> > >
>>> > > Tony Pearce
>>> > >
>>> > >
>>> > >
>>> > > On Tue, 20 Aug 2019 at 09:52, Curtis E. Combs Jr. <
>>> ej.alb...@gmail.com> wrote:
>>> > > >
>>> > > > Hey Tony!
>>> > > >
>>> > > > I only know the basics of Spanning Tree. At the current moment the
>>> > > > only way to get migrations to work at all without breaking the
>>> whole
>>> > > > oVirt cluster is to have it on. After changing it according to
>>> Paul's
>>> > > > instruction, it works like it has never worked before. Every
>>> migration
>>> > > > event was successful. Whereas before and even at times with the
>>> > > > cronjob (when vdsm set STP to off between cron runs) the link would
>>> > > > drop out and oVirt would say that the host was "unresponsive".
>>> > > >
>>> > > > It would be too - it wouldn't respond to SSH, ping, arp
>>> > > > requests...nothing. I never got a good idea of how long this would
>>> be
>>> > > > for, but it would, eventually go away and the link would come back
>>> > > > online.
>>> > > >
>>> > > > I have no access to the hardware. From using tcpdump to get some
>>> CDP
>>> > > > packets, I do know that it's Cisco switches but the IT team here is
>>> > > > completely unresponsive (they literally ignore our tickets) and the
>>> > > > co-lo where our servers are hosted won't even pick up the phone for
>>> > > > anyone but them
>>> > > >
>>> > > > Unfortunately, this is what I'm going to have to do. The cluster is
>>> > > > very functional, though. I created around 15 VMs today and
>>> > > > migrated them from host to host without any problem.
>>> > > >
>>> > > > Anything else you'd like me to try? This is currently dev, so I can
>>> > > > really do anything I want and I can just IPMI reboot the nodes if
>>> it
>>> > > > causes issues...
>>> > > >
>>> > > > Thanks!
>>> > > > cecjr
>>> > > >
>>> > > >
>>> > > > On Mon, Aug 19, 2019 at 9:37 PM Tony Pearce 
>>> wrote:
>>> > > > >
>>> > > > > e.albany,
>>> > > > >
>>> > > > > STP is meant to block loops in layer 2. In basic operation, a
>>> root
>>> > > > > bridge is elected which is the root of the tree. This bridge
>>> sends,
>>> > > > > essentially 'hello' messages as multicast packets. The switches
>>> then
>>> > > > > detect the loop in the network and block one of the links to
>>> prevent
>>> > > > > such things as a broadcast storm.
>>> > > > >
>>> > > >

[ovirt-users] Re: Need to enable STP on ovirt bridges

[Tony Pearce]

No - no recommendations from me to use either. I took it that you were
using ovs bridge as I was not aware of another bridge. The only other
option I was aware of if what I am using, vlan interfaces and kernel vlan
tags. If you could share a link to what you're using, I would be keen to
read up on it to know more.

*Tony Pearce*


On Tue, 20 Aug 2019 at 16:27, Curtis E. Combs Jr. 
wrote:

> Tony,
>
> Well, thank you for that, but I'm not using openvswitchs, I'm just using
> regular bridges. Are you suggesting that I do?
>
> From what I can see in the interface they have "(experimental)" marked on
> them and we'd like to see production with this at some point.
>
> None of my ports are trunking between VLANs - they only have one in
> untagged mode - and there's only 2 VLANs here, one per-port.
>
> Thanks again!
> cecjr
>
>
>
> On Mon, Aug 19, 2019 at 10:36 PM Tony Pearce  wrote:
>
>> A couple of links I found helpful, thought I'd send them over
>> http://therandomsecurityguy.com/openvswitch-cheat-sheet/
>>
>> https://ovirt.org/develop/release-management/features/network/openvswitch/native-openvswitch.html
>>
>> With STP off, if the network is detecting a loop then it will have to
>> block a link. With STP on I guess it's allowing the network to remain
>> forwarding and the blocking to occur elsewhere. 👍
>>
>>
>> Tony Pearce
>>
>> On Tue, 20 Aug 2019 at 10:12, Curtis E. Combs Jr. 
>> wrote:
>> >
>> > Cool, I can capture some packets tomorrow when I'm in the office and
>> > see how that compares...
>> >
>> > But, yea, it's a hassle to get them to respond IF they do, so the only
>> > real options I'm going to have are what I can do with my servers from
>> the OS. No
>> > physical access. No nice DC guy to help me out.
>> >
>> >
>> > On Mon, Aug 19, 2019 at 10:06 PM Tony Pearce  wrote:
>> > >
>> > > :) They might be using Cisco's per-vlan spanning tree on the network
>> > > side. It is possible to capture the packets coming in from the network
>> > > and confirm that.
>> > >
>> > > Attached screenshot of wireshark for you for reference.
>> > >
>> > > Glad you're all working :)
>> > >
>> > > Regards
>> > >
>> > > Tony Pearce
>> > >
>> > >
>> > >
>> > > On Tue, 20 Aug 2019 at 09:52, Curtis E. Combs Jr. <
>> ej.alb...@gmail.com> wrote:
>> > > >
>> > > > Hey Tony!
>> > > >
>> > > > I only know the basics of Spanning Tree. At the current moment the
>> > > > only way to get migrations to work at all without breaking the whole
>> > > > oVirt cluster is to have it on. After changing it according to
>> Paul's
>> > > > instruction, it works like it has never worked before. Every
>> migration
>> > > > event was successful. Whereas before and even at times with the
>> > > > cronjob (when vdsm set STP to off between cron runs) the link would
>> > > > drop out and oVirt would say that the host was "unresponsive".
>> > > >
>> > > > It would be too - it wouldn't respond to SSH, ping, arp
>> > > > requests...nothing. I never got a good idea of how long this would
>> be
>> > > > for, but it would, eventually go away and the link would come back
>> > > > online.
>> > > >
>> > > > I have no access to the hardware. From using tcpdump to get some CDP
>> > > > packets, I do know that it's Cisco switches but the IT team here is
>> > > > completely unresponsive (they literally ignore our tickets) and the
>> > > > co-lo where our servers are hosted won't even pick up the phone for
>> > > > anyone but them
>> > > >
>> > > > Unfortunately, this is what I'm going to have to do. The cluster is
>> > > > very functional, though. I created around 15 VMs today and
>> > > > migrated them from host to host without any problem.
>> > > >
>> > > > Anything else you'd like me to try? This is currently dev, so I can
>> > > > really do anything I want and I can just IPMI reboot the nodes if it
>> > > > causes issues...
>> > > >
>> > > > Thanks!
>> > > > cecjr
>> > > >
>> > > >
>> > > > On Mon, Aug 19, 2019 at 9:37 PM Tony Pearce 
>> wrote:
>> > > > >
>> > > > > e.albany,
>> > > > >
>> > > > > STP is meant to block loops in layer 2. In basic operation, a root
>> > > > > bridge is elected which is the root of the tree. This bridge
>> sends,
>> > > > > essentially 'hello' messages as multicast packets. The switches
>> then
>> > > > > detect the loop in the network and block one of the links to
>> prevent
>> > > > > such things as a broadcast storm.
>> > > > >
>> > > > > There are different flavours of STP but "STP" usually means the
>> hellos
>> > > > > are sent over VLAN 1 (or no vlan). Therefore if you have multiple
>> > > > > VLANs on links, the hellos are still only sent over VLAN 1 and all
>> > > > > VLANs are dealt with that way. Meaning if a link is blocked then
>> all
>> > > > > VLANs are blocked on that link,
>> > > > >
>> > > > > Then came the different flavours, one of which is per-vlan STP.
>> This
>> > > > > allows individual VLANs to be blocked and gives more flexibility.
>> > > > >
>> > > > > After STP has dealt with the blocking, this l

[ovirt-users] Re: Need to enable STP on ovirt bridges

[Curtis E. Combs Jr.]

Tony,

Well, thank you for that, but I'm not using openvswitchs, I'm just using
regular bridges. Are you suggesting that I do?

>From what I can see in the interface they have "(experimental)" marked on
them and we'd like to see production with this at some point.

None of my ports are trunking between VLANs - they only have one in
untagged mode - and there's only 2 VLANs here, one per-port.

Thanks again!
cecjr



On Mon, Aug 19, 2019 at 10:36 PM Tony Pearce  wrote:

> A couple of links I found helpful, thought I'd send them over
> http://therandomsecurityguy.com/openvswitch-cheat-sheet/
>
> https://ovirt.org/develop/release-management/features/network/openvswitch/native-openvswitch.html
>
> With STP off, if the network is detecting a loop then it will have to
> block a link. With STP on I guess it's allowing the network to remain
> forwarding and the blocking to occur elsewhere. 👍
>
>
> Tony Pearce
>
> On Tue, 20 Aug 2019 at 10:12, Curtis E. Combs Jr. 
> wrote:
> >
> > Cool, I can capture some packets tomorrow when I'm in the office and
> > see how that compares...
> >
> > But, yea, it's a hassle to get them to respond IF they do, so the only
> > real options I'm going to have are what I can do with my servers from
> the OS. No
> > physical access. No nice DC guy to help me out.
> >
> >
> > On Mon, Aug 19, 2019 at 10:06 PM Tony Pearce  wrote:
> > >
> > > :) They might be using Cisco's per-vlan spanning tree on the network
> > > side. It is possible to capture the packets coming in from the network
> > > and confirm that.
> > >
> > > Attached screenshot of wireshark for you for reference.
> > >
> > > Glad you're all working :)
> > >
> > > Regards
> > >
> > > Tony Pearce
> > >
> > >
> > >
> > > On Tue, 20 Aug 2019 at 09:52, Curtis E. Combs Jr. 
> wrote:
> > > >
> > > > Hey Tony!
> > > >
> > > > I only know the basics of Spanning Tree. At the current moment the
> > > > only way to get migrations to work at all without breaking the whole
> > > > oVirt cluster is to have it on. After changing it according to Paul's
> > > > instruction, it works like it has never worked before. Every
> migration
> > > > event was successful. Whereas before and even at times with the
> > > > cronjob (when vdsm set STP to off between cron runs) the link would
> > > > drop out and oVirt would say that the host was "unresponsive".
> > > >
> > > > It would be too - it wouldn't respond to SSH, ping, arp
> > > > requests...nothing. I never got a good idea of how long this would be
> > > > for, but it would, eventually go away and the link would come back
> > > > online.
> > > >
> > > > I have no access to the hardware. From using tcpdump to get some CDP
> > > > packets, I do know that it's Cisco switches but the IT team here is
> > > > completely unresponsive (they literally ignore our tickets) and the
> > > > co-lo where our servers are hosted won't even pick up the phone for
> > > > anyone but them
> > > >
> > > > Unfortunately, this is what I'm going to have to do. The cluster is
> > > > very functional, though. I created around 15 VMs today and
> > > > migrated them from host to host without any problem.
> > > >
> > > > Anything else you'd like me to try? This is currently dev, so I can
> > > > really do anything I want and I can just IPMI reboot the nodes if it
> > > > causes issues...
> > > >
> > > > Thanks!
> > > > cecjr
> > > >
> > > >
> > > > On Mon, Aug 19, 2019 at 9:37 PM Tony Pearce 
> wrote:
> > > > >
> > > > > e.albany,
> > > > >
> > > > > STP is meant to block loops in layer 2. In basic operation, a root
> > > > > bridge is elected which is the root of the tree. This bridge sends,
> > > > > essentially 'hello' messages as multicast packets. The switches
> then
> > > > > detect the loop in the network and block one of the links to
> prevent
> > > > > such things as a broadcast storm.
> > > > >
> > > > > There are different flavours of STP but "STP" usually means the
> hellos
> > > > > are sent over VLAN 1 (or no vlan). Therefore if you have multiple
> > > > > VLANs on links, the hellos are still only sent over VLAN 1 and all
> > > > > VLANs are dealt with that way. Meaning if a link is blocked then
> all
> > > > > VLANs are blocked on that link,
> > > > >
> > > > > Then came the different flavours, one of which is per-vlan STP.
> This
> > > > > allows individual VLANs to be blocked and gives more flexibility.
> > > > >
> > > > > After STP has dealt with the blocking, this link blocking will
> > > > > continue until a change in the network is detected. This is
> detected
> > > > > by the absence of the STP packets or the presence of new STP
> packets
> > > > > where there shouldnt be. When this happens, STP packets are flooded
> > > > > everywhere to discover the new network topology. Ultimately, the
> loop
> > > > > will be blocked again.
> > > > >
> > > > > I think that you have two STP versions running in your network and
> > > > > it's causing the issue. An easy test would be to remove the loop
> > > > > manually

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

[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 
> [org.ovirt.engine.core.util