- Users - oVirt List Archives

vdsm 4.50.3.4 and qemu-kvm update problem
by Kapetanakis Giannis 16 Nov '22

16 Nov '22

It seems that vdsm 4.50.3.4-1.el8 has been pushed to centos-ovirt45 which according to https://github.com/oVirt/vdsm/blob/master/vdsm.spec.in # Zero-copy migrations, https://bugzilla.redhat.com/2089434 Requires: qemu-kvm >= 15:6.2.0-11.module+el8.6.0+16360+9e5d914e.4 This is not available in Rocky 8.6, probably not backported from Redhat 8.7? # dnf update Last metadata expiration check: 0:02:15 ago on Tue 08 Nov 2022 13:24:14 EET. Error: Problem 1: cannot install the best update candidate for package vdsm-4.50.2.2-1.el8.x86_64 - nothing provides qemu-kvm >= 15:6.2.0-11.module+el8.6.0+16360+9e5d914e.4 needed by vdsm-4.50.3.4-1.el8.x86_64 G

3 6

Best performance for vcpu pinning
by martin.decker＠ora-solutions.net 16 Nov '22

16 Nov '22

Hello List, how can I achieve the best performance with vcpu pinning in KVM? Is it better to have 1:1 mapping between virtual and physical thread like this: <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='5'/> <vcpupin vcpu='6' cpuset='6'/> <vcpupin vcpu='7' cpuset='7'/> Or is it better to allow each vCPU to run on any of the limited number of physical threads? e.g. <vcpupin vcpu='0' cpuset='0,1,2,3,4,5,6,7'/> <vcpupin vcpu='1' cpuset='0,1,2,3,4,5,6,7'/> <vcpupin vcpu='2' cpuset='0,1,2,3,4,5,6,7'/> <vcpupin vcpu='3' cpuset='0,1,2,3,4,5,6,7'/> <vcpupin vcpu='4' cpuset='0,1,2,3,4,5,6,7'/> <vcpupin vcpu='5' cpuset='0,1,2,3,4,5,6,7'/> <vcpupin vcpu='6' cpuset='0,1,2,3,4,5,6,7'/> <vcpupin vcpu='7' cpuset='0,1,2,3,4,5,6,7'/> The hypervisor host has 2 CPUs. Each CPU has 8 cores and each core 2 Threads. In total this are 32 threads. lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 32 On-line CPU(s) list: 0-31 Thread(s) per core: 2 Core(s) per socket: 8 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel CPU family: 6 Model: 85 Model name: Intel(R) Xeon(R) Gold 6244 CPU @ 3.60GHz Stepping: 7 CPU MHz: 4213.731 CPU max MHz: 4400.0000 CPU min MHz: 1200.0000 BogoMIPS: 7200.00 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 1024K L3 cache: 25344K NUMA node0 CPU(s): 0-7,16-23 NUMA node1 CPU(s): 8-15,24-31 I need to run 2 VMs on this host. One is for production and should have 24 vCPUs and the other one is for test and should have 8 vCPUs. Test VM workload should not impact Prod VM performance. Current configuration is: TEST: <vcpu placement='static' current='8'>128</vcpu> <iothreads>1</iothreads> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='5'/> <vcpupin vcpu='6' cpuset='6'/> <vcpupin vcpu='7' cpuset='7'/> </cputune> <cpu mode='host-passthrough' check='none'> <topology sockets='16' cores='4' threads='2'/> <numa> <cell id='0' cpus='0-7' memory='134217728' unit='KiB'/> </numa> </cpu> PROD: <vcpu placement='static' current='24'>192</vcpu> <iothreads>1</iothreads> <cputune> <vcpupin vcpu='0' cpuset='8'/> <vcpupin vcpu='1' cpuset='9'/> <vcpupin vcpu='2' cpuset='10'/> <vcpupin vcpu='3' cpuset='11'/> <vcpupin vcpu='4' cpuset='12'/> <vcpupin vcpu='5' cpuset='13'/> <vcpupin vcpu='6' cpuset='14'/> <vcpupin vcpu='7' cpuset='15'/> <vcpupin vcpu='8' cpuset='16'/> <vcpupin vcpu='9' cpuset='17'/> <vcpupin vcpu='10' cpuset='18'/> <vcpupin vcpu='11' cpuset='19'/> <vcpupin vcpu='12' cpuset='20'/> <vcpupin vcpu='13' cpuset='21'/> <vcpupin vcpu='14' cpuset='22'/> <vcpupin vcpu='15' cpuset='23'/> <vcpupin vcpu='16' cpuset='24'/> <vcpupin vcpu='17' cpuset='25'/> <vcpupin vcpu='18' cpuset='26'/> <vcpupin vcpu='19' cpuset='27'/> <vcpupin vcpu='20' cpuset='28'/> <vcpupin vcpu='21' cpuset='29'/> <vcpupin vcpu='22' cpuset='30'/> <vcpupin vcpu='23' cpuset='31'/> </cputune> <cpu mode='host-passthrough' check='none'> <topology sockets='16' cores='6' threads='2'/> <numa> <cell id='0' cpus='0-23' memory='889192448' unit='KiB'/> </numa> </cpu> Versions are: ovirt-host-4.3.5 libvirt-5.7.0-28.el7.x86_64 Thanks in advance, Martin

4 4

VDSM <host> command DestroyVDS failed: General Exception: ("Found not_in_hw, expected ('???',)",)
by nicolas＠devels.es 16 Nov '22

16 Nov '22

Hi, We're running oVirt version 4.4.8, vdsm version 4.40.100.2 and from a couple days ago some of our hosts are reporting the following error: VDSM <host> command DestroyVDS failed: General Exception: ("Found not_in_hw, expected ('???',)",) Seems that nothing has stopped working, but this is an error that shows up in the event list each minute (x each host) and is annoying. Not all hosts report this error, just a couple of them. As a fact, we had to downgrade the libvirt version on our hosts to version 7.6.0-6 because we found a bug that wouldn't start web VNC consoles with versions > 8.x.x. Not sure if this has something to do with it. Could someone shed some light on what's happening and how to solve it? Logs can be downloaded from: https://drive.google.com/file/d/1ltP-kqNu08TvOgthU9_XSZiVDa0nTGxO/view?usp=… Thanks. Nicolas

1 0

ovirt 4.5.3.2 - remove snapshot and powerdown VM take the VM disk to unconsistent state
by Diego Ercolani 16 Nov '22

16 Nov '22

I think I encountered another bug in the engine: I needed to remove a snapshot, and while I was removing the snapshot guest went down. What happened is that the snapshot remove failed and left "inconsistent". I think there is some issue to address. Here are the relevant log (the engine.log (see 22/11/14 13:17:59)) and the log of node4 that was used by the engine. https://cloud.ssis.sm/index.php/s/CiEqMwwK5mGxBgg

2 2

Is iSCSI supposed to be this slow?
by fs3000＠pm.me 15 Nov '22

15 Nov '22

Hello all. I just installed ovirt node and the hosted engine on a single host. As the setup did not offer a option for local filesystems, I used a iscsi LUN on the same host. So the engine got installed there. That LUN is a on a nvme disk, the kind that reads higher than 3GB/s. Yet, on a vm, i cannot get more than 280MB/s. That's using virtio-scsi or virtio as the interface. Using SATA gives around 350MB/s. I tested with dd, like: Bechmarking writes: dd if=/dev/zero of=/root/test bs=1M count=7000 status=progress Bechmarking reads: dd if=/root/test of=/dev/null bs=1M status=progress Also with hdparm -t /dev/sda Is ISCSI supposed to be this slow? Again, this is on the same machine.

1 0

what happens to vms when a host shutdowns?
by Nathanaël Blanchet 15 Nov '22

15 Nov '22

Hi, We are installing UPS powerchute client on hypervisors. What is the default vms behaviour of running vms when an hypervisor is ordered to shutdown: do the vms live migrate or do they shutdown properly (even the restart on an other host because of HA) ? -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

7 11

Remote logging for httpd
by eshwayri＠gmail.com 14 Nov '22

14 Nov '22

My relatively small lab system was generating ~10GB of httpd logging on a daily basis. Even with logrotate and compression, the activity level was just ludicrous. I don't remember this from earlier versions. I don't see any obvious errors in the log that explain this over-zealous behavior. I didn't want to suppress the logs completely, and the LogLevel is already on warn. I decided in the end to remote log to my central syslog server which stores the logs on an NFS mount from a FreeNAS (ZFS with compression) NAS. The compression will keep the actual disk space down, and since I am not all that worried about losing some logs, I went with sync=off and udp on the transit. Here are the changes I made to /etc/httpd/conf.d/ssl.conf in case someone else finds them useful. 48,49c48,51 < ErrorLog logs/ssl_error_log < TransferLog logs/ssl_access_log --- > #ErrorLog logs/ssl_error_log > ErrorLog "|/usr/bin/logger -t ssl-error -p local1.warn" > #TransferLog logs/ssl_access_log > TransferLog "|/usr/bin/logger -t ssl-access -p local1.warn" 203,206c205,212 < CustomLog logs/ssl_request_log \ < "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" < < CustomLog logs/ovirt-requests-log "%t %h \"Correlation-Id: %{Correlation-Id}o\" \"Duration: %Dus\" \"%r\" %b" "expr=%{QUERY_STRING} !~ /username.*password|password.*username/" --- > #CustomLog logs/ssl_request_log \ > # "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" > LogFormat "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" ssl-request-format > CustomLog "|/usr/bin/logger -t ssl-requests -p local1.warn" ssl-request-format > > LogFormat "%t %h \"Correlation-Id: %{Correlation-Id}o\" \"Duration: %Dus\" \"%r\" %b" ovirt-requests-format > CustomLog "|/usr/bin/logger -t ovirt-requests -p local1.warn" ovirt-requests-format "expr=%{QUERY_STRING} !~ /username.*password|password.*username/" > #CustomLog logs/ovirt-requests-log "%t %h \"Correlation-Id: %{Correlation-Id}o\" \"Duration: %Dus\" \"%r\" %b" "expr=%{QUERY_STRING} !~ /username.*password|password.*username/" then blocked local logging to messages with local1.none in rsyslog.conf.

1 0

[USB PROBLEM] - Unable to active USB
by cedric＠mrtn.ovh 14 Nov '22

14 Nov '22

Hello, I try to mount an usb key on one virtual machine (running linux) by adding it to hosted devices. But I can't active USB in "Console" menu, the field Enable USB is greyed. How can I enable it ? Best regards.

1 0

deployment engine.ear fail on bll.jar
by Sergey Yudin 14 Nov '22

14 Nov '22

We have oVirt 4.1. hosted-engine failed to start on deploying engine.ear/bll.jar stage with null pointer exception. Is it possible to understand why bll.jar failes ? Server.log is: 2022-11-13 23:17:46,914+03 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) stopped in 46ms 2022-11-13 23:36:14,083+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) WFLYCLINF0001: Activating Infinispan subsystem. 2022-11-13 23:36:14,098+03 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 28) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors 2022-11-13 23:36:14,108+03 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 33) WFLYNAM0001: Activating Naming Subsystem 2022-11-13 23:36:14,114+03 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 37) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. 2022-11-13 23:36:14,146+03 INFO [org.jboss.as.connector] (MSC service thread 1-6) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final) 2022-11-13 23:36:14,161+03 INFO [org.jboss.as.security] (ServerService Thread Pool -- 36) WFLYSEC0002: Activating Security Subsystem 2022-11-13 23:36:14,181+03 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 24) WFLYJCA0005: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.2) 2022-11-13 23:36:14,191+03 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = postgresql 2022-11-13 23:36:14,197+03 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.6.Final 2022-11-13 23:36:14,208+03 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service 2022-11-13 23:36:14,386+03 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.4.0.Final starting 2022-11-13 23:36:14,641+03 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: Started server default-server. 2022-11-13 23:36:14,652+03 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting 2022-11-13 23:36:14,663+03 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing. 2022-11-13 23:36:14,664+03 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host. 2022-11-13 23:36:14,686+03 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow AJP listener ajp listening on 127.0.0.1:8702 2022-11-13 23:36:14,721+03 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0098: Bound non-transactional data source: java:/ENGINEDataSourceNoJTA 2022-11-13 23:36:14,838+03 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:/DWHDataSource] 2022-11-13 23:36:14,859+03 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:/ENGINEDataSource] 2022-11-13 23:36:15,196+03 INFO [org.jboss.as.remoting] (MSC service thread 1-7) WFLYRMT0001: Listening on 127.0.0.1:8707 2022-11-13 23:36:15,245+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "ovirt-web-ui.war" (runtime-name: "ovirt-web-ui.war") 2022-11-13 23:36:15,247+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "restapi.war" (runtime-name: "restapi.war") 2022-11-13 23:36:15,248+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "engine.ear" (runtime-name: "engine.ear") 2022-11-13 23:36:15,255+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "apidoc.war" (runtime-name: "apidoc.war") 2022-11-13 23:36:15,266+03 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) WFLYDS0013: Started FileSystemDeploymentService for directory /var/lib/ovirt-engine/jboss_runtime/d eployments 2022-11-13 23:36:15,426+03 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final 2022-11-13 23:36:15,520+03 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 41) ISPN000152: Passivation configured without an eviction policy bei ng selected. Only manually evicted entities will be passivated. 2022-11-13 23:36:15,521+03 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 41) ISPN000152: Passivation configured without an eviction policy bei ng selected. Only manually evicted entities will be passivated. 2022-11-13 23:36:15,522+03 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 44) ISPN000152: Passivation configured without an eviction policy bei ng selected. Only manually evicted entities will be passivated. 2022-11-13 23:36:15,523+03 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 44) ISPN000152: Passivation configured without an eviction policy bei ng selected. Only manually evicted entities will be passivated. 2022-11-13 23:36:16,481+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "services.war") 2022-11-13 23:36:16,481+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "webadmin.war") 2022-11-13 23:36:16,482+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "enginesso.war") 2022-11-13 23:36:16,482+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "root.war") 2022-11-13 23:36:16,482+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "docs.war") 2022-11-13 23:36:16,482+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "welcome.war") 2022-11-13 23:36:16,483+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "bll.jar") 2022-11-13 23:36:16,483+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "userportal.war") 2022-11-13 23:36:17,081+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 44) WFLYUT0021: Registered web context: /ovirt-engine/web-ui 2022-11-13 23:36:17,080+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 46) WFLYUT0021: Registered web context: /ovirt-engine/apidoc 2022-11-13 23:36:18,785+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment engine.ear 2022-11-13 23:36:19,033+03 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 5.2.4.Final 2022-11-13 23:36:19,109+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment root.war 2022-11-13 23:36:19,144+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment services.war 2022-11-13 23:36:19,202+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment enginesso.war 2022-11-13 23:36:19,207+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment docs.war 2022-11-13 23:36:19,216+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment welcome.war 2022-11-13 23:36:19,256+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment userportal.war 2022-11-13 23:36:19,281+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment webadmin.war 2022-11-13 23:36:19,286+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment bll.jar 2022-11-13 23:36:19,294+03 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'LockManager' in deployment unit 'subdeployment "bll.jar" o f deployment "engine.ear"' are as follows: java:global/engine/bll/LockManager!org.ovirt.engine.core.utils.lock.LockManager java:app/bll/LockManager!org.ovirt.engine.core.utils.lock.LockManager java:module/LockManager!org.ovirt.engine.core.utils.lock.LockManager java:global/engine/bll/LockManager java:app/bll/LockManager java:module/LockManager 2022-11-13 23:36:19,294+03 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'Backend' in deployment unit 'subdeployment "bll.jar" of de ployment "engine.ear"' are as follows: java:global/engine/bll/Backend!org.ovirt.engine.core.common.interfaces.BackendLocal java:app/bll/Backend!org.ovirt.engine.core.common.interfaces.BackendLocal java:module/Backend!org.ovirt.engine.core.common.interfaces.BackendLocal java:global/engine/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler java:app/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler java:module/Backend!org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler java:global/engine/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendInternal java:app/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendInternal java:module/Backend!org.ovirt.engine.core.bll.interfaces.BackendInternal 2022-11-13 23:36:19,301+03 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'InitBackendServicesOnStartupBean' in deployment unit 'subd eployment "bll.jar" of deployment "engine.ear"' are as follows: java:global/engine/bll/InitBackendServicesOnStartupBean!org.ovirt.engine.core.bll.InitBackendServicesOnStartup java:app/bll/InitBackendServicesOnStartupBean!org.ovirt.engine.core.bll.InitBackendServicesOnStartup java:module/InitBackendServicesOnStartupBean!org.ovirt.engine.core.bll.InitBackendServicesOnStartup java:global/engine/bll/InitBackendServicesOnStartupBean java:app/bll/InitBackendServicesOnStartupBean java:module/InitBackendServicesOnStartupBean 2022-11-13 23:36:19,301+03 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'MacPoolPerCluster' in deployment unit 'subdeployment "bll. jar" of deployment "engine.ear"' are as follows: java:global/engine/bll/MacPoolPerCluster!org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster java:app/bll/MacPoolPerCluster!org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster java:module/MacPoolPerCluster!org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster java:global/engine/bll/MacPoolPerCluster java:app/bll/MacPoolPerCluster java:module/MacPoolPerCluster 2022-11-13 23:36:19,368+03 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900: 2.3.5 (Final) 2022-11-13 23:36:26,032+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 48) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.ovirt.engine.api.v3.V3Ap plication 2022-11-13 23:36:26,033+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 48) RESTEASY002220: Adding singleton resource org.ovirt.engine.api.v3.servers.V3SystemServer f rom Application class org.ovirt.engine.api.v3.V3Application 2022-11-13 23:36:26,033+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 48) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.v3.V3InvalidValueExceptionM apper from Application class org.ovirt.engine.api.v3.V3Application 2022-11-13 23:36:26,033+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 48) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.v3.V3IOExceptionMapper from Application class org.ovirt.engine.api.v3.V3Application 2022-11-13 23:36:26,274+03 WARN [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000167: Class org.ovirt.engine.core.dao.EngineSessionDaoImpl$EngineSessionParameterSource is annotated with @ Dependent but it does not declare an appropriate constructor therefore is not registered as a bean! 2022-11-13 23:36:26,274+03 WARN [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 3) WELD-000167: Class org.ovirt.engine.core.dao.AsyncTaskDaoImpl$AsyncTaskParameterSource is annotated with @Dependen t but it does not declare an appropriate constructor therefore is not registered as a bean! 2022-11-13 23:36:26,281+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 5) WELD-001125: Illegal bean type org.ovirt.engine.core.dao.GenericDao<org.ovirt.engine.core.common.businessentities. Provider<?>, org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Singleton @Named class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-11-13 23:36:26,282+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 5) WELD-001125: Illegal bean type org.ovirt.engine.core.dao.DefaultGenericDao<org.ovirt.engine.core.common.businessen tities.Provider<?>, org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Singleton @Named class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-11-13 23:36:26,282+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 5) WELD-001125: Illegal bean type interface org.ovirt.engine.core.dao.ReadDao<org.ovirt.engine.core.common.businessen tities.Provider<?>,class org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Singleton @Named class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-11-13 23:36:26,282+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 5) WELD-001125: Illegal bean type org.ovirt.engine.core.dao.SearchDao<org.ovirt.engine.core.common.businessentities.P rovider<?>> ignored on [EnhancedAnnotatedTypeImpl] public @Singleton @Named class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-11-13 23:36:26,283+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 5) WELD-001125: Illegal bean type interface org.ovirt.engine.core.dao.ModificationDao<org.ovirt.engine.core.common.bu sinessentities.Provider<?>,class org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Singleton @Named class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-11-13 23:36:26,283+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 5) WELD-001125: Illegal bean type class org.ovirt.engine.core.dao.DefaultReadDao<org.ovirt.engine.core.common.busines sentities.Provider<?>,class org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Singleton @Named class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-11-13 23:36:26,321+03 WARN [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000167: Class org.ovirt.engine.core.dao.DbUserDaoImpl$DbUserMapSqlParameterSource is annotated with @Dependen t but it does not declare an appropriate constructor therefore is not registered as a bean! 2022-11-13 23:36:26,331+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-001125: Illegal bean type org.springframework.jdbc.core.RowMapper<org.ovirt.engine.core.common.businessentiti es.Provider<?>> ignored on [EnhancedAnnotatedTypeImpl] private static class org.ovirt.engine.core.dao.provider.ProviderDaoImpl$ProviderRowMapper 2022-11-13 23:36:26,333+03 WARN [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-000167: Class org.ovirt.engine.core.dao.BookmarkDaoImpl$BookmarkSqlParameterSource is annotated with @Depende nt but it does not declare an appropriate constructor therefore is not registered as a bean! 2022-11-13 23:36:26,446+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 4) WELD-001125: Illegal bean type java.util.Comparator<org.ovirt.engine.core.common.businessentities.network.NetworkI nterface<?>> ignored on [EnhancedAnnotatedTypeImpl] public class org.ovirt.engine.core.common.businessentities.comparators.InterfaceComparerByMAC 2022-11-13 23:36:26,672+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 3) WELD-001125: Illegal bean type class org.codehaus.jackson.map.deser.std.StdDeserializer<java.lang.Enum<?>> ignored on [EnhancedAnnotatedTypeImpl] public class org.ovirt.engine.core.utils.serialization.json.JsonEnumDeserializer 2022-11-13 23:36:26,673+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 3) WELD-001125: Illegal bean type org.codehaus.jackson.map.deser.std.StdScalarDeserializer<java.lang.Enum<?>> ignored on [EnhancedAnnotatedTypeImpl] public class org.ovirt.engine.core.utils.serialization.json.JsonEnumDeserializer 2022-11-13 23:36:26,673+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 3) WELD-001125: Illegal bean type class org.codehaus.jackson.map.JsonDeserializer<java.lang.Enum<?>> ignored on [Enha ncedAnnotatedTypeImpl] public class org.ovirt.engine.core.utils.serialization.json.JsonEnumDeserializer 2022-11-13 23:36:26,988+03 WARN [org.jboss.as.weld] (Weld Thread Pool -- 1) WFLYWELD0052: Using deployment classloader to load proxy classes for module org.ovirt.engine.core.dal:main. Package-priva te access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi] 2022-11-13 23:36:27,455+03 WARN [org.jboss.as.weld] (MSC service thread 1-1) WFLYWELD0052: Using deployment classloader to load proxy classes for module org.ovirt.engine.core.common:main. Package-p rivate access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi] 2022-11-13 23:36:28,030+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0021: Registered web context: /ovirt-engine/docs 2022-11-13 23:36:28,055+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 40) WFLYUT0021: Registered web context: / 2022-11-13 23:36:28,102+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0021: Registered web context: /ovirt-engine/userportal 2022-11-13 23:36:28,135+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) WFLYUT0021: Registered web context: /ovirt-engine 2022-11-13 23:36:28,142+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 54) WFLYUT0021: Registered web context: /ovirt-engine/services 2022-11-13 23:36:28,370+03 INFO [org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (ServerService Thread Pool -- 49) Loading XML bean definitions from class path resource [org/springfr amework/jdbc/support/sql-error-codes.xml] 2022-11-13 23:36:28,611+03 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 40) IJ000407: No lazy enlistment available for ENGINEDataSource 2022-11-13 23:36:28,675+03 INFO [org.springframework.jdbc.support.SQLErrorCodesFactory] (ServerService Thread Pool -- 49) SQLErrorCodes loaded: [DB2, Derby, H2, HSQL, Informix, MS-SQL, MySQL, Oracl e, PostgreSQL, Sybase, Hana] 2022-11-13 23:36:28,800+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 40) WFLYUT0021: Registered web context: /ovirt-engine/sso 2022-11-13 23:36:28,920+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 46) WFLYCLINF0002: Started dashboard cache from ovirt-engine container 2022-11-13 23:36:28,941+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 46) WFLYCLINF0002: Started inventory cache from ovirt-engine container 2022-11-13 23:36:28,952+03 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 46) IJ000407: No lazy enlistment available for DWHDataSource 2022-11-13 23:36:28,962+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 46) WFLYUT0021: Registered web context: /ovirt-engine/webadmin 2022-11-13 23:36:29,033+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 48) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.ovirt.engine.api.restapi .BackendApplication 2022-11-13 23:36:29,034+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 48) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation .MalformedIdExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-11-13 23:36:29,034+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 48) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation .JsonExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-11-13 23:36:29,034+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 48) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation .IOExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-11-13 23:36:29,034+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 48) RESTEASY002220: Adding singleton resource org.ovirt.engine.api.restapi.resource.BackendApi Resource from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-11-13 23:36:29,034+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 48) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation .MappingExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-11-13 23:36:29,055+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 48) WFLYUT0021: Registered web context: /ovirt-engine/api 2022-11-13 23:36:29,584+03 INFO [org.quartz.impl.StdSchedulerFactory] (ServerService Thread Pool -- 49) Using default implementation for ThreadExecutor 2022-11-13 23:36:29,600+03 INFO [org.quartz.core.QuartzSchedulerThread] (ServerService Thread Pool -- 49) QuartzSchedulerThread Inheriting ContextClassLoader of thread: ServerService Thread Pool -- 49 2022-11-13 23:36:29,602+03 INFO [org.quartz.core.SchedulerSignalerImpl] (ServerService Thread Pool -- 49) Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl 2022-11-13 23:36:29,602+03 INFO [org.quartz.core.QuartzScheduler] (ServerService Thread Pool -- 49) Quartz Scheduler v.2.1.2 created. 2022-11-13 23:36:29,603+03 INFO [org.quartz.impl.jdbcjobstore.JobStoreCMT] (ServerService Thread Pool -- 49) JDBCJobStore threads will inherit ContextClassLoader of thread: ServerService Thread Poo l -- 49 2022-11-13 23:36:29,603+03 INFO [org.quartz.impl.jdbcjobstore.JobStoreCMT] (ServerService Thread Pool -- 49) Using db table-based data access locking (synchronization). 2022-11-13 23:36:29,605+03 INFO [org.quartz.impl.jdbcjobstore.JobStoreCMT] (ServerService Thread Pool -- 49) JobStoreCMT initialized. 2022-11-13 23:36:29,607+03 INFO [org.quartz.core.QuartzScheduler] (ServerService Thread Pool -- 49) Scheduler meta-data: Quartz Scheduler (v2.1.2) 'QuartzOvirtDBScheduler' with instanceId 'NON_CLUS TERED' Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally. NOT STARTED. Currently in standby mode. Number of jobs executed: 0 Using thread pool 'org.ovirt.engine.core.utils.timer.SchedulerThreadPool' - with 50 threads. Using job-store 'org.quartz.impl.jdbcjobstore.JobStoreCMT' - which supports persistence. and is not clustered. 2022-11-13 23:36:29,607+03 INFO [org.quartz.impl.StdSchedulerFactory] (ServerService Thread Pool -- 49) Quartz scheduler 'QuartzOvirtDBScheduler' initialized from an externally provided properties instance. 2022-11-13 23:36:29,607+03 INFO [org.quartz.impl.StdSchedulerFactory] (ServerService Thread Pool -- 49) Quartz scheduler version: 2.1.2 2022-11-13 23:36:29,772+03 INFO [org.quartz.impl.jdbcjobstore.JobStoreCMT] (ServerService Thread Pool -- 49) Freed 0 triggers from 'acquired' / 'blocked' state. 2022-11-13 23:36:29,810+03 INFO [org.quartz.impl.jdbcjobstore.JobStoreCMT] (ServerService Thread Pool -- 49) Recovering 0 jobs that were in-progress at the time of the last shut-down. 2022-11-13 23:36:29,811+03 INFO [org.quartz.impl.jdbcjobstore.JobStoreCMT] (ServerService Thread Pool -- 49) Recovery complete. 2022-11-13 23:36:29,811+03 INFO [org.quartz.impl.jdbcjobstore.JobStoreCMT] (ServerService Thread Pool -- 49) Removed 0 'complete' triggers. 2022-11-13 23:36:29,812+03 INFO [org.quartz.impl.jdbcjobstore.JobStoreCMT] (ServerService Thread Pool -- 49) Removed 0 stale fired job entries. 2022-11-13 23:36:29,816+03 INFO [org.quartz.core.QuartzScheduler] (ServerService Thread Pool -- 49) Scheduler QuartzOvirtDBScheduler_$_NON_CLUSTERED started. 2022-11-13 23:36:29,827+03 INFO [org.quartz.impl.StdSchedulerFactory] (ServerService Thread Pool -- 49) Using default implementation for ThreadExecutor 2022-11-13 23:36:29,828+03 INFO [org.quartz.core.SchedulerSignalerImpl] (ServerService Thread Pool -- 49) Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl 2022-11-13 23:36:29,828+03 INFO [org.quartz.core.QuartzScheduler] (ServerService Thread Pool -- 49) Quartz Scheduler v.2.1.2 created. 2022-11-13 23:36:29,828+03 INFO [org.quartz.simpl.RAMJobStore] (ServerService Thread Pool -- 49) RAMJobStore initialized. 2022-11-13 23:36:29,828+03 INFO [org.quartz.core.QuartzScheduler] (ServerService Thread Pool -- 49) Scheduler meta-data: Quartz Scheduler (v2.1.2) 'DefaultQuartzScheduler' with instanceId 'NON_CLUS TERED' Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally. NOT STARTED. Currently in standby mode. Number of jobs executed: 0 Using thread pool 'org.ovirt.engine.core.utils.timer.SchedulerThreadPool' - with 100 threads. Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered. 2022-11-13 23:36:29,828+03 INFO [org.quartz.impl.StdSchedulerFactory] (ServerService Thread Pool -- 49) Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz pa ckage: 'quartz.properties' 2022-11-13 23:36:29,828+03 INFO [org.quartz.impl.StdSchedulerFactory] (ServerService Thread Pool -- 49) Quartz scheduler version: 2.1.2 2022-11-13 23:36:29,828+03 INFO [org.quartz.core.QuartzScheduler] (ServerService Thread Pool -- 49) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. 2022-11-13 23:36:29,848+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 49) WFLYCLINF0002: Started timeout-base cache from ovirt-engine container 2022-11-13 23:36:33,874+03 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 49) MSC000001: Failed to start service jboss.deployment.subunit."engine.ear"."bll.jar".component.InitBacke ndServicesOnStartupBean.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."engine.ear"."bll.jar".component.InitBackendServicesOnStartupBean.START: java.lang.IllegalStat eException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_161] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_161] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_161] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_161] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_161] at org.jboss.threads.JBossThread.run(JBossThread.java:320) Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:124) at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:138) at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] ... 6 more Caused by: javax.ejb.EJBException: WFLYEJB0442: Unexpected Error at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:184) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:277) at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:349) at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.ejb3.component.singleton.StartupCountDownInterceptor.processInvocation(StartupCountDownInterceptor.java:25) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] ... 11 more Caused by: java.lang.ExceptionInInitializerError at org.ovirt.engine.core.bll.InitBackendServicesOnStartupBean.create(InitBackendServicesOnStartupBean.java:64) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_161] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_161] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_161] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_161] at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doLifecycleInterception(Jsr299BindingsInterceptor.java:114) at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:103) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:53) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [wildfly-ee-10.1.0.Final.jar:10.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) [jboss-invocation-1.4.1.Final.jar:1.4.1.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275) ... 29 more Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke private void org.ovirt.engine.core.bll.tasks.CommandsRepository.handleUnmanagedCommands() on org.ovirt.engine.core.b ll.tasks.CommandsRepository@4837a568 at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:100) at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:81) at org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:126) at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101) at org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:141) at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742) at org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance(InstanceImpl.java:189) at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:100) at org.ovirt.engine.core.di.Injector.get(Injector.java:45) at org.ovirt.engine.core.bll.tasks.CommandCoordinatorImpl.<init>(CommandCoordinatorImpl.java:53) at org.ovirt.engine.core.bll.tasks.CommandCoordinatorUtil.<clinit>(CommandCoordinatorUtil.java:34) ... 54 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_161] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_161] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_161] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_161] at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:98) ... 67 more Caused by: java.lang.NullPointerException at org.ovirt.engine.core.bll.CloneVmCommand.getSharedLocks(CloneVmCommand.java:106) at org.ovirt.engine.core.bll.CommandBase.buildLock(CommandBase.java:1970) at org.ovirt.engine.core.bll.CommandBase.acquireLockInternal(CommandBase.java:1932) at org.ovirt.engine.core.bll.CommandBase.acquireLockAsyncTask(CommandBase.java:1923) at org.ovirt.engine.core.bll.CommandBase.reacquireLocks(CommandBase.java:1911) at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) [rt.jar:1.8.0_161] at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) [rt.jar:1.8.0_161] at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) [rt.jar:1.8.0_161] at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) [rt.jar:1.8.0_161] at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) [rt.jar:1.8.0_161] at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) [rt.jar:1.8.0_161] at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) [rt.jar:1.8.0_161] at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382) [rt.jar:1.8.0_161] at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) [rt.jar:1.8.0_161] at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) [rt.jar:1.8.0_161] at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) [rt.jar:1.8.0_161] at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) [rt.jar:1.8.0_161] at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) [rt.jar:1.8.0_161] at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) [rt.jar:1.8.0_161] at org.ovirt.engine.core.bll.tasks.CommandsRepository.handleUnmanagedCommands(CommandsRepository.java:110) ... 72 more 2022-11-13 23:36:33,891+03 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "engine.ear")]) - fail ure description: { "WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.InitBackendServicesOnStartupBean.START" => "org.jboss.msc.service.StartException in service jbos s.deployment.subunit.\"engine.ear\".\"bll.jar\".component.InitBackendServicesOnStartupBean.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: javax.ejb.EJBException: WFLYEJB0442: Unexpected Error Caused by: java.lang.ExceptionInInitializerError Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke private void org.ovirt.engine.core.bll.tasks.CommandsRepository.handleUnmanagedCommands() on org.ovirt.engine.co re.bll.tasks.CommandsRepository@4837a568 Caused by: java.lang.reflect.InvocationTargetException Caused by: java.lang.NullPointerException"}, "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.InitBackendServicesOnStartupBean.START"], "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined } 2022-11-13 23:36:34,350+03 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : "ovirt-web-ui.war") 2022-11-13 23:36:34,350+03 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war") 2022-11-13 23:36:34,350+03 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war") 2022-11-13 23:36:34,350+03 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear") 2022-11-13 23:36:34,358+03 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."engine.ear"."bll.jar".component.InitBackendServicesOnStartupBean.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."engine.ear"."bll.jar".component.InitBackendServicesOnStartupBean.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance 2022-11-13 23:36:34,704+03 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:8706/management 2022-11-13 23:36:34,704+03 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:8706 2022-11-13 23:36:34,704+03 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started (with errors) in 26057ms - Started 1558 of 1843 ser vices (4 services failed or missing dependencies, 463 services are lazy, passive or on-demand) 2022-11-13 23:36:34,785+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 10) WFLYUT0022: Unregistered web context: /ovirt-engine/sso 2022-11-13 23:36:34,787+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 7) WFLYUT0022: Unregistered web context: /ovirt-engine/api 2022-11-13 23:36:34,788+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 9) WFLYUT0022: Unregistered web context: /ovirt-engine/services 2022-11-13 23:36:34,791+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 12) WFLYUT0022: Unregistered web context: /ovirt-engine/userportal 2022-11-13 23:36:34,794+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 20) WFLYUT0022: Unregistered web context: / 2022-11-13 23:36:34,799+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 16) WFLYUT0022: Unregistered web context: /ovirt-engine 2022-11-13 23:36:34,800+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 15) WFLYUT0022: Unregistered web context: /ovirt-engine/webadmin 2022-11-13 23:36:34,800+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 19) WFLYUT0022: Unregistered web context: /ovirt-engine/docs 2022-11-13 23:36:34,823+03 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-4) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down. 2022-11-13 23:36:34,823+03 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-4) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused. 2022-11-13 23:36:34,823+03 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-4) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete. 2022-11-13 23:36:34,823+03 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-4) Scheduler QuartzOvirtDBScheduler_$_NON_CLUSTERED shutting down. 2022-11-13 23:36:34,824+03 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-4) Scheduler QuartzOvirtDBScheduler_$_NON_CLUSTERED paused. 2022-11-13 23:36:34,824+03 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-4) Scheduler QuartzOvirtDBScheduler_$_NON_CLUSTERED shutdown complete. 2022-11-13 23:36:34,871+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0208: Stopped subdeployment (runtime-name: webadmin.war) in 118ms 2022-11-13 23:36:34,871+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0208: Stopped subdeployment (runtime-name: docs.war) in 118ms 2022-11-13 23:36:34,871+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0208: Stopped subdeployment (runtime-name: root.war) in 118ms 2022-11-13 23:36:34,871+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0208: Stopped subdeployment (runtime-name: bll.jar) in 118ms 2022-11-13 23:36:34,872+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0208: Stopped subdeployment (runtime-name: enginesso.war) in 118ms 2022-11-13 23:36:34,872+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0208: Stopped subdeployment (runtime-name: welcome.war) in 118ms 2022-11-13 23:36:34,872+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0208: Stopped subdeployment (runtime-name: userportal.war) in 119ms 2022-11-13 23:36:34,872+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0208: Stopped subdeployment (runtime-name: services.war) in 119ms 2022-11-13 23:36:34,873+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment engine.ear (runtime-name: engine.ear) in 121ms 2022-11-13 23:36:34,930+03 WARN [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address [] 2022-11-13 23:36:34,931+03 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "engine.ear" (runtime-name: "engine.ear”) 2022-11-13 23:36:34,932+03 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".moduleDeploymentRuntimeInformatio nStart, service jboss.deployment.subunit."engine.ear"."bll.jar".deploymentCompleteService] service jboss.deployment.subunit."engine.ear"."bll.jar".component.InitBackendServicesOnStartupBean.START (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".moduleDe ploymentRuntimeInformationStart, service jboss.deployment.subunit."engine.ear"."bll.jar".deploymentCompleteService] service jboss.deployment.subunit."engine.ear"."bll.jar".component.LockManager.START (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".moduleDeploymentRuntimeInform ationStart, service jboss.deployment.subunit."engine.ear"."bll.jar".deploymentCompleteService] service jboss.deployment.subunit."engine.ear"."bll.jar".component.MacPoolPerCluster.START (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".moduleDeploymentRuntime InformationStart, service jboss.deployment.subunit."engine.ear"."bll.jar".deploymentCompleteService] service jboss.deployment.subunit."engine.ear"."bll.jar".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."engine.ear".deploymentCompleteService] service jboss.deployment.subunit."engine.ear"."bll.jar".moduleDeploymentRuntimeInformation (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".moduleDeploymentRuntim eInformationStart] service jboss.deployment.subunit."engine.ear"."docs.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."engine.ear".deploymentCompleteService] service jboss.deployment.subunit."engine.ear"."enginesso.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."engine.ear".deploymentCompleteService] service jboss.deployment.subunit."engine.ear"."root.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."engine.ear".deploymentCompleteService] service jboss.deployment.subunit."engine.ear"."services.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."engine.ear".deploymentCompleteService] service jboss.deployment.subunit."engine.ear"."userportal.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."engine.ear".deploymentCompleteService] service jboss.deployment.subunit."engine.ear"."webadmin.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."engine.ear".deploymentCompleteService] service jboss.deployment.subunit."engine.ear"."welcome.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."engine.ear".deploymentCompleteService] service jboss.naming.context.java.global.engine.bll."Backend!org.ovirt.engine.core.common.interfaces.BackendLocal" (missing) dependents: [service jboss.naming.context.java.module.restapi.resta pi.env."org.ovirt.engine.api.restapi.security.CORSSupportFilter".backend, service jboss.naming.context.java.module.restapi.restapi.env."org.ovirt.engine.api.restapi.invocation.CurrentFilter".backend ] WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."engine.ear"."bll.jar".component.InitBackendServicesOnStartupBean.START

1 0

novnc console - promise.js 404 error
by Alexandre Bezroutchko 12 Nov '22

12 Nov '22

Hello, I have deployed oVirt 4.5 on CentOS Stream 8 with self-hosted engine, in IPv6-only mode. I am trying to use noVNC console, from Firefox on MacOS. I have added engine's CA to the list of trusted CAs. I have noticed the webproxy only listens on IPv4 by default, I have tried to add the following configuration file and it made it listed on both IPv4 and IPv6: [root@mng41 ~]# cat /etc/ovirt-engine/ovirt-websocket-proxy.conf.d/20-ipv6.conf SOURCE_IS_IPV6=True Is this correct approach or there is a better way? I guess this should be part of the setup process... Anyway, it does not solve my issue. When I try to use noVNC console, I get the following error in the Firefox javascript console: Loading failed for the <script> with source “ https://mng41.gremwell.com/ovirt-engine/services/files/novnc/vendor/promise… ”. I also get the following message: Firefox can’t establish a connection to the server at wss:// mng41.gremwell.com:6100/ey... I have checked that the port is open and I see some traffic flowing between the browser and that port. In /var/log/ovirt-engine/engine.log I see: 2022-11-11 14:32:57,652+01 INFO [org.ovirt.engine.core.bll.SetVmTicketCommand] (default task-11) [2d6aa0eb] Running command: SetVmTicketCommand internal: false. Entities affected : ID: 7fb95436-da52-421a-a733-503181429929 Type: VMAction group CONNECT_TO_VM with role type USER 2022-11-11 14:32:57,657+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (default task-11) [2d6aa0eb] START, SetVmTicketVDSCommand(HostName = elon41.gremwell.com, SetVmTicketVDSCommandParameters:{hostId='f63b9132-fb54-4c24-b5b3-240c0a1896f9', vmId='7fb95436-da52-421a-a733-503181429929', protocol='VNC', ticket='47kRPdus', validTime='120', userName='admin', userId='af04127c-60d7-11ed-8ad9-00163e63cf1d', disconnectAction='LOCK_SCREEN', consoleDisconnectActionDelay='0'}), log id: 27745778 2022-11-11 14:32:57,688+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (default task-11) [2d6aa0eb] FINISH, SetVmTicketVDSCommand, return: , log id: 27745778 2022-11-11 14:32:57,716+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-11) [2d6aa0eb] EVENT_ID: VM_SET_TICKET(164), User admin@internal-authz initiated console session for VM test 2022-11-11 14:32:57,947+01 INFO [org.ovirt.engine.core.utils.servlet.ServletUtils] (default task-11) [] Can't read file '/usr/share/ovirt-engine/files/novnc/vendor/promise.js' for request '/ovirt-engine/services/files/novnc/vendor/promise.js' -- 404 Any ideas how to have this fixed? Best regards, Alex

1 1

Engine deploy fails - "Wait for the host to be up"
by simon＠justconnect.ie 11 Nov '22

11 Nov '22

I use ansible to build a 3 node HCI environment, or at least I did with 4.4.6. This fails every time with 4.5.2 - what broke? Has anyone any idea what changed and if there's a simple resolution? Kind Regards Simon...

2 3

Adding Foreman as a provider for Ovirt
by eevans＠digitaldatatechs.com 11 Nov '22

11 Nov '22

I am using Ovirt 4.3 on CentOS 7 and ust built a Foreman 3.3 Katello 4.5 vm. I can add ovirt to foreman as a compute resource but Ovirt will not communicate to add foreman as a provider. Engine log states: Adding foreman as Ovirt provider PROVIDER FAILURE and code 5050 I'm not sure why but have searched and cannot find an answer. Any help would be appreciated. Thanks in advance/

2 1

glusterfs Host is not in 'Peer in Cluster' state"
by ziyi Liu 10 Nov '22

10 Nov '22

Version: 4.5.1 Configure the HCI mode on the cockpit web interface, and the message "glusterfs Host is not in 'Peer in Cluster' state" is displayed. node1 gluster peer status normally shows three storage nodes #gluster peer status Number of Peers: 2 Hostname: 10.10.1.6 Uuid: 7973fa76-092e-4102-be43-d69ce2e1202f State: Accepted peer request (Connected) Hostname: 110.10.1.7 Uuid: c65ca1f1-8b0c-4424-80cd-d4606a6bed9e State: Accepted peer request (Connected) node2 # gluster peer status Number of Peers: 1 Hostname: localhost Uuid: 2fd3c233-6457-4d3e-9646-c1d6ed0c27aa State: Accepted peer request (Disconnected) node3 # gluster peer status Number of Peers: 1 Hostname: localhost Uuid: 2fd3c233-6457-4d3e-9646-c1d6ed0c27aa State: Accepted peer request (Disconnected) TASK [gluster.features/roles/gluster_hci : Create the GlusterFS volumes] ******* failed: [10.10.1.5] (item={'volname': 'tj-data1', 'brick': '/gluster_bricks/tj-data1/tj-data1', 'arbiter': 1}) => {"ansible_loop_var ": "item", "changed": true, "cmd": "gluster volume create tj-data1 replica 3 arbiter 1 transport tcp 10.10.1.5:/gluster_bricks/tj-data1/tj-data1 10.10.1.6:/gluster_bricks/ tj-data1/tj-data1 10.10.1.7:/gluster_bricks/tj-data1/tj-data1 force\n", "delta": "0:00:00.091228", "end": "2022-11-08 22: 37:07.609311", "item": {"arbiter": 1, "brick": "/gluster_bricks/tj-data1/tj-data1", "volname": "tj-data1"}, "msg": "non -zero return code", "rc": 1, "start": "2022-11-08 22:37:07.518083", "stderr": "volume create: tj-data1: failed: Host 10.10.1.6 is not in 'Peer in Cluster' state", "stderr_lines": ["volume create: tj-data1: failed: Host 10.10.1.6 is not in 'Peer in Cluster' state"], "stdout": "", "stdout_lines": []} failed: [10.10.1.5] (item={'volname': 'tj-vmstore1', 'brick': '/gluster_bricks/tj-vmstore1/tj-vmstore1', 'arbiter': 1}) => {"ansible_loop_var ": "item", "changed": true, "cmd": "gluster volume create tj-vmstore1 replica 3 arbiter 1 transport tcp 10.10.1.5:/gluster_bricks/tj-vmstore1/tj-vmstore1 10.10.1.6:/gluster_bricks/ tj-vmstore1/tj-vmstore1 10.10.1.7:/gluster_bricks/tj-vmstore1/tj-vmstore1 force\n", "delta": "0:00:00.092017", "end": "2022-11-08 22: 37:08.076088", "item": {"arbiter": 1, "brick": "/gluster_bricks/tj-vmstore1/tj-vmstore1", "volname": "tj-vmstore1"}, "msg": "non -zero return code", "rc": 1, "start": "2022-11-08 22:37:07.984071", "stderr": "volume create: tj-vmstore1: failed: Host 10.10.1.6 is not in 'Peer in Cluster' state", "stderr_lines": ["volume create: tj-vmstore1: failed: Host 10.10.1.6 is not in 'Peer in Cluster' state"], "stdout": "", "stdout_lines": []}

1 1

[FOSDEM][CFP] Virtualization & IaaS Devroom
by Piotr Kliczewski 10 Nov '22

10 Nov '22

We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2023, to be hosted on February 4th 2023. This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, KubeVirt, QEMU, KVM, and Foreman. We would like to invite all those who are involved in these fields to submit your proposals by December 10th, 2022. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors or virtual machine managers such as Xen Project, KVM, bhyve and VirtualBox as well as Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, OpenStack, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 10th December 2022 Acceptance notifications: 15th December 2022 Final schedule announcement: 20th December 2022 Devroom: First half of 4th February 2023 Submit Your Proposal All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) Submission Guidelines Mentored presentations will have 25-minute slots, where 20 minutes will include the presentation and 5 minutes will be reserved for questions. The number of newcomer session slots is limited, so we will probably not be able to accept all applications. You must submit your talk and abstract to apply for the mentoring program, our mentors are volunteering their time and will happily provide feedback but won't write your presentation for you! If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. How to Apply In addition to agreeing to video recording and confirming that you can attend FOSDEM in case your session is accepted, please write "speaker mentoring program application" in the "Submission notes" field, and list any prior speaking experience or other relevant information for your application. Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Call for Volunteers We are also looking for volunteers to help run the devroom. We need assistance watching time for the speakers, and helping with video for the devroom. Please contact devroom mailing list [2] for more information. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] <https://penta.fosdem.org/submission/FOSDEM17> https://penta.fosdem.org/submission/FOSDEM23 [2] iaas-virt-devroom at lists.fosdem.org

1 0

ovirt-node 4.5 and engine 4.4
by Nathanaël Blanchet 10 Nov '22

10 Nov '22

Hello, I'm planning to upgrade ovirt engine to 4.5, but I need now to install additionnal hosts. Is it safe to directly install my new hosts with ovirt-node 4.5 and attach them to 4.4 engine? Thank you -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 1

Blog Post - Using Ceph Only Storage For oVirt Datacenter by Sandro Bonazzola – Wednesday 14 July 2021
by Matthew J Black 10 Nov '22

10 Nov '22

Hi All, In the above mentioned blog post (https://blogs.ovirt.org/2021/07/using-ceph-only-storage-for-ovirt-datacente…) in mentions the line: "Follow oVirt documentation for setting up Cinderlib" with a link to this URL: https://ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_us… This link is broken/obsolete/no longer available, so my question(s) is/are: Where can I obtain this information? Is there a new URL? Are these instructions no-longer required with the new oVirt v4.5.X? Can someone who has these instructions post/email them, please? Thanks in advance Dulux-Oz

6 10

Downloading successful, but checksum doesn't match
by jb 09 Nov '22

09 Nov '22

Hello community, since yesterday I try to update my cluster, but when I was trying it through GUI it never finished and when I try it manually I got: [MIRROR] ovirt-node-ng-image-update-4.5.3.2-1.el8.noarch.rpm: Downloading successful, but checksum doesn't match. Calculated: 365a886b0a2784fa5304d7581970e56a312ab0789c4a97fd329bbd7313da736c(sha256) Expected: 04979b883581b7ccb51ec063329b87a92bc5ea4405a161384cfdea68215e5306(sha256) and it starts again the download process. Before I also run: dnf clean all Can it be, that something with the mirrors are wrong? Best Regard Jonathan

2 2

Hosted engine 4.5.3.2 - still with bug
by vanBulion＠gmail.com 08 Nov '22

08 Nov '22

hi I've try to install new hosted-engine version but deploy process finish with an error after vm start on shared storage (FC disks from SAN storage). [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Check engine VM health] this cuz Jboos web page not working "Service Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later." I open console to VM engine and... disk dm-6 and dm-3 was corrupted - LOL - must fix by xfs_repair. But after restart hosted-engne.service wont start. ● ovirt-engine.service - oVirt Engine Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2022-10-31 15:35:30 CET; 4min 11s ago Process: 1469 ExecStart=/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py --redirect-output --systemd=notify $EXTRA_ARGS start (code=exited, status=1/FAILURE) Main PID: 1469 (code=exited, status=1/FAILURE) Oct 31 15:35:23 ovirt systemd[1]: Starting oVirt Engine... Oct 31 15:35:23 ovirt systemd[1]: Started oVirt Engine. Oct 31 15:35:26 ovirt ovirt-engine.py[1469]: 2022-10-31 15:35:26,606+0100 ovirt-engine: INFO _detectJBossVersion:186 Detecting JBoss version. Running: /usr/lib/jvm/jre-11-openjdk-11.0.> Oct 31 15:35:30 ovirt ovirt-engine.py[1469]: 2022-10-31 15:35:30,369+0100 ovirt-engine: INFO _detectJBossVersion:206 Return code: -6, | stdout: '['#', '# A fatal error has been detect> Oct 31 15:35:30 ovirt ovirt-engine.py[1469]: 2022-10-31 15:35:30,370+0100 ovirt-engine: ERROR run:543 Error: Cannot detect JBoss version Oct 31 15:35:30 ovirt.pogodno systemd[1]: ovirt-engine.service: Main process exited, code=exited, status=1/FAILURE Oct 31 15:35:30 ovirt.pogodno systemd[1]: ovirt-engine.service: Failed with result 'exit-code'. I even try to downgrade postgresql-jdbc to 42.2.3 but no effect. If I stop deploy process when VM start from local storage and I dont continue it - engine VM start with no error but VM start without HA IP configured - not usefully. So I still witing to good working - ovirt-engine-appliance 4.5 ovirt-node-ng-installer-4.5.3.2-2022102813.el8.iso ovirt-engine-appliance-4.5-20221026100732.1.el8.x86_64.rpm Regards Damian

2 3

How to reset admin@ovirt in keycloak
by Sven Jansen 07 Nov '22

07 Nov '22

Hello, after setting up a new oVirt Cluster with buildin keycloak i have issues login in as admin@ovirt, looks like i saved the wrong password in my password manager, now i have issues finding a way to reset the password of this user to do administration in the keycloak admin console, i tried changing the password with: /usr/share/ovirt-engine-keycloak/bin/add-user-keycloak.sh and /usr/share/ovirt-engine-wildfly/bin/add-user-keycloak.sh. Both without success, i found i can create a new "keycloak-add-user.json" with the second command and i can copy it over to the right place where the old file was, after rebooting the hosted engine this has no effect. Is there a known way to reset admin@ovirt with the internal keycloak? i cant find anything in the docs.

1 0

infrastructure boostrap. (i.e engine start / autostart).
by duparchy＠esrf.fr 07 Nov '22

07 Nov '22

Hi, We decided to run the oVirt engine (Oracle flavor) outside the infrastructure. (Medium infrastructure, 10 Hosts, iSCSI storage arrays) We created a second, smaller infrastructure (Single host, local storage) for management (engine) and monitoring (nagios, Dell storage manager etc..) . . This secondary infrastructure's engine runs in the first infrastructure. So, If you picture it, we're facing a "bootstrap" cross-dependency problem where each engine need the other one to start. This is actually a design we had when we were using Xen (Oracle's). Xen provides the "xen create" command to start a VM, even w/o a manager. Bootstrap problem solved. We're moving to oVirt and I understand that oVirt does not support out-of-the-box starting a VM w/o the engine. I've found a workaround that seems to work and would like your advice : - keep a dump of XML of the engine VM # virsh -r dumpxml prodEngine > prodEngine.xml - When necessary use virsh to start the engine # virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf create prodEngine.xml The only visible problem is a warning at the VM that was started manually saying "Newer configuration for next run". A restart clears the warning and there's does not seem to be consequences with the VM that had been started from a dump xml. Note : I understand that there is the "self-hosted" engine architecture that solves that "bootstrap" problem. We're no into that for now. We had bad experience with that design in the past.

3 4

Re: The latest guest agent needs to be installed
by Milan Zamazal 07 Nov '22

07 Nov '22

Christopher Law <chris(a)chrislaw.me> writes: > I've got a couple of VMs giving me this error message, "the latest > guest agent needs to be installed and running". These VMs have the > latest guest agent installed and it is running (virtio-win-1.9.24.iso) You're probably hitting https://bugzilla.redhat.com/2120381. It should get fixed in the next release. Regards, Milan

1 0

Locking down management network
by David White 05 Nov '22

05 Nov '22

I just discovered that my default management network has the "VM Network" checkbox toggled (on the page where you navigate to Network -> Networks and select the management network). There are no virtual machines associated with the management network. Is it safe to simply edit the management network and uncheck the "VM Network" box? Will anything break (even temporarily) if I do this? Sent with Proton Mail secure email.

1 0

Virtual Machine Pools
by Christopher Law 04 Nov '22

04 Nov '22

Hopefully, someone can clarify this a bit for me... From the redhat instructions... "In principle, virtual machines in a pool are started when taken by a user, and shut down when the user is finished. However, virtual machine pools can also contain pre-started virtual machines. Pre-started virtual machines are kept in an up state, and remain idle until they are taken by a user. This allows users to start using such virtual machines immediately, but these virtual machines will consume system resources even while not in use due to being idle." How do users request "take" virtual machines from the pool? For example with a windows machine where we want them to remote desktop into it using RDP? Or does this have to happen through some other portal? Do we have to give users access to the VM Portal? Cheers, Chris.

1 0

The latest guest agent needs to be installed
by Christopher Law 04 Nov '22

04 Nov '22

I've got a couple of VMs giving me this error message, "the latest guest agent needs to be installed and running". These VMs have the latest guest agent installed and it is running (virtio-win-1.9.24.iso) The only change to the environment recently was one host has been upgraded from 4.5.2 to 4.5.3. It seems to be the VMs that had at one point ran on this updated host. However, that host is currently turned off they are running on 4.5.2 hosts and have been rebooted. These are Windows Server 2022, 2019 and Windows 11 VMs. I will be updating the rest of the hosts this weekend so can see what happens then. The qemu-guest-agent tools is the same version running elsewhere even tried to repair it no change. Any ideas? Cheers, Chris.

1 0

Creating new system
by vkasabiev＠gmail.com 04 Nov '22

04 Nov '22

Hello, can you pls help me with creating my oVirt system. I installed Centos 7 on one VM and on one physical server. I succesfully configured my VM for oVirtEngie and I can access to web interface. Now I want to configure my physical server to use it as virtualization server(kvm01). My VM has 2 disks, one for system and one for ISO images. My phisycal server also has 2 disks(actually 4 but in 2 Raid1). One for system and one for virtualization storage. Its the second time I try to install everything properly, 1st time I had some issues and decided to reinstall everything. 1st time I successfully added my kvm01 to my ovirtengine, but I couldnt create any VM because I had error with my Data Center, that had status uninitialized, and it seems like I cant initialize it because I have no domain. I'm already confused and decided to ask forum for a correct answer and advices. What shell I do first? I havent added kvm01 to my ovirtEngine yet.

2 1

Host restarting with error
by Murilo Morais 03 Nov '22

03 Nov '22

Good morning gentlemen. I have a weird problem with a setup I finished. I'm using oVirt 4.4 Hosted Engine with NFS as Storage Domain, it happens that, if the Storage disconnects, in a few minutes the machine restarts and the red LED lights up as if there had been a crash. I managed to capture a screenshot of this moment once, OOM-Killer killed modprobe which doesn't make much sense as there is no VM other than the Hosted Engine and there is 128G of RAM on the machine.

1 0

VNC console connection fails [ovirt 4.5.3.1-1.el8]
by andre.liebe＠gematik.de 02 Nov '22

02 Nov '22

Hello list, is there anybody else out there having problems to connect to a vm console via vnc or is it just me? We are running ovirt-engine 4.5.3.1-1.el8 on up to date ovirt-nodes. I can connect to every virtual machine by spice, but am unable to connect via vnc due to a tls handshake error. Remote-viever just shows "Failed to complete handshake Error in the pull function" (on windows and linux clients). Wireshark tls handshake capture looks supicious to me, server hello message is just 182 bytes long and doesn't coantain a server certificate. Is this normal? sincerely André

2 1

Re: OVS Task Error when Add EL Host
by Federico Cucinella 02 Nov '22

02 Nov '22

Had the same issue, solved by upgrading the hosted-engine

1 0

How can I download multiple disks using wget or curl?
by wodel youchi 31 Oct '22

31 Oct '22

Hi, VM disks can be downloaded from the Manager UI. How can I achieve the same result using curl or wget or something else? I have several disks that I wish to download via script. Could you help with that? Regards.

3 2

mom-vdsm service is failing after update to 4.5.3.2-1.el8
by Jirka Simon 31 Oct '22

31 Oct '22

Hello there, we just updated oVirt engine to 4.5.3.2-1.el8 which was smooth, but then when we start to update all nodes, after restart mom-vdsm service is failing to start mom-vdsm rpm -q vdsm vdsm-4.50.3.4-1.el8.x86_64 (VDSM was updated from 4.50.2.2-1.el8 ) rpm -q mom mom-0.6.3-1.el8.noarch (MOM was not updated duting tha last update) here is error from /var/log/vdsm/mom.log 2022-10-28 13:17:18,105 - mom - INFO - MOM starting 2022-10-28 13:17:18,138 - mom.HostMonitor - INFO - Host Monitor starting 2022-10-28 13:17:18,138 - mom - INFO - hypervisor interface vdsmjsonrpcclient 2022-10-28 13:17:18,179 - mom.HostMonitor - INFO - HostMonitor is ready 2022-10-28 13:17:18,242 - mom.GuestManager - INFO - Guest Manager starting: multi-thread 2022-10-28 13:17:18,247 - mom.Policy - INFO - Loaded policy '00-defines' 2022-10-28 13:17:18,247 - mom - ERROR - Failed to initialize MOM threads Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/mom/__init__.py", line 35, in run host_monitor, guest_manager) File "/usr/lib/python3.6/site-packages/mom/PolicyEngine.py", line 42, in __init__ self.load_policy() File "/usr/lib/python3.6/site-packages/mom/PolicyEngine.py", line 71, in load_policy read_policy(fname, name.split('.policy')[0]) File "/usr/lib/python3.6/site-packages/mom/PolicyEngine.py", line 53, in read_policy return self.policy.set_policy(policy_name, policyStr) File "/usr/lib/python3.6/site-packages/mom/Policy/Policy.py", line 64, in set_policy self.code = get_code(Evaluator(), self._cat_policies()) File "/usr/lib/python3.6/site-packages/mom/Policy/Parser.py", line 543, in get_code tokens = scanner.tokenize(string) File "/usr/lib/python3.6/site-packages/mom/Policy/Parser.py", line 72, in tokenize GenericScanner.tokenize(self, input) File "/usr/lib/python3.6/site-packages/mom/Policy/spark.py", line 78, in tokenize add_lines = self.index2func[i](groups[i], line) TypeError: t_default() takes 2 positional arguments but 3 were given any tip what could be the reason ? Thaak you Jirka

2 2

Nightly build to stable
by Erdősi Péter 29 Oct '22

29 Oct '22

Hi, I've installed the Version 4.5.4-0.2.master.20221007083550.gitb24d914c24.el8 few days before (since the stable not working at the time) Is there any way to make this installation following the stable updates if the 4.5.4 became stable? Regards, Peter -- *Erdősi Péter * /Informatikus, IKT Fejlesztési Főosztály / *Kormányzati Informatikai Fejlesztési Ügynökség * cím: 1134 Budapest, Váci út 35. tel: +36 1 450 3080 e-mail: erdosi.peter(a)kifu.gov.hu <mailto:erdosi.peter@kifu.gov.hu> KIFÜ - www.kifu.gov.hu <http://kifu.gov.hu/kifu/>

1 0

Start Hosted Engine - new installation 4.5.3.1
by nowak.pawel.mail＠gmail.com 28 Oct '22

28 Oct '22

Hi, I am trying to configure "Hosted Engine Deployment". I get a message "The ipaddr filter requires python's netaddr be installed on the ansible controller". I think I have the necessary components installed. How to solve the problem?

4 4

[4.4.7] The latest guest agent needs to be installed and running on the guest
by Christoph Timm 28 Oct '22

28 Oct '22

Hi list, I have upgraded my oVirt from 4.4.4 to 4.4.7 and notice that some VMs have issues to report the performance information via the guest agent. I see the following message on the VMs: The latest guest agent needs to be installed and running on the guest The qemu-guest agent is installed on VMs (the VM OS is CentOS 8). Any advice how to troubleshoot this? I can see the stats will be presented in the GUI, if I migrate the VM to a different host. Best regards Christoph

4 8

Wrong engine version grts installed
by ada per 28 Oct '22

28 Oct '22

Hello, Both node version 4.5.3 and 4.5.2 ate installing the master version. The version of the engine that gets installed is 4.5.4-0.2.master.20221025103923.git936a8fcd09.el8 I do not understand why master version was installed, as I wanted the stable version.

4 13

Linux direct boot kernel/initrd from Data Domain
by Francesco Zaccaria 26 Oct '22

26 Oct '22

Hi, I'm using Ansible ovirt_vm module for automating VM Linux direct boot, but it seems kernel/initrd are not working if uploaded to Data Domain. Same problem starting VM from Ansible playbook and from OLVM web portal. I uploaded kernel/initrd (extracted from Oracle Linux 8.6 ISO) on a Data Domain, both via webconsole and REST APIs; according to doc (http://ovirt.github.io/ovirt-engine-api-model/master/#types/operating_syste…) kernel/initrd can be on ISO storage domain, but it's a deprecated OLVM feature. I have an OLVM cluster (Version 4.4.8.6) with 1 manager, 2 hosts and 2 Fibre Channel Data Domains (I always use first one for VMs). Uploading kernel/initrd on hosts installation works like a charm: kernel_path: /tmp/vmlinuz initrd_path: /tmp/initrd.img kernel_params: "inst.ks.sendmac inst.ks=https://[webserver]ks.cfg ip={{ item.static_ip }}::{{ item.gateway }}:{{ vm_netmask }}::{{ item.nic_name }}:off net.ifnames=0 {% for ip in dns_server %} nameserver={{ ip }} {% endfor %}" kernel_params_persist: false While using Data Domain is not working (disk ID is needed because of alias names not unique): kernel_path: iso://69146b00-4779-47b3-95eb-d2c9bb84e588 initrd_path: iso://6212fb79-e4bb-42ca-ac5c-1da0d0dba7dc At VM booting I get this error, reporting path which is present just on first host (why not on both?): Exit message: unable to set security context 'system_u:object_r:virt_content_t:s0' on '/rhev/data-center/mnt/blockSD/38730c94-68b1-4fde-8a31-8c3870925996/images/69146b00-4779-47b3-95eb-d2c9bb84e588/9797758e-d038-4a50-a188-e3601ad0e539': No such file or directory. Finally, using same full ISO CD attached to VM: kernel_path: iso://b9e8fad1-9884-46a4-8203-9ac73b69ecac initrd_path: iso://b9e8fad1-9884-46a4-8203-9ac73b69ecac I get permission denied (link seems missing, though image is correctly used when booting from CD): Exit message: internal error: process exited while connecting to monitor: 2022-10-26T11:07:07.779657Z qemu-system-x86_64: -blockdev {"driver":"host_device","filename":"/rhev/data-center/mnt/blockSD/38730c94-68b1-4fde-8a31-8c3870925996/images/b9e8fad1-9884-46a4-8203-9ac73b69ecac/48b92374-b4cb-45f6-b388-883abbf691c2","node-name":"libvirt-5-storage","auto-read-only":true,"discard":"unmap"}: Could not open '/rhev/data-center/mnt/blockSD/38730c94-68b1-4fde-8a31-8c3870925996/images/b9e8fad1-9884-46a4-8203-9ac73b69ecac/48b92374-b4cb-45f6-b388-883abbf691c2': Permission denied. I found similar issue opened https://lists.ovirt.org/archives/list/users@ovirt.org/thread/IDIDY6ZLZCRMVM… could the problem be ISO path with Data Storage? https://github.com/oVirt/ovirt-engine/blob/936a8fcd09a4047c03b6cb5bf77709e0…

1 0

build OVA file from ovf file + files with RAW disks
by goosesk blabla 26 Oct '22

26 Oct '22

Hi, for backup VM i use script to create snapshot and then attach disks of VM to backupVM where i do copy of this disk . Also i backup OVF file. for restore , i just upload disk to corupted VM and attach. But ,, if i want to make some easy restore GUI,, it will be easier if i build OVA file from restored OVF and raw disks and then through API just import VM from OVA. The problem is i cannot find any correct way to to build correct OVA file for OVIRT. is there some playbook or script or way ho to do ? thank you Jan

2 1

Async release for ovirt-engine (4.5.3.2) and mom (0.6.4) is now available
by Lev Veyde 26 Oct '22

26 Oct '22

The oVirt Team has just released a new version of ovirt-engine package (4.5.3.2) and mom (0.6.4) that fixes important bugs: - Bug 2137207 <https://bugzilla.redhat.com/2137207> - The RemoveDisk job finishes before the disk was removed from the DB - Bug 2137532 <https://bugzilla.redhat.com/2137532> - MoM functionality is broken in mom-0.6.3-1 - Failed to initialize MOM threads The update is already available on resources.ovirt.org and should land on oVirt mirrors within 24 hours. -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Unable to delete snapshots on vm
by roanne.philip＠voxtelecom.co.za 26 Oct '22

26 Oct '22

Hi I am unable to delete snapshots on VM The error below "Cannot remove Snapshot. Snapshot is currently being created for VM" I have checked with ./taskcleaner.sh no tasks and with ./unlock_entity.sh no locked disks,vm,sanpshots ect But on ovirt UI there is an lock icon on the vm further i have checked the DB engine=# select * from job order by start_time desc; job_id | action_type | description | status | owner_id | visible | start_time | end_time | last_update_time | correlation_id | is_external | is_auto_cleared | engine_session_seq_id --------------------------------------+----------------+------------------------------------------------+--------+--------------------------------------+---------+----------------------------+----------------------------+----------------------------+------------------------------------- -+-------------+-----------------+----------------------- 9aea9f99-406f-45ab-9fe1-8d861b7b00c3 | RemoveSnapshot | Removing Snapshot 01/10/2022 of VM QRADAR_SIEM | FAILED | d6720431-c743-41ca-83e7-34901bc0df88 | t | 2022-10-18 14:00:37.295+02 | 2022-10-18 14:00:37.307+02 | 2022-10-18 14:00:37.307+02 | fb369cc6-8dae-4d57-9017-ae93a0b0237b | f | t | 60043 (1 row) no other running tasks can someone please assist how to get the running snapshot task if there isn't any

3 18

Re: New hosted engine installation, fails to login to the Administration Portal
by Jacob Møller Nielsen 26 Oct '22

26 Oct '22

Hi It seems the old authentication method for local users is or will be depreciated. (internal-authz) It is replaced by internalkeycloak-authz method. I can’t find any way to add local users, but only to use external (LDAP,AD etc..) Please update this if you find a way to do local users. First Name Last Name User Name Authorization provider Namespace E-mail [cid:image001.png@01D8E938.611B0230] admin admin<javascript:;> internal-authz * [cid:image001.png@01D8E938.611B0230] admin@ovirt<javascript:;> internalkeycloak-authz * [cid:image001.png@01D8E938.611B0230] Test Test test<javascript:;> internal-authz * jmn Best Regards [cid:b4r-logo200px_462d7941-ffe2-4f69-8c53-aade89528399.jpg] Jacob Møller Nielsen Senior IT Solution Specialist Mobile +45 30 50 07 20<tel:+45%2030%2050%2007%2020> E-mail jmn(a)b4restore.com<mailto:jmn@b4restore.com> Web www.b4restore.com<http://www.b4restore.com> [cid:linkedin_a3dd4789-eec6-4d7c-8d20-670718e518a6.png]<https://www.linkedin.com/company/b4restore-a-s/> [cid:twitter_14d6b75a-f4b7-45ec-ba88-75a90e22a7be.png] <https://twitter.com/b4restore> [cid:facebook_915c5beb-e98f-46ec-bd13-f86d9235df9b.png] <https://www.facebook.com/B4Restore> [cid:email_d9cf36a4-1bfe-4032-9d73-17a7eb3d40d3.png] <https://www.b4restore.com/en/about-us/newsletter>

1 0

Zanata access request
by Vladimir Talankin 26 Oct '22

26 Oct '22

Hello! I'm writing on behalf of the HOSTVM support team. HOSTVM is a virtualization platform based on Ovirt. For the purposes of improving UI languages, can you please provide us with account details for Zanata ( https://zanata.ovirt.org/)? If any additional information is needed, just let me know. Thank you. Regards, Vladimir

3 5

Re: New hosted engine installation, fails to login to the Administration Portal
by Ada 26 Oct '22

26 Oct '22

1 0

URGENT HELP NEEDED!! Hosts are in non-operational state.
by eugene＠knorydev.com 26 Oct '22

26 Oct '22

Oct 25, 2022, 4:10:01 PM - Failed to connect Host <hostname> to Storage Pool <storage pool> Oct 25, 2022, 4:10:01 PM - Host <hostname> cannot access the Storage Domain(s) VM_Data attached to the <data center>. Setting Host state to Non-Operational. Oct 25, 2022, 4:10:01 PM - Host <hostname> reports about one of the Active Storage Domains as Problematic. Oct 25, 2022, 4:09:52 PM - Activation of host <hostname> initiated by <user>. Hi All, Today morning, noticed that my 1st and 2nd host is in non-operational status and saw that my storage pool isn't being mounted and whenever I try to press Activate under Management, the above error happens. I have multiple VM running and I can't bring it up if it goes down, and it is my production server for my company. Any advise on how to check on this or what logs to look & provide to resolve this? The person who deployed this setup is no longer in my company and I have no one else to seek help for this issue.

4 4

New hosted engine installation, fails to login to the Administration Portal
by Ada 25 Oct '22

25 Oct '22

1 0

ovirt 4.5.3 and missing python3.9 packages
by Nathanaël Blanchet 25 Oct '22

25 Oct '22

Hi, When running hosted-engine --deploy with the el8 ovirt-node, ansible 2.13 uses python3.9 by default. But the installation fails two times because of missing netaddr and jmespath module for python3.9. I suppose the issue is not present in el9 because default python 3.9 presence. The workaround is to install those two packages with pip: dnf install python39-pip --enabelrepo appstream pip3.9 install netaddr jmespath Why not default installing those two packages ?

1 0

Re: OVS Task Error when Add EL Host
by Ada 25 Oct '22

25 Oct '22

2 1

Re: admin user locked out (OVN invalid_grant)
by Mounir MOHELLEBI 25 Oct '22

25 Oct '22

Hi there !!, Can you tel me exactly what is the command you executed to Run /usr/share/ovirt-engine/bin/ovirt-register-sso-client-tool.sh with Client Id: ovirt-provider-ovn Client CA Certificate File Location: /etc/pki/ovirt-engine/certs/engine.cer ??? I executed the following command "/usr/share/ovirt-engine/bin/ovirt-register-sso-client-tool.sh ovirt-provider-ovn" but I obtained this ouput: Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false Oct 25, 2022 8:17:39 AM org.ovirt.engine.ssoreg.core.SsoRegistrationToolExecutor main INFO: ========================================================================= Oct 25, 2022 8:17:39 AM org.ovirt.engine.ssoreg.core.SsoRegistrationToolExecutor main INFO: ================== oVirt Sso Client Registration Tool =================== Oct 25, 2022 8:17:39 AM org.ovirt.engine.ssoreg.core.SsoRegistrationToolExecutor main INFO: ========================================================================= Oct 25, 2022 8:17:39 AM org.ovirt.engine.ssoreg.core.SsoRegistrationToolExecutor main SEVERE: Parameter required but not found: client-id Can you tell how to execute this command properly and how can I find the correct client-id ?? Best regards, MOHELLEBI Mounir Ingénieur système | CIAR Assurances Spa Phone : +213 (0) 21 692 275 | 021 692 527 | 021 691 597 | 021 694 923 Mobile: + 213 561 604 771 Site: https://www.laciar.com Email: m.mohellebi(a)laciar.com<mailto:m.mohellebi@laciar.com> Adresse : 11, Chemin des Crêtes ll Paradou ll Hydra ll Alger ll Algerie IMPORTANT : Ce courriel est une communication confidentielle et l'information qu'il contient est réservée à l'usage exclusif du destinataire. Si vous n'êtes pas le destinataire visé, vous n'avez aucun droit d'utiliser cette information, de la copier, de la distribuer ou de la diffuser. Si cette communication vous a été transmise par erreur, veuillez la détruire et nous en aviser immédiatement par courriel. Nous vous remercions pour votre aide. The information contained and transmitted in this email is confidential, and is intended only for the named recipient to which it is addressed. The content of this email may not have been sent with the authority of the company. If the reader of this message is not the named recipient or a person responsible for delivering it to the named recipient, you are notified that the review, dissemination, distribution, transmission, printing or copying, forwarding, or any other use of this message or any part of it, including any attachments, is strictly prohibited. ________________________________

1 0

Local (Deployment) VM Can't Reach "centos-ceph-pacific" Repo
by Matthew J Black 25 Oct '22

25 Oct '22

Hi All, OK, new issue: :-( If I'm reading things right the local (deployment) vm can't get to the centos-ceph-pacific repo. The repo is installed on the host machine (along with all of the relevant dependant repos). I thought that local 192.168.222.0/24 network was nated out the virbr0 virtual bridge - am I wrong in this (ie do we need to update/change our routing tables/whatever)? Here is the (relevant part) of the log: ~~~ 2022-10-11 16:22:14,749+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.engine_setup : Install oVirt Engine package] 2022-10-11 16:26:03,643+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'results': [], 'rc': 1, 'msg': "Failed to download metadata for repo 'centos-ceph-pacific': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried", 'invocation': {'module_args': {'name': ['ovirt-engine'], 'state': 'present', 'allow_downgrade': False, 'autoremove': False, 'bugfix': False, 'cacheonly': False, 'disable_gpg_check': False, 'disable_plugin': [], 'disablerepo': [], 'download_only': False, 'enable_plugin': [], 'enablerepo': [], 'exclude': [], 'installroot': '/', 'install_repoquery': True, 'install_weak_deps': True, 'security': False, 'skip_broken': False, 'update_cache': False, 'update_only': False, 'validate_certs': True, 'lock_timeout': 30, 'allowerasing': False, 'nobest': False, 'conf_file': None, 'disable_excludes': None, 'download_dir': None, 'list': None, 'releasever': None}}, '_ansible_no_log': False, 'changed': False, ' _ansible_delegated_vars': {'ansible_host': '192.168.222.77', 'ansible_port': None, 'ansible_user': 'root', 'ansible_connection': 'smart'}} 2022-10-11 16:26:03,744+1100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost -> 192.168.222.77]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'centos-ceph-pacific': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried", "rc": 1, "results": []} 2022-10-11 16:26:04,045+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] 2022-10-11 16:26:04,947+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 changed: [localhost -> 192.168.222.77] 2022-10-11 16:26:05,449+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Set destination directory path] 2022-10-11 16:26:05,950+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost -> localhost] 2022-10-11 16:26:06,352+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Create destination directory] 2022-10-11 16:26:06,953+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 changed: [localhost -> localhost] 2022-10-11 16:26:07,355+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] 2022-10-11 16:26:07,856+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost] 2022-10-11 16:26:08,357+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Find the local appliance image] 2022-10-11 16:26:08,959+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost -> localhost] 2022-10-11 16:26:09,460+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path] 2022-10-11 16:26:09,862+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost -> localhost] 2022-10-11 16:26:10,363+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] 2022-10-11 16:26:20,986+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 ok: [localhost -> localhost] 2022-10-11 16:26:21,388+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Copy engine logs] 2022-10-11 16:26:27,901+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 changed: [localhost] 2022-10-11 16:26:28,403+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Change ownership of copied engine logs] 2022-10-11 16:26:29,005+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 changed: [localhost -> localhost] 2022-10-11 16:26:29,506+1100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] 2022-10-11 16:26:29,908+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'msg': 'There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n', '_ansible_no_log': False, 'changed': False} 2022-10-11 16:26:30,008+1100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": false, "msg": "There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} 2022-10-11 16:26:30,410+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 PLAY RECAP [localhost] : ok: 161 changed: 59 unreachable: 0 skipped: 80 failed: 1 2022-10-11 16:26:30,510+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:226 ansible-playbook rc: 2 2022-10-11 16:26:30,510+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:233 ansible-playbook stdout: 2022-10-11 16:26:30,510+1100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:236 ansible-playbook stderr: 2022-10-11 16:26:30,510+1100 DEBUG otopi.plugins.gr_he_ansiblesetup.core.misc misc._closeup:475 {'otopi_host_net': {'ansible_facts': {'otopi_host_net': ['bond0.40', 'ens1', 'bond0.20']}, '_ansible_no_log': False, 'changed': False}, 'otopi_localvm_dir': {'changed': True, 'path': '/var/tmp/localvmfq67djtv', 'uid': 0, 'gid': 0, 'owner': 'root', 'group': 'root', 'mode': '0700', 'state': 'directory', 'secontext': 'unconfined_u:object_r:user_tmp_t:s0', 'size': 6, 'invocation': {'module_args': {'state': 'directory', 'path': '/var/tmp', 'prefix': 'localvm', 'suffix': ''}}, '_ansible_no_log': False}, 'otopi_appliance_disk_size': {'ansible_facts': {'virtual_size': '53689188352'}, '_ansible_no_log': False, 'changed': False}, 'ansible-playbook_rc': 2} 2022-10-11 16:26:30,511+1100 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 509, in _closeup raise RuntimeError(_('Failed executing ansible-playbook')) RuntimeError: Failed executing ansible-playbook 2022-10-11 16:26:30,511+1100 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Closing up': Failed executing ansible-playbook 2022-10-11 16:26:30,512+1100 DEBUG otopi.context context.dumpEnvironment:765 ENVIRONMENT DUMP - BEGIN 2022-10-11 16:26:30,512+1100 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/error=bool:'True' 2022-10-11 16:26:30,512+1100 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/exceptionInfo=list:'[(<class 'RuntimeError'>, RuntimeError('Failed executing ansible-playbook',), <traceback object at 0x7efe2a39fa08>)]' 2022-10-11 16:26:30,512+1100 DEBUG otopi.context context.dumpEnvironment:775 ENV OVEHOSTED_CORE/localVMDir=str:'/var/tmp/localvmfq67djtv' 2022-10-11 16:26:30,512+1100 DEBUG otopi.context context.dumpEnvironment:775 ENV OVEHOSTED_STORAGE/ovfSizeGB=int:'51' 2022-10-11 16:26:30,513+1100 DEBUG otopi.context context.dumpEnvironment:779 ENVIRONMENT DUMP - END ~~~ Anyone got any ideas - thanks: Dulux-Oz

1 2

Failed to delete snapshot
by Jirka Simon 24 Oct '22

24 Oct '22

Hello there. we have troubles with one VM ad it's snapshot here is short log from engine.log 2022-08-23 09:02:38,735+02 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-1265784) [4d79272b-ffac-4b2b-a987-8c19577cd8c4] CommandAsyncTask:: HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object for entity '5842cafc-60d4-4131-8da1-8a909123f08c' 2022-08-23 09:02:41,435+02 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [4d79272b -ffac-4b2b-a987-8c19577cd8c4] Command id: 'ead3fbba-7439-4337-8aaf-1d6cf65bbb15 failed child command status for step 'REDUCE_IMAGE' 2022-08-23 09:02:41,435+02 INFO [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommandCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [ 4d79272b-ffac-4b2b-a987-8c19577cd8c4] Command 'RemoveSnapshotSingleDiskLive' id: 'ead3fbba-7439-4337-8aaf-1d6cf65bbb15' child commands '[5b33d970-6ea0-4b8b-bc31-607afd8af1ca, 185d3fec-8c76- 44d3-a0a1-fe8fff331354, 308baf9d-1fc5-43a1-a624-b5f08f7bec1b, f11f3550-4356-417e-af10-a3afb2051dec, 5842cafc-60d4-4131-8da1-8a909123f08c]' executions were completed, status 'FAILED' 2022-08-23 09:02:42,445+02 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) [4d79272b -ffac-4b2b-a987-8c19577cd8c4] Merging of snapshot '6634db4e-23d8-4849-a008-864f15d28c3d' images 'd24a9199-741b-49cb-96d2-0d76fcd21f48'..'48af3301-0cbb-4a6e-97d1-7299e7de883f' failed. Images have been marked illegal and can no longer be previewed or reverted to. Please retry Live Merge on the snapshot to complete the operation. 2022-08-23 09:02:42,451+02 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) [4d79272b -ffac-4b2b-a987-8c19577cd8c4] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand' with failure. 2022-08-23 09:02:42,457+02 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) [4d79272b-ffac -4b2b-a987-8c19577cd8c4] Command 'RemoveSnapshot' id: '73340ac8-07d7-4de2-bfeb-8062fa1e8cfd' child commands '[ead3fbba-7439-4337-8aaf-1d6cf65bbb15]' executions were completed, status 'FAILE D' 2022-08-23 09:02:43,470+02 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-22) [4d79272b-ffac-4b2b-a98 7-8c19577cd8c4] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand' with failure. 2022-08-23 09:02:43,490+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-22) [4d79272b-ff ac-4b2b-a987-8c19577cd8c4] EVENT_ID: USER_REMOVE_SNAPSHOT_FINISHED_FAILURE(357), Failed to delete snapshot 'vProtect 2022-08-05 22:33:44.088143' for VM 'web1.wiki.prod.hq.sldev.cz-2'. Snapshot can't be deleted, and VM is not possible to clone. thank you for any help. Jirka

7 12

Help - Unable to break bond interface from Ovrit Engine
by Amrit Thakur 23 Oct '22

23 Oct '22

Hi, Currently I am using ovirt 4.3 version with two clusters. Previously I used a bond interface with two NICs for NFS storage. Now I want to use iscsi with multipathing but I didn't find any option to break the bond interface from the ovirt engine GUI. So my question is, is there any way to break the bond interface or if I remove bond interface from node os level, will it sync with the ovirt engine after restart os or vdsm service ? Thank You

2 1

RPM issues updating Ovirt 4.5.2 to 4.5.3
by David Johnson 21 Oct '22

21 Oct '22

Good afternoon all, We are trying to update our cluster from 4.5.2 to see if we can resolve some issues with the VM Web console not functioning on VM's that run on one of the hosts. So there's two problems here, if we can resolve the one (dependency resolution) we are hoping that we can resolve the other with a reinstall of the software. *Symptoms:* 1. On VM's running one one host, the VM web console does not work. The console.vv downloads to the desktop and we can attempt to launch it. On launch, it immediately exits. The web console works on the VM's on the other host. 2. Attempting to update or reinstall the software to any host via the ovirt Compute -> Hosts -> Installation -> Reinstall, or Upgrade menu, we get a dependency resolution error: package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but none of the providers can be installed\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-117.el8s.x86_64 It appears that the 4.5.2 build is running on an older release of openvswitch? Please advise. *Environment:* Production environment: Ovirt 4.5.2.4-1.el8 1 Standalone engine (upgraded to 3 hosts *Log excerpts* *VM Web Console Not Starting:* Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for fe80::f0ca:56ff:fe8c:7bb8 on veth8a5345f. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for veth8a5345f. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for fe80::d879:d5ff:fee4:1855 on vethc9bd12f. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for vethc9bd12f. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for fe80::42:15ff:fe5a:679 on br-1feb13c47a4f. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for 172.22.0.1 on br-1feb13c47a4f. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for br-1feb13c47a4f. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for 172.19.0.1 on docker_gwbridge. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for docker_gwbridge. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for 172.17.0.1 on docker0. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for docker0. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for 172.18.0.1 on br-4209e789b982. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for br-4209e789b982. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for virbr0-nic. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for virbr0. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing address record for 192.168.2.163 on eth0. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for eth0. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Withdrawing workstation service for lo. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Host name conflict, retrying with cen-76-alc-qa-4236 Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for fe80::f0ca:56ff:fe8c:7bb8 on veth8a5345f.*. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for fe80::d879:d5ff:fee4:1855 on vethc9bd12f.*. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for fe80::42:15ff:fe5a:679 on br-1feb13c47a4f.*. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for 172.22.0.1 on br-1feb13c47a4f.IPv4. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for 172.19.0.1 on docker_gwbridge.IPv4. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for 172.17.0.1 on docker0.IPv4. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for 172.18.0.1 on br-4209e789b982.IPv4. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for 192.168.122.1 on virbr0.IPv4. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for fe80::3a72:e773:4d49:55ba on eth0.*. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering new address record for 192.168.2.163 on eth0.IPv4. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Server startup complete. Host name is cen-76-alc-qa-4236.local. Local service cookie is 3875159144. Oct 18 13:22:02 cen-76-alc-qa-163 avahi-daemon[780]: Registering HINFO record with values 'X86_64'/'LINUX'. Oct 18 13:22:02 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:02.828860278-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.695827803-05:00" level=error msg="agent: session failed" backoff=8s error="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\"" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.695994815-05:00" level=info msg="parsed scheme: \"\"" module=grpc Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.696023188-05:00" level=info msg="scheme \"\" not registered, fallback to default scheme" module=grpc Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.696208750-05:00" level=info msg="ccResolverWrapper: sending update to cc: {[{192.168.2.162:2377 <nil> 0 <nil>}] <nil> <nil>}" module=grpc Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.696239844-05:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.696294355-05:00" level=info msg="manager selected by agent for new session: {z80ib665fps13yuqtzqqnltr6 192.168.2.162:2377}" module=node/agent node.id=iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.696355540-05:00" level=info msg="waiting 6.545410435s before registering session" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:04 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:04.697629711-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:05 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:05.699785481-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:07 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:07.247677166-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:10 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:10.062182617-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.242738688-05:00" level=error msg="agent: session failed" backoff=8s error="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\"" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.242918867-05:00" level=info msg="parsed scheme: \"\"" module=grpc Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.242954837-05:00" level=info msg="scheme \"\" not registered, fallback to default scheme" module=grpc Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.243141828-05:00" level=info msg="ccResolverWrapper: sending update to cc: {[{192.168.2.162:2377 <nil> 0 <nil>}] <nil> <nil>}" module=grpc Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.243170522-05:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.243226320-05:00" level=info msg="manager selected by agent for new session: {z80ib665fps13yuqtzqqnltr6 192.168.2.162:2377}" module=node/agent node.id=iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.243290968-05:00" level=info msg="waiting 3.202102632s before registering session" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:11 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:11.244389573-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:12 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:12.246550975-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.073299399-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.446614366-05:00" level=error msg="agent: session failed" backoff=8s error="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\"" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.446832560-05:00" level=info msg="parsed scheme: \"\"" module=grpc Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.446863564-05:00" level=info msg="scheme \"\" not registered, fallback to default scheme" module=grpc Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.447060785-05:00" level=info msg="ccResolverWrapper: sending update to cc: {[{192.168.2.162:2377 <nil> 0 <nil>}] <nil> <nil>}" module=grpc Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.447089843-05:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.447142554-05:00" level=info msg="manager selected by agent for new session: {z80ib665fps13yuqtzqqnltr6 192.168.2.162:2377}" module=node/agent node.id=iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.447206125-05:00" level=info msg="waiting 3.65571267s before registering session" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:14 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:14.448787529-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:15 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:15.450286831-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:17 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:17.254956187-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.103309534-05:00" level=error msg="agent: session failed" backoff=8s error="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\"" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.103525940-05:00" level=info msg="parsed scheme: \"\"" module=grpc Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.103557034-05:00" level=info msg="scheme \"\" not registered, fallback to default scheme" module=grpc Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.103843903-05:00" level=info msg="ccResolverWrapper: sending update to cc: {[{192.168.2.162:2377 <nil> 0 <nil>}] <nil> <nil>}" module=grpc Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.103880439-05:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.103970819-05:00" level=info msg="manager selected by agent for new session: {z80ib665fps13yuqtzqqnltr6 192.168.2.162:2377}" module=node/agent node.id=iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.104034386-05:00" level=info msg="waiting 3.770112424s before registering session" module=node/agent node.id =iz0s4qedzrsxkdcbq6nzvxyfj Oct 18 13:22:18 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:18.105363177-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:19 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:19.107464606-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc Oct 18 13:22:20 cen-76-alc-qa-163 dockerd: time="2022-10-18T13:22:20.460645439-05:00" level=warning msg="grpc: addrConn.createTransport failed to connect to {192.168.2.162:2377 <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 192.168.2.162:2377: connect: connection refused\". Reconnecting..." module=grpc *Host log from update attempt:* 2022-10-17 13:57:22 CDT - { "uuid" : "71edb069-f43c-452b-8528-a0c3d6625fd1", "counter" : 175, "stdout" : "fatal: [192.168.2.18]: FAILED! => {\"changed\": false, \"failures\": [], \"msg\": \"Depsolve Error occurred: \\n Problem 1: package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but none of the providers can be installed\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-117.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-106.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-110.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-115.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-22.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-23.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-24.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-27.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-30.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-32.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-35.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-37.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-39.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-41.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-47.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-48.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-51.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-52.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-53.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-54.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-56.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-6.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-72.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-75.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-80.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-81.el8s.x86_64\\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-88.el8s.x86_64\\n - cannot install the best update candidate for package ovirt-openvswitch-2.15-4.el8.noarch\\n - cannot install the best update candidate for package openvswitch2.15-2.15.0-117.el8s.x86_64\\n Problem 2: package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-119.el8s.x86_64\\n - package openvswitch2.15-ipsec-2.15.0-119.el8s.x86_64 requires python3-openvswitch2.15 = 2.15.0-119.el8s, but none of the providers can be installed\\n - cannot install the best update candidate for package python3-openvswitch2.15-2.15.0-117.el8s.x86_64\\n - cannot install the best update candidate for package openvswitch2.15-ipsec-2.15.0-117.el8s.x86_64\\n Problem 3: package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none of the providers can be installed\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-82.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-21.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-40.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-17.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-29.el8s.x86_64\\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-11.el8s.x86_64\\n - cannot install the best update candidate for package ovn-2021-21.12.0-82.el8s.x86_64\\n - cannot install the best update candidate for package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch\\n Problem 4: package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch requires ovn-2021-host, but none of the providers can be installed\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.12.0-82.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.03.0-21.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.03.0-40.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.06.0-17.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.06.0-29.el8s.x86_64\\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.12.0-11.el8s.x86_64\\n - cannot install the best update candidate for package ovn-2021-host-21.12.0-82.el8s.x86_64\\n - cannot install the best update candidate for package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch\", \"rc\": 1, \"results\": []}", "start_line" : 171, "end_line" : 172, "runner_ident" : "e370b346-b9e8-4a0c-8595-9a717b14c901", "event" : "runner_on_failed", "pid" : 3151, "created" : "2022-10-17T18:57:22.572472", "parent_uuid" : "64006a61-d37f-a54d-f807-000000000042", "event_data" : { "playbook" : "ovirt-host-upgrade.yml", "playbook_uuid" : "b4383145-d80b-4cf6-83a2-550febf56e5c", "play" : "all", "play_uuid" : "64006a61-d37f-a54d-f807-000000000006", "play_pattern" : "all", "task" : "Upgrade packages", "task_uuid" : "64006a61-d37f-a54d-f807-000000000042", "task_action" : "yum", "task_args" : "", "task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-upgrade/tasks/main.yml:49", "role" : "ovirt-host-upgrade", "host" : "192.168.2.18", "remote_addr" : "192.168.2.18", "res" : { "failures" : [ ], "results" : [ ], "rc" : 1, "msg" : "Depsolve Error occurred: \n Problem 1: package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but none of the providers can be installed\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-117.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-106.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-110.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-115.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-119.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-22.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-23.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-24.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-27.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-30.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-32.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-35.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-37.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-39.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-41.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-47.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-48.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-51.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-52.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-53.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-54.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-56.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-6.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-72.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-75.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-80.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-81.el8s.x86_64\n - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-88.el8s.x86_64\n - cannot install the best update candidate for package ovirt-openvswitch-2.15-4.el8.noarch\n - cannot install the best update candidate for package openvswitch2.15-2.15.0-117.el8s.x86_64\n Problem 2: package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-119.el8s.x86_64\n - package openvswitch2.15-ipsec-2.15.0-119.el8s.x86_64 requires python3-openvswitch2.15 = 2.15.0-119.el8s, but none of the providers can be installed\n - cannot install the best update candidate for package python3-openvswitch2.15-2.15.0-117.el8s.x86_64\n - cannot install the best update candidate for package openvswitch2.15-ipsec-2.15.0-117.el8s.x86_64\n Problem 3: package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none of the providers can be installed\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-82.el8s.x86_64\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-21.el8s.x86_64\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-40.el8s.x86_64\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-17.el8s.x86_64\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-29.el8s.x86_64\n - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-11.el8s.x86_64\n - cannot install the best update candidate for package ovn-2021-21.12.0-82.el8s.x86_64\n - cannot install the best update candidate for package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch\n Problem 4: package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch requires ovn-2021-host, but none of the providers can be installed\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.12.0-82.el8s.x86_64\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.03.0-21.el8s.x86_64\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.03.0-40.el8s.x86_64\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.06.0-17.el8s.x86_64\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.06.0-29.el8s.x86_64\n - package rdo-ovn-host-2:22.06-3.el8.noarch obsoletes ovn-2021-host < 22.06 provided by ovn-2021-host-21.12.0-11.el8s.x86_64\n - cannot install the best update candidate for package ovn-2021-host-21.12.0-82.el8s.x86_64\n - cannot install the best update candidate for package ovirt-openvswitch-ovn-host-2.15-4.el8.noarch", "invocation" : { "module_args" : { "name" : [ "*" ], "state" : "latest", "allow_downgrade" : false, "autoremove" : false, "bugfix" : false, "cacheonly" : false, "disable_gpg_check" : false, "disable_plugin" : [ ], "disablerepo" : [ ], "download_only" : false, "enable_plugin" : [ ], "enablerepo" : [ ], "exclude" : [ ], "installroot" : "/", "install_repoquery" : true, "install_weak_deps" : true, "security" : false, "skip_broken" : false, "update_cache" : false, "update_only" : false, "validate_certs" : true, "lock_timeout" : 30, "allowerasing" : false, "nobest" : false, "conf_file" : null, "disable_excludes" : null, "download_dir" : null, "list" : null, "releasever" : null } }, "_ansible_no_log" : false, "changed" : false }, "start" : "2022-10-17T18:57:19.992530", "end" : "2022-10-17T18:57:22.572294", "duration" : 2.579764, "ignore_errors" : null, "event_loop" : null, "uuid" : "71edb069-f43c-452b-8528-a0c3d6625fd1" } } *David Johnson*

6 11