- Users - oVirt List Archives

How to use Python to manage each node in batches, because I want to send some scripts to nodes in batches
by ZiYi Liu 21 Aug '23

21 Aug '23

By default, find the management in engine-web and use ssh management to restart and stop the node node. Can I get the host's secret key or other login information to log in through Python, and then send some commands or scripts?

4 4

Update path of hosted_storage domain
by francesco＠shellrent.com 18 Aug '23

18 Aug '23

Hello everyone, we have a self hosted engine environment (oVirt 4.4.5) that use a replica 2 + arbiter glusterfs. Those servers are both glusterfs nodes and oVirt node of the hosted engine. For an upgrade we followed this guide https://access.redhat.com/documentation/it-it/red_hat_hyperconverged_infras…. The planned upgrade was adding 2 new servers (node3 and node4) that would replace the existing ones. We added to oVirt cluster and the glusterfs pool the servers and moved the engine in those new hosts, without touching the underlay glusterfs configuration. After the step n° 18 ("Reboot the existing and replacement hosts.Wait until all hosts are available before continuing.") of the guide we tried to start the engine but we got error on the hosted_storage domain due to old path (the glusterfs mounted path was "node1" and the backupvolfile was "node2"). For avoiding corruption we updated the database with the correct path and mount options accordly with the new configuration edited in the file /etc/ovirt-hosted-engine/hosted-engine.conf (as written in the guide). If we try to detach the node1 brick everything stop working causing storage error. We noticed that reference of node1 is still present in the file /rhev/data-center/mnt/glusterSD/node1.ovirt.xyz:_engine/36c75f6e-d95d-48f4-9ceb-ad2895ab2123/dom_md/metadata, on both of new hosts (node3 and node4). I'll be more than glad to attach any log file needed for understanding what's going on, and thank you whoever will take time for helping me out :) Regards, Francesco

1 0

Task Configure OVN for oVirt failed to execute
by Jorge Visentini 15 Aug '23

15 Aug '23

Hi, I am trying to reinstall this host, but I cannot because of this issue. Any tips for me? Host ksmmi1r01ovirt20.kosmo.cloud installation failed. Task Configure OVN for oVirt failed to execute. Please check logs for more details: /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20230815194759-ksmmi1r01ovirt20.kosmo.cloud-63609c39-934a-4360-a822-f2f6935cc5b6.log. "stdout" : "fatal: [ksmmi1r01ovirt20.kosmo.cloud]: FAILED! => {\"changed\": true, \"cmd\": [\"vdsm-tool\", \"ovn-config\", \"10.250.156.20\", \"ksmmi1r01ovirt20.kosmo.cloud\"], \"delta\": \"0:00:02.319187\", \"end\": \"2023-08-15 19:50:05.483458\", \"msg\": \"non-zero return code\", \"rc\": 1, \"start\": \"2023-08-15 19:50:03.164271\", \"stderr\": \"Traceback (most recent call last):\\n File \\\"/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py\\\", line 117, in get_network\\n return networks[net_name]\\nKeyError: 'ksmmi1r01ovirt20.kosmo.cloud'\\n\\nDuring handling of the above exception, another exception occurred:\\n\\nTraceback (most recent call last):\\n File \\\"/usr/bin/vdsm-tool\\\", line 195, in main\\n return tool_command[cmd][\\\"command\\\"](*args)\\n File \\\"/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py\\\", line 63, in ovn_config\\n ip_address = get_ip_addr(get_network(network_caps(), net_name))\\n File \\\"/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py\\\", line 119, in get_network\\n raise NetworkNotFoundError(net_name)\\nvdsm.tool.ovn_config.NetworkNotFoundError: ksmmi1r01ovirt20.kosmo.cloud\", \"stderr_lines\": [\"Traceback (most recent call last):\", \" File \\\"/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py\\\", line 117, in get_network\", \" return networks[net_name]\", \"KeyError: 'ksmmi1r01ovirt20.kosmo.cloud'\", \"\", \"During handling of the above exception, another exception occurred:\", \"\", \"Traceback (most recent call last):\", \" File \\\"/usr/bin/vdsm-tool\\\", line 195, in main\", \" return tool_command[cmd][\\\"command\\\"](*args)\", \" File \\\"/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py\\\", line 63, in ovn_config\", \" ip_address = get_ip_addr(get_network(network_caps(), net_name))\", \" File \\\"/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py\\\", line 119, in get_network\", \" raise NetworkNotFoundError(net_name)\", \"vdsm.tool.ovn_config.NetworkNotFoundError: ksmmi1r01ovirt20.kosmo.cloud\"], \"stdout\": \"\", \"stdout_lines\": []}", [root@ksmmi1r01ovirt20 ~]# vdsm-tool ovn-config 10.250.156.20 ksmmi1r01ovirt20.kosmo.cloud Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py", line 117, in get_network return networks[net_name] KeyError: 'ksmmi1r01ovirt20.kosmo.cloud' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/vdsm-tool", line 195, in main return tool_command[cmd]["command"](*args) File "/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py", line 63, in ovn_config ip_address = get_ip_addr(get_network(network_caps(), net_name)) File "/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py", line 119, in get_network raise NetworkNotFoundError(net_name) vdsm.tool.ovn_config.NetworkNotFoundError: ksmmi1r01ovirt20.kosmo.cloud [root@ksmmi1r01ovirt20 ~]# vdsm-tool list-nets ovirtmgmt (default route) -- Att, Jorge Visentini +55 55 98432-9868

1 0

oVirt 4.5.5 snapshot - Migration failed due to an Error: Fatal error during migration
by Jorge Visentini 13 Aug '23

13 Aug '23

Any tips about this error? 2023-08-10 18:24:57,544-03 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-4) [633be3a0-3afd-490c-b412-805d2b14e1c2] Lock Acquired to object 'EngineLock:{exclusiveLocks='[29032e83-cfaf-4d30-bcc2-df72c5358552=VM]', sharedLocks=''}' 2023-08-10 18:24:57,578-03 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-4) [633be3a0-3afd-490c-b412-805d2b14e1c2] Running command: MigrateVmToServerCommand internal: false. Entities affected : ID: 29032e83-cfaf-4d30-bcc2-df72c5358552 Type: VMAction group MIGRATE_VM with role type USER 2023-08-10 18:24:57,628-03 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-4) [633be3a0-3afd-490c-b412-805d2b14e1c2] START, MigrateVDSCommand( MigrateVDSCommandParameters:{hostId='282b69aa-8b74-4312-8cc0-9c20e01982b7', vmId='29032e83-cfaf-4d30-bcc2-df72c5358552', srcHost='ksmmi1r01ovirt18', dstVdsId='73c38b36-36da-4ffa-b17a-492fd7b093ae', dstHost='ksmmi1r01ovirt19:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', migrateEncrypted='false', consoleAddress='null', maxBandwidth='3125', parallel='null', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='10.250.156.19', cpusets='null', numaNodesets='null'}), log id: 5bbc21d6 2023-08-10 18:24:57,628-03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-4) [633be3a0-3afd-490c-b412-805d2b14e1c2] START, MigrateBrokerVDSCommand(HostName = ksmmi1r01ovirt18, MigrateVDSCommandParameters:{hostId='282b69aa-8b74-4312-8cc0-9c20e01982b7', vmId='29032e83-cfaf-4d30-bcc2-df72c5358552', srcHost='ksmmi1r01ovirt18', dstVdsId='73c38b36-36da-4ffa-b17a-492fd7b093ae', dstHost='ksmmi1r01ovirt19:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', migrateEncrypted='false', consoleAddress='null', maxBandwidth='3125', parallel='null', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='10.250.156.19', cpusets='null', numaNodesets='null'}), log id: 14d92c9 2023-08-10 18:24:57,631-03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-4) [633be3a0-3afd-490c-b412-805d2b14e1c2] FINISH, MigrateBrokerVDSCommand, return: , log id: 14d92c9 2023-08-10 18:24:57,634-03 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-4) [633be3a0-3afd-490c-b412-805d2b14e1c2] FINISH, MigrateVDSCommand, return: MigratingFrom, log id: 5bbc21d6 2023-08-10 18:24:57,639-03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-4) [633be3a0-3afd-490c-b412-805d2b14e1c2] EVENT_ID: VM_MIGRATION_START(62), Migration started (VM: ROUTER, Source: ksmmi1r01ovirt18, Destination: ksmmi1r01ovirt19, User: admin@ovirt @internalkeycloak-authz). 2023-08-10 18:24:57,641-03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-13) [] VM '29032e83-cfaf-4d30-bcc2-df72c5358552'(ROUTER) moved from 'MigratingFrom' --> 'Up' 2023-08-10 18:24:57,641-03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-13) [] Adding VM '29032e83-cfaf-4d30-bcc2-df72c5358552'(ROUTER) to re-run list 2023-08-10 18:24:57,643-03 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (ForkJoinPool-1-worker-13) [] Rerun VM '29032e83-cfaf-4d30-bcc2-df72c5358552'. Called from VDS 'ksmmi1r01ovirt18' 2023-08-10 18:24:57,679-03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-2194) [] START, MigrateStatusVDSCommand(HostName = ksmmi1r01ovirt18, MigrateStatusVDSCommandParameters:{hostId='282b69aa-8b74-4312-8cc0-9c20e01982b7', vmId='29032e83-cfaf-4d30-bcc2-df72c5358552'}), log id: 445b81e0 2023-08-10 18:24:57,681-03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-2194) [] FINISH, MigrateStatusVDSCommand, return: org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusReturn@12cb7b1b, log id: 445b81e0 2023-08-10 18:24:57,695-03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-2194) [] EVENT_ID: VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed due to an Error: Fatal error during migration (VM: ROUTER, Source: ksmmi1r01ovirt18, Destination: ksmmi1r01ovirt19). 2023-08-10 18:24:57,698-03 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (EE-ManagedThreadFactory-engine-Thread-2194) [] Lock freed to object 'EngineLock:{exclusiveLocks='[29032e83-cfaf-4d30-bcc2-df72c5358552=VM]', sharedLocks=''}' ovirt-release-master-4.5.5-0.0.master.20230612064154.git0c65b0e.el9.noarch ovirt-imageio-common-2.5.1-0.202307060620.git4e5f7e0.el9.x86_64 python3-ovirt-engine-sdk4-4.6.3-0.1.master.20230324091708.el9.x86_64 ovirt-openvswitch-ovn-2.17-1.el9.noarch ovirt-openvswitch-ovn-common-2.17-1.el9.noarch ovirt-openvswitch-ovn-host-2.17-1.el9.noarch ovirt-imageio-client-2.5.1-0.202307060620.git4e5f7e0.el9.x86_64 ovirt-imageio-daemon-2.5.1-0.202307060620.git4e5f7e0.el9.x86_64 python3-ovirt-setup-lib-1.3.4-0.0.master.20220413133253.gitd32d35f.el9.noarch python3.11-ovirt-engine-sdk4-4.6.3-0.1.master.20230324091708.el9.x86_64 python3.11-ovirt-imageio-common-2.5.1-0.202307060620.git4e5f7e0.el9.x86_64 python3.11-ovirt-imageio-client-2.5.1-0.202307060620.git4e5f7e0.el9.x86_64 ovirt-ansible-collection-3.1.3-0.1.master.20230420113738.el9.noarch ovirt-vmconsole-1.0.9-2.el9.noarch ovirt-vmconsole-host-1.0.9-2.el9.noarch ovirt-openvswitch-2.17-1.el9.noarch ovirt-python-openvswitch-2.17-1.el9.noarch ovirt-openvswitch-ipsec-2.17-1.el9.noarch python3-ovirt-node-ng-nodectl-4.4.3-0.20220615.0.el9.noarch ovirt-node-ng-nodectl-4.4.3-0.20220615.0.el9.noarch ovirt-host-dependencies-4.5.0-3.1.20220510094000.git2f2d022.el9.x86_64 ovirt-hosted-engine-ha-2.5.1-0.0.master.20220707064804.20220707064802.git14b1139.el9.noarch ovirt-provider-ovn-driver-1.2.37-0.20220610132522.git62111d0.el9.noarch ovirt-hosted-engine-setup-2.7.1-0.0.master.20230414113600.git340e19b.el9.noarch ovirt-host-4.5.0-3.1.20220510094000.git2f2d022.el9.x86_64 ovirt-release-host-node-4.5.5-0.0.master.20230612064150.git0c65b0e.el9.x86_64 ovirt-node-ng-image-update-placeholder-4.5.5-0.0.master.20230612064150.git0c65b0e.el9.noarch qemu-kvm-tools-8.0.0-6.el9.x86_64 qemu-kvm-docs-8.0.0-6.el9.x86_64 qemu-kvm-common-8.0.0-6.el9.x86_64 qemu-kvm-device-display-virtio-gpu-8.0.0-6.el9.x86_64 qemu-kvm-ui-opengl-8.0.0-6.el9.x86_64 qemu-kvm-ui-egl-headless-8.0.0-6.el9.x86_64 qemu-kvm-device-display-virtio-gpu-pci-8.0.0-6.el9.x86_64 qemu-kvm-block-blkio-8.0.0-6.el9.x86_64 qemu-kvm-device-display-virtio-vga-8.0.0-6.el9.x86_64 qemu-kvm-device-usb-host-8.0.0-6.el9.x86_64 qemu-kvm-device-usb-redirect-8.0.0-6.el9.x86_64 qemu-kvm-audio-pa-8.0.0-6.el9.x86_64 qemu-kvm-block-rbd-8.0.0-6.el9.x86_64 qemu-kvm-core-8.0.0-6.el9.x86_64 qemu-kvm-8.0.0-6.el9.x86_64 libvirt-daemon-kvm-9.3.0-2.el9.x86_64 Cheers! -- Att, Jorge Visentini +55 55 98432-9868

3 4

CPU support Xeon E5345
by Mikhail Po 11 Aug '23

11 Aug '23

Is it possible to install oVirt 4.3/4.4 on ProLiant BL460c G1 with Intel Xeon E5345 processor(a)2.33GHz ? In case of a setup failure, [ERROR] is fatal:[localhost]: FAILED!=>{"Changed":false,"message":"The host was inoperable, deployment errors: code 156:Host host1.test.com disabled because the host CPU type in this case is not supported by the cluster compatibility version or is not supported at all, code 9000: Failed to check the power management configuration for the host host1.test.com ., correct accordingly and re-deploy."

2 2

Trouble restoring + upgrading to ovirt 4.5 system after host crashed
by David Johnson 09 Aug '23

09 Aug '23

Good afternoon all, We had a confluence of events hit all at once and need help desperately. Our Ovirt engine system recently crashed and is unrecoverable. Due to a power maintenance event at the data center, 1/3 of our VM's are offline. I have recent backups from the engine created with engine-backup. I installed a clean Centos 9 and followed the directions to install the ovirt-engine . After I restore the backup, the engine-setup fails on the keycloak configuration. *From clean system:* *Install: **(Observe failed scriptlet during install, but rom install still succeeds)* [root@ovirt2 administrator]# dnf install -y ovirt-engine Last metadata expiration check: 2:08:15 ago on Tue 08 Aug 2023 10:11:31 AM CDT. Dependencies resolved. ============================================================================================================================================================= Package Architecture Version Repository Size ============================================================================================================================================================= Installing: ovirt-engine noarch 4.5.4-1.el9 centos-ovirt45 13 M Installing dependencies: SuperLU x86_64 5.3.0-2.el9 epel 182 k (Snip ...) * Running scriptlet: ovirt-vmconsole-1.0.9-1.el9.noarch 60/425Failed to resolve allow statement at /var/lib/selinux/targeted/tmp/modules/400/ovirt_vmconsole/cil:539Failed to resolve AST/usr/sbin/semodule: Failed!* (Snip ...) xmlrpc-common-3.1.3-1.1.el9.noarch xorg-x11-fonts-ISO8859-1-100dpi-7.5-33.el9.noarch zziplib-0.13.71-9.el9.x86_64 Complete! *Engine-restore (no visible issues):* [root@ovirt2 administrator]# engine-backup --mode=restore --log=restore1.log --file=Downloads/engine-2023-08-06.22.00.02.bak --provision-all-databases --restore-permissions Start of engine-backup with mode 'restore' scope: all archive file: Downloads/engine-2023-08-06.22.00.02.bak log file: restore1.log Preparing to restore: - Unpacking file 'Downloads/engine-2023-08-06.22.00.02.bak' Restoring: - Files ------------------------------------------------------------------------------ Please note: Operating system is different from the one used during backup. Current operating system: centos9 Operating system at backup: centos8 Apache httpd configuration will not be restored. You will be asked about it on the next engine-setup run. ------------------------------------------------------------------------------ Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' - user 'ovirt_engine_history', database 'ovirt_engine_history' - user 'ovirt_engine_history_grafana' on database 'ovirt_engine_history' Restoring: - Engine database 'engine' - Cleaning up temporary tables in engine database 'engine' - Updating DbJustRestored VdcOption in engine database - Resetting DwhCurrentlyRunning in dwh_history_timekeeping in engine database - Resetting HA VM status ------------------------------------------------------------------------------ Please note: The engine database was backed up at 2023-08-06 22:00:19.000000000 -0500 . Objects that were added, removed or changed after this date, such as virtual machines, disks, etc., are missing in the engine, and will probably require recovery or recreation. ------------------------------------------------------------------------------ - DWH database 'ovirt_engine_history' - Grafana database '/var/lib/grafana/grafana.db' You should now run engine-setup. Done. [root@ovirt2 administrator]# *Engine-setup :* [root@ovirt2 administrator]# engine-setup [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, /etc/ovirt-engine-setup.conf.d/10-packaging.conf, /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20230808124501-joveku.log Version: otopi-1.10.3 (otopi-1.10.3-1.el9) [ INFO ] The engine DB has been restored from a backup *[ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to Keycloak database 'ovirt_engine_keycloak' using existing credentials: ovirt_engine_keycloak@localhost:5432*[ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20230808124501-joveku.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20230808124504-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination *[ ERROR ] Execution of setup failed[root@ovirt2 administrator]#* *Engine-cleanup results:* (snip) [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-remove-20230808120445-mj4eef.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20230808120508-cleanup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ INFO ] Execution of cleanup completed successfully [root@cen-90-tmpl administrator]# *Engine backup (restore) results:* [root@ovirt2 administrator]# engine-backup --mode=restore --log=restore1.log --file=Downloads/engine-2023-08-06.22.00.02.bak --provision-all-databases --restore-permissions Start of engine-backup with mode 'restore' scope: all archive file: Downloads/engine-2023-08-06.22.00.02.bak log file: restore1.log Preparing to restore: - Unpacking file 'Downloads/engine-2023-08-06.22.00.02.bak' Restoring: - Files ------------------------------------------------------------------------------ Please note: Operating system is different from the one used during backup. Current operating system: centos9 Operating system at backup: centos8 Apache httpd configuration will not be restored. You will be asked about it on the next engine-setup run. ------------------------------------------------------------------------------ Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' *FATAL: Existing database 'engine' or user 'engine' found and temporary ones created - Please clean up everything and try again* Any advice would be appreciated. *David Johnson*

2 2

Trouble restoring + upgrading to ovirt 4.5 system after host crashed
by David Johnson 08 Aug '23

08 Aug '23

Update: I have confirmed the original ovirt version has an ovirt_engine_keycloak database, but the database was not backed up by the engine-backup command *David Johnson* *Director of Development, Maxis Technology* 844.696.2947 ext 702 (o) | 479.531.3590 (c) <https://www.linkedin.com/in/pojoguy/> <https://maxistechnology.com/wp-content/uploads/vcards/vcard-David_Johnson.v…> <https://maxistechnology.com/> *Follow us:* <https://www.linkedin.com/company/maxis-tech-inc/>

1 1

ovirt node NonResponsive
by carlos.mendes＠mgo.cv 08 Aug '23

08 Aug '23

Hello, I have ovirt with two nodes and one that are NonResponsive and and cant manage them because they are in Unknown state. It seems that nodes lost connection for a while with their gateway. The node (ovirt2) however is having consistent problems. The follow sequence of events is reproducible and is causing the host to enter a "NonOperational" state on the cluster: What is the proper way of restoring management? I have a two-node cluster with the ovirt manager running standlone on the virtual maachine CentOS-Stream-9 and the ovirt node running the most recent oVirt Node 4.5.4 software. I can then re-activate ovirt2, which appears as green for approximately 5 minutes and then repeats all of the above issues. What can I do to troubleshoot this?

1 0

How restore nodes ovirt UP from NonResponsive and VMs executing
by José Pascual 08 Aug '23

08 Aug '23

Hello, I have ovirt with two nodes that are NonResponsive and all the VMs are properly executing but i cant manage them because are in Unknown state. It seems that nodes lost connection for a while with their gateway. I have thought of first restarting the node where the engine is not running and trying to put in UP. Then restart the engine from within de VM to see if it starts up on this node. What is the proper way of restoring management? I Thanks, Best Regards -- Saludos, José Pascual Gallud Martínez Nombre | Dpto. Ingeniería <http://telfy.com/>

3 2

Re: Some problems with ovirt
by אריה קלטר 07 Aug '23

07 Aug '23

Hi, Sorry for the late reply I tried now to get logs for the vm, for the scenario of stucked in the middle of the power up because of no disk. The vm id is 486cea97-ed56-47d4-930b-5f85c51ad3cf, the vm name is kc26-1 [image: image.png] About the second problem, with the migration, i also attached the logs here, both from the source and from the destination server. Any clue how to solve the problems? It is רeally annoying that a lot of times when I am trying to power on the vm it hangs like that, and when the system is doing live migration for the engine vm it is always not working and I need to power it off and on manually from the cli. For both scenarios i uploaded bot the /var/log/vdsm/vdsm.log and /var/log/libvirt/qemu/<vmname>.log

1 0

Certificates expired...
by Jason P. Thomas 07 Aug '23

07 Aug '23

We're moving to a new facility and pretty much building the infrastructure out from scratch. As such, the oVirt 4.4 cluster at our old location has floated under notice because it has just worked for years. In July it seems some of the certs expired (specifically the engine apache cert) and we just noticed it. I followed a post for changing the apache cert and that allowed us to login to the engine web interface, but nothing in the interface showed as connected. VMs are still running, I even rebooted one via ssh before realizing the certificate issues. In "Events" in the engine, it was complaining about certs being expired on the hosts. I found this post to this mailing list and followed the instructions possibly in error: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NHJNETOIMSHDXM… Now the engine won't start at all and I'm afraid I'm one power outage away from complete disaster. I need to keep the old location up and functioning for another 4-6 months, so any insights would be greatly appreciated. Sincerely, Jason P. Thomas

5 11

Problems running CentOS 9 Stream GenericCloud guests
by Gianluca Amato 04 Aug '23

04 Aug '23

Hello everyone, I'm trying to run CentOS 9 Stream GenericCloud as a guest in oVirt 4.5.4. While the images in the ovirt-image-repository seems to work fine (in particular, I've tried version 20211119.0), the latest version (20230727.1) does not start. After the initial boot messages, it gives the error: Starting dracut mount hook dracut-mount[413]: Warning: Can't mount root filesystem Starting dracut emergency shell and brings me to the emergency shell. Is this some known bug ? Note that if I start from the old image and then upgrade all the packages, I have no problems at all. Thanks in advance for any help. Gianluca

2 1

Installing oVirt as a self-hosted engine - big big problem :()
by Jorge Visentini 03 Aug '23

03 Aug '23

Hi guys, starting the weekend with a "cucumber" like that in my hands. I've been racking my brains for about 4 days to deploy a new engine. Turns out I already tested *4.4.10*, *4.5.4.x*, and *4.5.5(master)* (el8 and el9) and none is working. It seems to me to be ansible or a python problem, but I'm not sure. I've read several oVirt reddit and github threads, but they seem to have no effect anymore. I believe it's some package in the CentOS Stream repositories, *but unfortunately I don't have it frozen locally here*. Deploy hangs at *[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up]* I already tried to update the version of *python netaddr* as I read in git and it still didn't work I also tried to *freeze the ansible update* in the engine and it didn't work. I updated the version of *ovirt-ansible-collection to ovirt-ansible-collection-3.1.3-0.1.master.20230420113738.el8.noarch.rpm* and it didn't work either... *The error seems to be on all oVirt builds*, but I don't know what I'm doing wrong anymore because I can't pinpoint where the error is. I appreciate any tips *Below are some log outputs:* [root@ksmmi1r02ovirt36 ~]# tail -f /var/log/vdsm/vdsm.log 2023-07-07 22:23:30,144-0300 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=6df1f5ed-0f41-4001-bb2e-e50fb0214ac7 (api:37) 2023-07-07 22:23:30,144-0300 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723) 2023-07-07 22:23:35,146-0300 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList() from=internal, task_id=bd2a755d-3488-4b43-8ca4-44717dd6b017 (api:31) 2023-07-07 22:23:35,146-0300 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=bd2a755d-3488-4b43-8ca4-44717dd6b017 (api:37) 2023-07-07 22:23:35,146-0300 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723) 2023-07-07 22:23:39,320-0300 INFO (periodic/3) [vdsm.api] START repoStats(domains=()) from=internal, task_id=68567ce3-b579-469d-a46d-7bafc7b3e6bd (api:31) 2023-07-07 22:23:39,320-0300 INFO (periodic/3) [vdsm.api] FINISH repoStats return={} from=internal, task_id=68567ce3-b579-469d-a46d-7bafc7b3e6bd (api:37) 2023-07-07 22:23:40,151-0300 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList() from=internal, task_id=fadcf734-9f7e-4681-8764-9d3863718644 (api:31) 2023-07-07 22:23:40,151-0300 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=fadcf734-9f7e-4681-8764-9d3863718644 (api:37) 2023-07-07 22:23:40,151-0300 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723) 2023-07-07 22:23:44,183-0300 INFO (jsonrpc/1) [api.host] START getAllVmStats() from=::1,49920 (api:31) 2023-07-07 22:23:44,184-0300 INFO (jsonrpc/1) [api.host] FINISH getAllVmStats return={'status': {'code': 0, 'message': 'Done'}, 'statsList': (suppressed)} from=::1,49920 (api:37) 2023-07-07 22:23:45,157-0300 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList() from=internal, task_id=504d8028-35be-45a3-b24d-4ec7cbc82f7e (api:31) 2023-07-07 22:23:45,157-0300 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=504d8028-35be-45a3-b24d-4ec7cbc82f7e (api:37) 2023-07-07 22:23:45,157-0300 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723) 2023-07-07 22:23:50,162-0300 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList() from=internal, task_id=297ad1df-c855-4fbb-a89f-dfbe7a1b60a2 (api:31) 2023-07-07 22:23:50,162-0300 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=297ad1df-c855-4fbb-a89f-dfbe7a1b60a2 (api:37) 2023-07-07 22:23:50,162-0300 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723) [root@ksmmi1r02ovirt36 ~]# journalctl -f -- Logs begin at Fri 2023-07-07 21:57:13 -03. -- Jul 07 22:24:46 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[13790]: 13791 still running (86045) Jul 07 22:24:50 ksmmi1r02ovirt36.kosmo.cloud platform-python[22812]: ansible-ovirt_host_info Invoked with pattern=name=ksmmi1r02ovirt36.kosmo.cloud auth={'token': 'eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICIyZzVfWUdWX08wSFJoWnlVeFNkdGl4d0liRWV6Wkp5NTgwN3BaXzUxelBvIn0.eyJleHAiOjE2ODg3OTY0MzAsImlhdCI6MTY4ODc3OTE1MCwianRpIjoiOTBlOWE5ZTAtMmExNS00MzNiLWIxOGQtMmUwNmI4MTQ5NGE2IiwiaXNzIjoiaHR0cHM6Ly9rc21lbmdpbmUwMS5rb3Ntby5jbG91ZC9vdmlydC1lbmdpbmUtYXV0aC9yZWFsbXMvb3ZpcnQtaW50ZXJuYWwiLCJhdWQiOiJhY2NvdW50Iiwic3ViIjoiYWRkMWMyYzYtYzJjMy00N2M4LWI1ODUtNGI2MTU2ZDAxYTE3IiwidHlwIjoiQmVhcmVyIiwiYXpwIjoib3ZpcnQtZW5naW5lLWludGVybmFsIiwic2Vzc2lvbl9zdGF0ZSI6IjNhMWUzZTU2LWIyZTUtNGMyYi05YTIxLThjZjE1YzY4NzlmNiIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cHM6Ly9rc21lbmdpbmUwMS5rb3Ntby5jbG91ZCJdLCJyZWFsbV9hY2Nlc3MiOnsicm9sZXMiOlsiZGVmYXVsdC1yb2xlcy1vdmlydC1pbnRlcm5hbCIsIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iXX0sInJlc291cmNlX2FjY2VzcyI6eyJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6Im92aXJ0LWV4dD10b2tlbjpwYXNzd29yZC1hY2Nlc3Mgb3ZpcnQtZXh0PXRva2VuLWluZm86cHVibGljLWF1dGh6LXNlYXJjaCBvdmlydC1hcHAtYXBpIG92aXJ0LWV4dD10b2tlbi1pbmZvOnZhbGlkYXRlIHByb2ZpbGUgZW1haWwgb3ZpcnQtZXh0PXRva2VuLWluZm86YXV0aHotc2VhcmNoIiwic2lkIjoiM2ExZTNlNTYtYjJlNS00YzJiLTlhMjEtOGNmMTVjNjg3OWY2IiwiZW1haWxfdmVyaWZpZWQiOmZhbHNlLCJncm91cHMiOlsiL292aXJ0LWFkbWluaXN0cmF0b3IiXSwicHJlZmVycmVkX3VzZXJuYW1lIjoiYWRtaW5Ab3ZpcnQiLCJlbWFpbCI6ImFkbWluQGxvY2FsaG9zdCJ9.o9PsulNw0urPphWITcB6Y3wpHQiiQ0v00su6XorITcvNElzkfHqyYfJd8W-kIfgElh6BNnCmYyIwtX7t3T4-PiLgDdipH1J9uzuDBXkmNBNcVmFimfUAqyC8aUITK56CqZ5TyRyHqhOicPciqGSY8R98hQ8I8y11w2RiIFT0rQYnRev75gjKoqUH29uNyeCAdTyKvPSGHNm1pLLrtPUmk-JCGmsYytNRCMHAPoNIlZP3k94PbQ9pI4jZ5O7kcRSgJik8tUDOVglcL4g0MoAJwracek2MUTvK8pDpRghI9hSQVLFtAXCyGRxfHHzTko4EbHBbFlz5s3pfs2kbF6TFmw', 'url': 'https://ksmengine01.kosmo.cloud/ovirt-engine/api', 'ca_file': None, 'insecure': True, 'timeout': 0, 'compress': True, 'kerberos': False, 'headers': None, 'hostname': None, 'username': None, 'password': None} fetch_nested=False nested_attributes=[] follow=[] all_content=False cluster_version=None Jul 07 22:24:51 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[13790]: 13791 still running (86040) Jul 07 22:24:56 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[13790]: 13791 still running (86035) Jul 07 22:25:00 ksmmi1r02ovirt36.kosmo.cloud platform-python[22829]: ansible-ovirt_host_info Invoked with pattern=name=ksmmi1r02ovirt36.kosmo.cloud auth={'token': 'eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICIyZzVfWUdWX08wSFJoWnlVeFNkdGl4d0liRWV6Wkp5NTgwN3BaXzUxelBvIn0.eyJleHAiOjE2ODg3OTY0MzAsImlhdCI6MTY4ODc3OTE1MCwianRpIjoiOTBlOWE5ZTAtMmExNS00MzNiLWIxOGQtMmUwNmI4MTQ5NGE2IiwiaXNzIjoiaHR0cHM6Ly9rc21lbmdpbmUwMS5rb3Ntby5jbG91ZC9vdmlydC1lbmdpbmUtYXV0aC9yZWFsbXMvb3ZpcnQtaW50ZXJuYWwiLCJhdWQiOiJhY2NvdW50Iiwic3ViIjoiYWRkMWMyYzYtYzJjMy00N2M4LWI1ODUtNGI2MTU2ZDAxYTE3IiwidHlwIjoiQmVhcmVyIiwiYXpwIjoib3ZpcnQtZW5naW5lLWludGVybmFsIiwic2Vzc2lvbl9zdGF0ZSI6IjNhMWUzZTU2LWIyZTUtNGMyYi05YTIxLThjZjE1YzY4NzlmNiIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cHM6Ly9rc21lbmdpbmUwMS5rb3Ntby5jbG91ZCJdLCJyZWFsbV9hY2Nlc3MiOnsicm9sZXMiOlsiZGVmYXVsdC1yb2xlcy1vdmlydC1pbnRlcm5hbCIsIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iXX0sInJlc291cmNlX2FjY2VzcyI6eyJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6Im92aXJ0LWV4dD10b2tlbjpwYXNzd29yZC1hY2Nlc3Mgb3ZpcnQtZXh0PXRva2VuLWluZm86cHVibGljLWF1dGh6LXNlYXJjaCBvdmlydC1hcHAtYXBpIG92aXJ0LWV4dD10b2tlbi1pbmZvOnZhbGlkYXRlIHByb2ZpbGUgZW1haWwgb3ZpcnQtZXh0PXRva2VuLWluZm86YXV0aHotc2VhcmNoIiwic2lkIjoiM2ExZTNlNTYtYjJlNS00YzJiLTlhMjEtOGNmMTVjNjg3OWY2IiwiZW1haWxfdmVyaWZpZWQiOmZhbHNlLCJncm91cHMiOlsiL292aXJ0LWFkbWluaXN0cmF0b3IiXSwicHJlZmVycmVkX3VzZXJuYW1lIjoiYWRtaW5Ab3ZpcnQiLCJlbWFpbCI6ImFkbWluQGxvY2FsaG9zdCJ9.o9PsulNw0urPphWITcB6Y3wpHQiiQ0v00su6XorITcvNElzkfHqyYfJd8W-kIfgElh6BNnCmYyIwtX7t3T4-PiLgDdipH1J9uzuDBXkmNBNcVmFimfUAqyC8aUITK56CqZ5TyRyHqhOicPciqGSY8R98hQ8I8y11w2RiIFT0rQYnRev75gjKoqUH29uNyeCAdTyKvPSGHNm1pLLrtPUmk-JCGmsYytNRCMHAPoNIlZP3k94PbQ9pI4jZ5O7kcRSgJik8tUDOVglcL4g0MoAJwracek2MUTvK8pDpRghI9hSQVLFtAXCyGRxfHHzTko4EbHBbFlz5s3pfs2kbF6TFmw', 'url': 'https://ksmengine01.kosmo.cloud/ovirt-engine/api', 'ca_file': None, 'insecure': True, 'timeout': 0, 'compress': True, 'kerberos': False, 'headers': None, 'hostname': None, 'username': None, 'password': None} fetch_nested=False nested_attributes=[] follow=[] all_content=False cluster_version=None cat /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20230707220613-2t8ze9.log 2023-07-07 22:19:11,816-0300 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up] 2023-07-07 22:39:39,882-0300 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'changed': False, 'ovirt_hosts': [{'href': '/ovirt-engine/api/hosts/d1bf8fb2-74f4-4954-8c34-66eb99ba2bf3', 'comment': '', 'id': 'd1bf8fb2-74f4-4954-8c34-66eb99ba2bf3', 'name': 'ksmmi1r02ovirt36.kosmo.cloud', 'address': 'ksmmi1r02ovirt36.kosmo.cloud', 'affinity_labels': [], 'auto_numa_status': 'unknown', 'certificate': {'organization': 'kosmo.cloud', 'subject': 'O=kosmo.cloud,CN=ksmmi1r02ovirt36.kosmo.cloud'}, 'cluster': {'href': '/ovirt-engine/api/clusters/d8784faf-8b77-45c8-9fa4-b9b4b0404d95', 'id': 'd8784faf-8b77-45c8-9fa4-b9b4b0404d95'}, 'cpu': {'speed': 0.0, 'topology': {}}, 'cpu_units': [], 'device_passthrough': {'enabled': False}, 'devices': [], 'external_network_provider_configurations': [], 'external_status': 'ok', 'hardware_information': {'supported_rng_sources': []}, 'hooks': [], 'katello_errata': [], 'kdump_status': 'unknown', 'ksm': {'enabled': False}, 'max_scheduling_memory': 0, 'memory': 0, 'network_attachments': [], 'nics': [], 'numa_nodes': [], 'numa_supported': False, 'os': {'custom_kernel_cmdline': ''}, 'ovn_configured': False, 'permissions': [], 'port': 54321, 'power_management': {'automatic_pm_enabled': True, 'enabled': False, 'kdump_detection': True, 'pm_proxies': []}, 'protocol': 'stomp', 'reinstallation_required': False, 'se_**FILTERED**': {}, 'spm': {'priority': 5, 'status': 'none'}, 'ssh': {'fingerprint': 'SHA256:Nr04m1g0UxbpqxwMBr93DLHz2m2wzR8+xFJhBVNovHY', 'port': 22, 'public_key': 'ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBE2EdJn0vJiJUagEK3w2G2nHmziJJasailwapaL06qWU2+BkPwkokSvyK07APhwyynnz6lw8J4y/kWv12D7/r+s='}, 'statistics': [], 'status': 'install_failed', 'storage_connection_extensions': [], 'summary': {'total': 0}, 'tags': [], 'transparent_huge_pages': {'enabled': False}, 'type': 'rhel', 'unmanaged_networks': [], 'update_available': False, 'vgpu_placement': 'consolidated'}], 'invocation': {'module_args': {'pattern': 'name=ksmmi1r02ovirt36.kosmo.cloud', 'fetch_nested': False, 'nested_attributes': [], 'follow': [], 'all_content': False, 'cluster_version': None}}, '_ansible_no_log': None, 'attempts': 120} 2023-07-07 22:39:39,983-0300 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 ignored: [localhost]: FAILED! => {"attempts": 120, "changed": false, "ovirt_hosts": [{"address": "ksmmi1r02ovirt36.kosmo.cloud", "affinity_labels": [], "auto_numa_status": "unknown", "certificate": {"organization": "kosmo.cloud", "subject": "O=kosmo.cloud,CN=ksmmi1r02ovirt36.kosmo.cloud"}, "cluster": {"href": "/ovirt-engine/api/clusters/d8784faf-8b77-45c8-9fa4-b9b4b0404d95", "id": "d8784faf-8b77-45c8-9fa4-b9b4b0404d95"}, "comment": "", "cpu": {"speed": 0.0, "topology": {}}, "cpu_units": [], "device_passthrough": {"enabled": false}, "devices": [], "external_network_provider_configurations": [], "external_status": "ok", "hardware_information": {"supported_rng_sources": []}, "hooks": [], "href": "/ovirt-engine/api/hosts/d1bf8fb2-74f4-4954-8c34-66eb99ba2bf3", "id": "d1bf8fb2-74f4-4954-8c34-66eb99ba2bf3", "katello_errata": [], "kdump_status": "unknown", "ksm": {"enabled": false}, "max_scheduling_memory": 0, "memory": 0, "name": "ksmmi1r02ovirt36.kosmo.cloud", "network_attachments": [], "nics": [], "numa_nodes": [], "numa_supported": false, "os": {"custom_kernel_cmdline": ""}, "ovn_configured": false, "permissions": [], "port": 54321, "power_management": {"automatic_pm_enabled": true, "enabled": false, "kdump_detection": true, "pm_proxies": []}, "protocol": "stomp", "reinstallation_required": false, "se_**FILTERED**": {}, "spm": {"priority": 5, "status": "none"}, "ssh": {"fingerprint": "SHA256:Nr04m1g0UxbpqxwMBr93DLHz2m2wzR8+xFJhBVNovHY", "port": 22, "public_key": "ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBE2EdJn0vJiJUagEK3w2G2nHmziJJasailwapaL06qWU2+BkPwkokSvyK07APhwyynnz6lw8J4y/kWv12D7/r+s="}, "statistics": [], "status": "install_failed", "storage_connection_extensions": [], "summary": {"total": 0}, "tags": [], "transparent_huge_pages": {"enabled": false}, "type": "rhel", "unmanaged_networks": [], "update_available": false, "vgpu_placement": "consolidated"}]} 2023-07-07 22:39:40,284-0300 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] 2023-07-07 22:39:40,685-0300 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'msg': 'Host is not up, please check logs, perhaps also on the engine machine', '_ansible_no_log': None, 'changed': False} 2023-07-07 22:39:40,786-0300 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"} Have a nice weekend! -- Att, Jorge Visentini +55 55 98432-9868

2 2

Q: New node install failed
by Andrei Verovski 03 Aug '23

03 Aug '23

Hi, I’m trying to install new node same way as I did several times before, with oVirt 4.5.2.4-1el8. HP Proliant with clean install of CentOS Stream 9 (in previous installs some time ago I used Stream 8). Add new node failed with this error (at the bottom of this e-mail), ovirt-host-deploy-ansible-20230803161025-node15.starlett.lv-827b7fc4-68b6-410f-aa90-f33884923ee8.log (from /var/log/ovirt-engine/host-deploy/) I can attach the whole log but it looks it is not necessary. My engine runs on dedicated PC and is NOT hosted engine. Thanks in advance for any help. Andrei ———————————————— [root@node15 ~]# dnf repolist --enabled repo id repo name appstream CentOS Stream 9 - AppStream baseos CentOS Stream 9 - BaseOS extras-common CentOS Stream 9 - Extras packages ---------------------------------- 2023-08-03 16:10:44 EEST - TASK [ovirt-host-deploy-vdsm : Install ovirt-hosted-engine-setup package] ****** 2023-08-03 16:10:47 EEST - { "uuid" : "b1ffdae5-0679-40c3-8609-1a5b976edc0e", "counter" : 99, "stdout" : "fatal: [node15.starlett.lv]: FAILED! => {\"changed\": false, \"failures\": [\"No package ovirt-hosted-engine-setup available.\"], \"msg\": \"Failed to install some of the specified packages\", \"rc\": 1, \"results\": []}", "start_line" : 87, "end_line" : 88, "runner_ident" : "281cf22b-29e3-4b4f-adc4-a47028b1ba59", "event" : "runner_on_failed", "pid" : 3199, "created" : "2023-08-03T13:10:45.632672", "parent_uuid" : "525400a7-0063-c9c3-eaa2-00000000022c", "event_data" : { "playbook" : "ovirt-host-deploy.yml", "playbook_uuid" : "dcb4654e-2e81-4090-a60e-b007a715eda6", "play" : "all", "play_uuid" : "525400a7-0063-c9c3-eaa2-000000000006", "play_pattern" : "all", "task" : "Install ovirt-hosted-engine-setup package", "task_uuid" : "525400a7-0063-c9c3-eaa2-00000000022c", "task_action" : "yum", "task_args" : "", "task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/packages.yml:6", "role" : "ovirt-host-deploy-vdsm", "host" : "node15.starlett.lv", "remote_addr" : "node15.starlett.lv", "res" : { "failures" : [ "No package ovirt-hosted-engine-setup available." ], "results" : [ ], "rc" : 1, "msg" : "Failed to install some of the specified packages", "invocation" : { "module_args" : { "name" : [ "ovirt-hosted-engine-setup" ], "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" : null, "disable_excludes" : null, "download_dir" : null, "list" : null, "releasever" : null } }, "_ansible_no_log" : false, "changed" : false }, "start" : "2023-08-03T13:10:43.563744", "end" : "2023-08-03T13:10:45.632205", "duration" : 2.068461, "ignore_errors" : null, "event_loop" : null, "uuid" : "b1ffdae5-0679-40c3-8609-1a5b976edc0e" } }

1 0

Ovirt engine after OS update doesn't start with WFLYEE0042: Failed t,o construct component instance
by Jirka Simon 29 Jul '23

29 Jul '23

Hello oVirt community. I just updated some OS packages (engine was up to date) and after restart engine doesn't start with error 500 and following error message in server.log I checked issue with postgres-jdbc (it has similar symptoms) and I downgraded it but it should be fixed now, but downgrade didn't help. here is part of server.log and list of all updated packages. thank you for any help. Jirka 023-07-29 12:01:51,382+02 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 42) MSC000001: Failed to start service jboss.deployment.subunit."engine.ear"."bll.jar".component. Backend.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: java.lang.IllegalStateException: WFLYEE0042: Failed t o construct component instance at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.base/java.lang.Thread.run(Thread.java:829) at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513) Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:170) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:141) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:127) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) ... 8 more Caused by: javax.ejb.EJBException: java.lang.RuntimeException: colliding os id 302 at node /os/centos_9x64/id at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:239) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:446) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:70) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld@24.0.1.Final//org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.singleton.StartupCountDownInterceptor.processInvocation(StartupCountDownInterceptor.java:25) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:168) ... 13 more Caused by: java.lang.RuntimeException: colliding os id 302 at node /os/centos_9x64/id at org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.OsRepositoryImpl.buildIdToUnameLookup(OsRepositoryImpl.java:105) at org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.OsRepositoryImpl.init(OsRepositoryImpl.java:66) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.Backend.initOsRepository(Backend.java:674) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.Backend.initialize(Backend.java:242) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.Backend.create(Backend.java:178) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:79) at org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doLifecycleInterception(Jsr299BindingsInterceptor.java:126) at org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:112) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) at org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld@24.0.1.Final//org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:53) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld@24.0.1.Final//org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ComponentInstantiatorInterceptor.processInvocation(ComponentInstantiatorInterceptor.java:74) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:111) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:232) ... 28 more 2023-07-29 12:01:51,393+02 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "engine.ear") ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.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: java.lang.RuntimeException: colliding os id 302 at node /os/centos_9x64/id Caused by: java.lang.RuntimeException: colliding os id 302 at node /os/centos_9x64/id"}} 2023-07-29 12:01:51,416+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : "ovirt-web-ui.war") 2023-07-29 12:01:51,417+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war") 2023-07-29 12:01:51,417+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war") 2023-07-29 12:01:51,417+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear") 2023-07-29 12:01:51,420+02 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.Backend.START: java.lang.IllegalStateException: WFLYEE0042: Failed to c onstruct component instance WFLYCTL0448: 2 additional services are down due to their dependencies being missing or failed 2023-07-29 12:01:51,462+02 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 2023-07-29 12:01:51,466+02 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 24.0.1.Final (WildFly Core 16.0.1.Final) started (with errors) in 14577ms - Started 1670 o f 1890 services (6 services failed or missing dependencies, 393 services are lazy, passive or on-demand) 2023-07-29 12:01:51,468+02 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:8706/management 2023-07-29 12:01:51,469+02 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:8706 list of all updated packages: dnf history info 21 Transaction ID : 21 Begin time : Sat 29 Jul 2023 10:59:14 AM CEST Begin rpmdb : 1077:5e724adb5bc93f2e2930cf25e895ccb36798d23c End time : Sat 29 Jul 2023 11:07:20 AM CEST (8 minutes) End rpmdb : 1087:60820a34eb4d036ba2c19d49841036fae4209af5 User : root <root> Return-Code : Success Releasever : 8 Command Line : update Comment : Packages Altered: Install apr-util-bdb-1.6.1-9.el8.x86_64 @appstream Install apr-util-openssl-1.6.1-9.el8.x86_64 @appstream Install kernel-4.18.0-500.el8.x86_64 @baseos Install kernel-core-4.18.0-500.el8.x86_64 @baseos Install kernel-modules-4.18.0-500.el8.x86_64 @baseos Install ongres-stringprep-1.1-2.el8.noarch @centos-ovirt45 Install python3.11-jmespath-0.9.0-11.5.el8.noarch @centos-ovirt45 Install python3.11-ovirt-engine-sdk4-4.6.2-1.el8.x86_64 @centos-ovirt45 Install python3.11-ovirt-imageio-client-2.5.0-1.el8.x86_64 @centos-ovirt45 Install python3.11-ovirt-imageio-common-2.5.0-1.el8.x86_64 @centos-ovirt45 Install python3.11-passlib-1.7.4-3.3.el8.noarch @centos-ovirt45 Install python3.11-pycurl-7.45.2-2.2.el8.x86_64 @centos-ovirt45 Install velocity-1.7-36.2.el8s.noarch @centos-ovirt45 Upgrade ceph-common-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded ceph-common-2:16.2.11-1.el8s.x86_64 @@System Upgrade libcephfs2-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded libcephfs2-2:16.2.11-1.el8s.x86_64 @@System Upgrade librados2-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded librados2-2:16.2.11-1.el8s.x86_64 @@System Upgrade libradosstriper1-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded libradosstriper1-2:16.2.11-1.el8s.x86_64 @@System Upgrade librbd1-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded librbd1-2:16.2.11-1.el8s.x86_64 @@System Upgrade librgw2-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded librgw2-2:16.2.11-1.el8s.x86_64 @@System Upgrade python3-ceph-argparse-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded python3-ceph-argparse-2:16.2.11-1.el8s.x86_64 @@System Upgrade python3-ceph-common-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded python3-ceph-common-2:16.2.11-1.el8s.x86_64 @@System Upgrade python3-cephfs-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded python3-cephfs-2:16.2.11-1.el8s.x86_64 @@System Upgrade python3-rados-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded python3-rados-2:16.2.11-1.el8s.x86_64 @@System Upgrade python3-rbd-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded python3-rbd-2:16.2.11-1.el8s.x86_64 @@System Upgrade python3-rgw-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded python3-rgw-2:16.2.11-1.el8s.x86_64 @@System Upgrade openvswitch2.15-2.15.0-136.el8s.x86_64 @centos-nfv-openvswitch Upgraded openvswitch2.15-2.15.0-135.el8s.x86_64 @@System Upgrade python3-openvswitch2.15-2.15.0-136.el8s.x86_64 @centos-nfv-openvswitch Upgraded python3-openvswitch2.15-2.15.0-135.el8s.x86_64 @@System Upgrade PackageKit-1.1.12-7.el8.x86_64 @appstream Upgraded PackageKit-1.1.12-6.el8.x86_64 @@System Upgrade PackageKit-glib-1.1.12-7.el8.x86_64 @appstream Upgraded PackageKit-glib-1.1.12-6.el8.x86_64 @@System Upgrade alsa-lib-1.2.9-1.el8.x86_64 @appstream Upgraded alsa-lib-1.2.8-2.el8.x86_64 @@System Upgrade ansible-core-2.15.0-1.el8.x86_64 @appstream Upgraded ansible-core-2.14.2-3.el8.x86_64 @@System Upgrade apr-util-1.6.1-9.el8.x86_64 @appstream Upgraded apr-util-1.6.1-6.el8.x86_64 @@System Upgrade cjose-0.6.1-3.module_el8+302+abe4241d.x86_64 @appstream Upgraded cjose-0.6.1-2.module_el8.4.0+674+2c6c7264.x86_64 @@System Upgrade cockpit-packagekit-295-1.el8.noarch @appstream Upgraded cockpit-packagekit-284-1.el8.noarch @@System Upgrade gdb-headless-8.2-20.el8.x86_64 @appstream Upgraded gdb-headless-8.2-19.el8.x86_64 @@System Upgrade git-2.39.3-1.el8.x86_64 @appstream Upgraded git-2.39.1-1.el8.x86_64 @@System Upgrade git-core-2.39.3-1.el8.x86_64 @appstream Upgraded git-core-2.39.1-1.el8.x86_64 @@System Upgrade git-core-doc-2.39.3-1.el8.noarch @appstream Upgraded git-core-doc-2.39.1-1.el8.noarch @@System Upgrade grafana-9.2.10-4.el8.x86_64 @appstream Upgraded grafana-7.5.15-4.el8.x86_64 @@System Upgrade grafana-pcp-5.1.1-1.el8.x86_64 @appstream Upgraded grafana-pcp-3.2.0-3.el8.x86_64 @@System Upgrade jq-1.6-7.el8.x86_64 @appstream Upgraded jq-1.6-6.el8.x86_64 @@System Upgrade libfastjson-0.99.9-2.el8.x86_64 @appstream Upgraded libfastjson-0.99.9-1.el8.x86_64 @@System Upgrade librsvg2-2.42.7-5.el8.x86_64 @appstream Upgraded librsvg2-2.42.7-4.el8.x86_64 @@System Upgrade libtiff-4.0.9-28.el8.x86_64 @appstream Upgraded libtiff-4.0.9-27.el8.x86_64 @@System Upgrade libwebp-1.0.0-9.el8.x86_64 @appstream Upgraded libwebp-1.0.0-5.el8.x86_64 @@System Upgrade mod_auth_openidc-2.4.9.4-5.module_el8+319+bd773fd7.x86_64 @appstream Upgraded mod_auth_openidc-2.4.9.4-1.module_el8.7.0+1136+d8f380b8.x86_64 @@System Upgrade nspr-4.35.0-1.el8.x86_64 @appstream Upgraded nspr-4.34.0-3.el8.x86_64 @@System Upgrade perl-Git-2.39.3-1.el8.noarch @appstream Upgraded perl-Git-2.39.1-1.el8.noarch @@System Upgrade platform-python-devel-3.6.8-52.el8.x86_64 @appstream Upgraded platform-python-devel-3.6.8-51.el8.x86_64 @@System Upgrade protobuf-c-1.3.0-8.el8.x86_64 @appstream Upgraded protobuf-c-1.3.0-6.el8.x86_64 @@System Upgrade python3-tkinter-3.6.8-52.el8.x86_64 @appstream Upgraded python3-tkinter-3.6.8-51.el8.x86_64 @@System Upgrade python3.11-3.11.4-1.el8.x86_64 @appstream Upgraded python3.11-3.11.2-2.el8.x86_64 @@System Upgrade python3.11-libs-3.11.4-1.el8.x86_64 @appstream Upgraded python3.11-libs-3.11.2-2.el8.x86_64 @@System Upgrade python3.11-tkinter-3.11.4-1.el8.x86_64 @appstream Upgraded python3.11-tkinter-3.11.2-2.el8.x86_64 @@System Upgrade python38-3.8.16-1.module_el8.8.0+1242+93d6d191.x86_64 @appstream Upgraded python38-3.8.13-1.module_el8.7.0+1177+19c53253.x86_64 @@System Upgrade python38-libs-3.8.16-1.module_el8.8.0+1242+93d6d191.x86_64 @appstream Upgraded python38-libs-3.8.13-1.module_el8.7.0+1177+19c53253.x86_64 @@System Upgrade python38-tkinter-3.8.16-1.module_el8.8.0+1242+93d6d191.x86_64 @appstream Upgraded python38-tkinter-3.8.13-1.module_el8.7.0+1177+19c53253.x86_64 @@System Upgrade qemu-guest-agent-15:6.2.0-35.module_el8+466+00f6f2b0.x86_64 @appstream Upgraded qemu-guest-agent-15:6.2.0-28.module_el8.8.0+1257+0c3374ae.x86_64 @@System Upgrade qemu-img-15:6.2.0-35.module_el8+466+00f6f2b0.x86_64 @appstream Upgraded qemu-img-15:6.2.0-28.module_el8.8.0+1257+0c3374ae.x86_64 @@System Upgrade rhel-system-roles-1.22.0-0.13.el8.noarch @appstream Upgraded rhel-system-roles-1.21.0-2.el8.noarch @@System Upgrade rsyslog-8.2102.0-15.el8.x86_64 @appstream Upgraded rsyslog-8.2102.0-13.el8.x86_64 @@System Upgrade rsyslog-elasticsearch-8.2102.0-15.el8.x86_64 @appstream Upgraded rsyslog-elasticsearch-8.2102.0-13.el8.x86_64 @@System Upgrade rsyslog-gnutls-8.2102.0-15.el8.x86_64 @appstream Upgraded rsyslog-gnutls-8.2102.0-13.el8.x86_64 @@System Upgrade rsyslog-mmjsonparse-8.2102.0-15.el8.x86_64 @appstream Upgraded rsyslog-mmjsonparse-8.2102.0-13.el8.x86_64 @@System Upgrade rsyslog-mmnormalize-8.2102.0-15.el8.x86_64 @appstream Upgraded rsyslog-mmnormalize-8.2102.0-13.el8.x86_64 @@System Upgrade texlive-base-7:20180414-29.el8.noarch @appstream Upgraded texlive-base-7:20180414-28.el8.noarch @@System Upgrade texlive-dvipng-7:20180414-29.el8.x86_64 @appstream Upgraded texlive-dvipng-7:20180414-28.el8.x86_64 @@System Upgrade texlive-kpathsea-7:20180414-29.el8.x86_64 @appstream Upgraded texlive-kpathsea-7:20180414-28.el8.x86_64 @@System Upgrade texlive-lib-7:20180414-29.el8.x86_64 @appstream Upgraded texlive-lib-7:20180414-28.el8.x86_64 @@System Upgrade texlive-tetex-7:20180414-29.el8.noarch @appstream Upgraded texlive-tetex-7:20180414-28.el8.noarch @@System Upgrade texlive-texlive.infra-7:20180414-29.el8.noarch @appstream Upgraded texlive-texlive.infra-7:20180414-28.el8.noarch @@System Upgrade tzdata-java-2023c-1.el8.noarch @appstream Upgraded tzdata-java-2022g-2.el8.noarch @@System Upgrade NetworkManager-1:1.40.16-8.el8.x86_64 @baseos Upgraded NetworkManager-1:1.40.16-2.el8.x86_64 @@System Upgrade NetworkManager-libnm-1:1.40.16-8.el8.x86_64 @baseos Upgraded NetworkManager-libnm-1:1.40.16-2.el8.x86_64 @@System Upgrade NetworkManager-team-1:1.40.16-8.el8.x86_64 @baseos Upgraded NetworkManager-team-1:1.40.16-2.el8.x86_64 @@System Upgrade NetworkManager-tui-1:1.40.16-8.el8.x86_64 @baseos Upgraded NetworkManager-tui-1:1.40.16-2.el8.x86_64 @@System Upgrade audit-3.0.7-5.el8.x86_64 @baseos Upgraded audit-3.0.7-4.el8.x86_64 @@System Upgrade audit-libs-3.0.7-5.el8.x86_64 @baseos Upgraded audit-libs-3.0.7-4.el8.x86_64 @@System Upgrade binutils-2.30-121.el8.x86_64 @baseos Upgraded binutils-2.30-119.el8.x86_64 @@System Upgrade c-ares-1.13.0-8.el8.x86_64 @baseos Upgraded c-ares-1.13.0-6.el8.x86_64 @@System Upgrade chkconfig-1.19.2-1.el8.x86_64 @baseos Upgraded chkconfig-1.19.1-1.el8.x86_64 @@System Upgrade cockpit-295-1.el8.x86_64 @baseos Upgraded cockpit-288.2-1.el8.x86_64 @@System Upgrade cockpit-bridge-295-1.el8.x86_64 @baseos Upgraded cockpit-bridge-288.2-1.el8.x86_64 @@System Upgrade cockpit-system-295-1.el8.noarch @baseos Upgraded cockpit-system-288.2-1.el8.noarch @@System Upgrade cockpit-ws-295-1.el8.x86_64 @baseos Upgraded cockpit-ws-288.2-1.el8.x86_64 @@System Upgrade curl-7.61.1-31.el8.x86_64 @baseos Upgraded curl-7.61.1-30.el8.x86_64 @@System Upgrade dbus-1:1.12.8-25.el8.x86_64 @baseos Upgraded dbus-1:1.12.8-24.el8.x86_64 @@System Upgrade dbus-common-1:1.12.8-25.el8.noarch @baseos Upgraded dbus-common-1:1.12.8-24.el8.noarch @@System Upgrade dbus-daemon-1:1.12.8-25.el8.x86_64 @baseos Upgraded dbus-daemon-1:1.12.8-24.el8.x86_64 @@System Upgrade dbus-libs-1:1.12.8-25.el8.x86_64 @baseos Upgraded dbus-libs-1:1.12.8-24.el8.x86_64 @@System Upgrade dbus-tools-1:1.12.8-25.el8.x86_64 @baseos Upgraded dbus-tools-1:1.12.8-24.el8.x86_64 @@System Upgrade dnf-4.7.0-18.el8.noarch @baseos Upgraded dnf-4.7.0-15.el8.noarch @@System Upgrade dnf-data-4.7.0-18.el8.noarch @baseos Upgraded dnf-data-4.7.0-15.el8.noarch @@System Upgrade dnf-plugins-core-4.0.21-23.el8.noarch @baseos Upgraded dnf-plugins-core-4.0.21-18.el8.noarch @@System Upgrade dracut-049-225.git20230614.el8.x86_64 @baseos Upgraded dracut-049-223.git20230119.el8.x86_64 @@System Upgrade dracut-config-generic-049-225.git20230614.el8.x86_64 @baseos Upgraded dracut-config-generic-049-223.git20230119.el8.x86_64 @@System Upgrade dracut-config-rescue-049-225.git20230614.el8.x86_64 @baseos Upgraded dracut-config-rescue-049-223.git20230119.el8.x86_64 @@System Upgrade dracut-network-049-225.git20230614.el8.x86_64 @baseos Upgraded dracut-network-049-223.git20230119.el8.x86_64 @@System Upgrade dracut-squash-049-225.git20230614.el8.x86_64 @baseos Upgraded dracut-squash-049-223.git20230119.el8.x86_64 @@System Upgrade elfutils-0.189-2.el8.x86_64 @baseos Upgraded elfutils-0.188-3.el8.x86_64 @@System Upgrade elfutils-debuginfod-client-0.189-2.el8.x86_64 @baseos Upgraded elfutils-debuginfod-client-0.188-3.el8.x86_64 @@System Upgrade elfutils-default-yama-scope-0.189-2.el8.noarch @baseos Upgraded elfutils-default-yama-scope-0.188-3.el8.noarch @@System Upgrade elfutils-libelf-0.189-2.el8.x86_64 @baseos Upgraded elfutils-libelf-0.188-3.el8.x86_64 @@System Upgrade elfutils-libs-0.189-2.el8.x86_64 @baseos Upgraded elfutils-libs-0.188-3.el8.x86_64 @@System Upgrade emacs-filesystem-1:26.1-11.el8.noarch @baseos Upgraded emacs-filesystem-1:26.1-9.el8.noarch @@System Upgrade file-5.33-25.el8.x86_64 @baseos Upgraded file-5.33-24.el8.x86_64 @@System Upgrade file-libs-5.33-25.el8.x86_64 @baseos Upgraded file-libs-5.33-24.el8.x86_64 @@System Upgrade fuse-libs-2.9.7-17.el8.x86_64 @baseos Upgraded fuse-libs-2.9.7-16.el8.x86_64 @@System Upgrade fuse3-libs-3.3.0-17.el8.x86_64 @baseos Upgraded fuse3-libs-3.3.0-16.el8.x86_64 @@System Upgrade glibc-2.28-228.el8.x86_64 @baseos Upgraded glibc-2.28-225.el8.x86_64 @@System Upgrade glibc-common-2.28-228.el8.x86_64 @baseos Upgraded glibc-common-2.28-225.el8.x86_64 @@System Upgrade glibc-gconv-extra-2.28-228.el8.x86_64 @baseos Upgraded glibc-gconv-extra-2.28-225.el8.x86_64 @@System Upgrade glibc-langpack-en-2.28-228.el8.x86_64 @baseos Upgraded glibc-langpack-en-2.28-225.el8.x86_64 @@System Upgrade gnutls-3.6.16-7.el8.x86_64 @baseos Upgraded gnutls-3.6.16-6.el8.x86_64 @@System Upgrade grubby-8.40-48.el8.x86_64 @baseos Upgraded grubby-8.40-47.el8.x86_64 @@System Upgrade hwdata-0.314-8.18.el8.noarch @baseos Upgraded hwdata-0.314-8.16.el8.noarch @@System Upgrade iproute-6.2.0-2.el8.x86_64 @baseos Upgraded iproute-5.18.0-1.el8.x86_64 @@System Upgrade iscsi-initiator-utils-6.2.1.4-8.git095f59c.el8.x86_64 @baseos Upgraded iscsi-initiator-utils-6.2.1.4-4.git095f59c.el8.x86_64 @@System Upgrade iscsi-initiator-utils-iscsiuio-6.2.1.4-8.git095f59c.el8.x86_64 @baseos Upgraded iscsi-initiator-utils-iscsiuio-6.2.1.4-4.git095f59c.el8.x86_64 @@System Upgrade kbd-2.0.4-11.el8.x86_64 @baseos Upgraded kbd-2.0.4-10.el8.x86_64 @@System Upgrade kbd-legacy-2.0.4-11.el8.noarch @baseos Upgraded kbd-legacy-2.0.4-10.el8.noarch @@System Upgrade kbd-misc-2.0.4-11.el8.noarch @baseos Upgraded kbd-misc-2.0.4-10.el8.noarch @@System Upgrade kernel-tools-4.18.0-500.el8.x86_64 @baseos Upgraded kernel-tools-4.18.0-481.el8.x86_64 @@System Upgrade kernel-tools-libs-4.18.0-500.el8.x86_64 @baseos Upgraded kernel-tools-libs-4.18.0-481.el8.x86_64 @@System Upgrade libblkid-2.32.1-42.el8.x86_64 @baseos Upgraded libblkid-2.32.1-41.el8.x86_64 @@System Upgrade libcurl-7.61.1-31.el8.x86_64 @baseos Upgraded libcurl-7.61.1-30.el8.x86_64 @@System Upgrade libdnf-0.63.0-16.el8.x86_64 @baseos Upgraded libdnf-0.63.0-13.el8.x86_64 @@System Upgrade libfdisk-2.32.1-42.el8.x86_64 @baseos Upgraded libfdisk-2.32.1-41.el8.x86_64 @@System Upgrade libgcc-8.5.0-20.el8.x86_64 @baseos Upgraded libgcc-8.5.0-18.el8.x86_64 @@System Upgrade libgfortran-8.5.0-20.el8.x86_64 @baseos Upgraded libgfortran-8.5.0-18.el8.x86_64 @@System Upgrade libgomp-8.5.0-20.el8.x86_64 @baseos Upgraded libgomp-8.5.0-18.el8.x86_64 @@System Upgrade libibverbs-46.0-1.el8.1.x86_64 @baseos Upgraded libibverbs-44.0-2.el8.1.x86_64 @@System Upgrade libldb-2.7.2-3.el8.x86_64 @baseos Upgraded libldb-2.6.1-1.el8.x86_64 @@System Upgrade libmount-2.32.1-42.el8.x86_64 @baseos Upgraded libmount-2.32.1-41.el8.x86_64 @@System Upgrade libnftnl-1.2.2-3.el8.x86_64 @baseos Upgraded libnftnl-1.1.5-5.el8.x86_64 @@System Upgrade libquadmath-8.5.0-20.el8.x86_64 @baseos Upgraded libquadmath-8.5.0-18.el8.x86_64 @@System Upgrade librabbitmq-0.9.0-4.el8.x86_64 @baseos Upgraded librabbitmq-0.9.0-3.el8.x86_64 @@System Upgrade librdmacm-46.0-1.el8.1.x86_64 @baseos Upgraded librdmacm-44.0-2.el8.1.x86_64 @@System Upgrade libsmartcols-2.32.1-42.el8.x86_64 @baseos Upgraded libsmartcols-2.32.1-41.el8.x86_64 @@System Upgrade libsolv-0.7.20-6.el8.x86_64 @baseos Upgraded libsolv-0.7.20-4.el8.x86_64 @@System Upgrade libsoup-2.62.3-4.el8.x86_64 @baseos Upgraded libsoup-2.62.3-3.el8.x86_64 @@System Upgrade libsss_autofs-2.9.1-1.el8.x86_64 @baseos Upgraded libsss_autofs-2.8.2-1.el8.x86_64 @@System Upgrade libsss_certmap-2.9.1-1.el8.x86_64 @baseos Upgraded libsss_certmap-2.8.2-1.el8.x86_64 @@System Upgrade libsss_idmap-2.9.1-1.el8.x86_64 @baseos Upgraded libsss_idmap-2.8.2-1.el8.x86_64 @@System Upgrade libsss_nss_idmap-2.9.1-1.el8.x86_64 @baseos Upgraded libsss_nss_idmap-2.8.2-1.el8.x86_64 @@System Upgrade libsss_sudo-2.9.1-1.el8.x86_64 @baseos Upgraded libsss_sudo-2.8.2-1.el8.x86_64 @@System Upgrade libstdc++-8.5.0-20.el8.x86_64 @baseos Upgraded libstdc++-8.5.0-18.el8.x86_64 @@System Upgrade libtalloc-2.4.0-3.el8.x86_64 @baseos Upgraded libtalloc-2.3.4-1.el8.x86_64 @@System Upgrade libtdb-1.4.8-3.el8.x86_64 @baseos Upgraded libtdb-1.4.7-1.el8.x86_64 @@System Upgrade libtevent-0.14.1-3.el8.x86_64 @baseos Upgraded libtevent-0.13.0-1.el8.x86_64 @@System Upgrade libuuid-2.32.1-42.el8.x86_64 @baseos Upgraded libuuid-2.32.1-41.el8.x86_64 @@System Upgrade linux-firmware-20230515-115.gitd1962891.el8.noarch @baseos Upgraded linux-firmware-20230217-113.git83f1d778.el8.noarch @@System Upgrade memstrack-0.2.5-2.el8.x86_64 @baseos Upgraded memstrack-0.2.4-2.el8.x86_64 @@System Upgrade microcode_ctl-4:20230214-2.el8.x86_64 @baseos Upgraded microcode_ctl-4:20220809-2.el8.x86_64 @@System Upgrade nvme-cli-1.16-9.el8.x86_64 @baseos Upgraded nvme-cli-1.16-7.el8.x86_64 @@System Upgrade nvmetcli-0.7-5.el8.noarch @baseos Upgraded nvmetcli-0.7-3.el8.noarch @@System Upgrade pam-1.3.1-27.el8.x86_64 @baseos Upgraded pam-1.3.1-25.el8.x86_64 @@System Upgrade platform-python-3.6.8-52.el8.x86_64 @baseos Upgraded platform-python-3.6.8-51.el8.x86_64 @@System Upgrade python-rpm-macros-3-45.el8.noarch @baseos Upgraded python-rpm-macros-3-44.el8.noarch @@System Upgrade python-srpm-macros-3-45.el8.noarch @baseos Upgraded python-srpm-macros-3-44.el8.noarch @@System Upgrade python3-audit-3.0.7-5.el8.x86_64 @baseos Upgraded python3-audit-3.0.7-4.el8.x86_64 @@System Upgrade python3-cryptography-3.2.1-6.el8.x86_64 @baseos Upgraded python3-cryptography-3.2.1-5.el8.x86_64 @@System Upgrade python3-dnf-4.7.0-18.el8.noarch @baseos Upgraded python3-dnf-4.7.0-15.el8.noarch @@System Upgrade python3-dnf-plugin-versionlock-4.0.21-23.el8.noarch @baseos Upgraded python3-dnf-plugin-versionlock-4.0.21-18.el8.noarch @@System Upgrade python3-dnf-plugins-core-4.0.21-23.el8.noarch @baseos Upgraded python3-dnf-plugins-core-4.0.21-18.el8.noarch @@System Upgrade python3-hawkey-0.63.0-16.el8.x86_64 @baseos Upgraded python3-hawkey-0.63.0-13.el8.x86_64 @@System Upgrade python3-libdnf-0.63.0-16.el8.x86_64 @baseos Upgraded python3-libdnf-0.63.0-13.el8.x86_64 @@System Upgrade python3-libs-3.6.8-52.el8.x86_64 @baseos Upgraded python3-libs-3.6.8-51.el8.x86_64 @@System Upgrade python3-magic-5.33-25.el8.noarch @baseos Upgraded python3-magic-5.33-24.el8.noarch @@System Upgrade python3-perf-4.18.0-500.el8.x86_64 @baseos Upgraded python3-perf-4.18.0-481.el8.x86_64 @@System Upgrade python3-rpm-macros-3-45.el8.noarch @baseos Upgraded python3-rpm-macros-3-44.el8.noarch @@System Upgrade python3-syspurpose-1.28.38-1.el8.x86_64 @baseos Upgraded python3-syspurpose-1.28.35-1.el8.x86_64 @@System Upgrade selinux-policy-3.14.3-123.el8.noarch @baseos Upgraded selinux-policy-3.14.3-117.el8.noarch @@System Upgrade selinux-policy-targeted-3.14.3-123.el8.noarch @baseos Upgraded selinux-policy-targeted-3.14.3-117.el8.noarch @@System Upgrade shadow-utils-2:4.6-18.el8.x86_64 @baseos Upgraded shadow-utils-2:4.6-17.el8.x86_64 @@System Upgrade sos-4.5.4-1.el8.noarch @baseos Upgraded sos-4.5.0-1.el8.noarch @@System Upgrade sqlite-3.26.0-18.el8.x86_64 @baseos Upgraded sqlite-3.26.0-17.el8.x86_64 @@System Upgrade sqlite-libs-3.26.0-18.el8.x86_64 @baseos Upgraded sqlite-libs-3.26.0-17.el8.x86_64 @@System Upgrade sssd-client-2.9.1-1.el8.x86_64 @baseos Upgraded sssd-client-2.8.2-1.el8.x86_64 @@System Upgrade sssd-common-2.9.1-1.el8.x86_64 @baseos Upgraded sssd-common-2.8.2-1.el8.x86_64 @@System Upgrade sssd-kcm-2.9.1-1.el8.x86_64 @baseos Upgraded sssd-kcm-2.8.2-1.el8.x86_64 @@System Upgrade sssd-nfs-idmap-2.9.1-1.el8.x86_64 @baseos Upgraded sssd-nfs-idmap-2.8.2-1.el8.x86_64 @@System Upgrade systemd-239-76.el8.x86_64 @baseos Upgraded systemd-239-73.el8.x86_64 @@System Upgrade systemd-libs-239-76.el8.x86_64 @baseos Upgraded systemd-libs-239-73.el8.x86_64 @@System Upgrade systemd-pam-239-76.el8.x86_64 @baseos Upgraded systemd-pam-239-73.el8.x86_64 @@System Upgrade systemd-udev-239-76.el8.x86_64 @baseos Upgraded systemd-udev-239-73.el8.x86_64 @@System Upgrade tmux-2.7-3.el8.x86_64 @baseos Upgraded tmux-2.7-1.el8.x86_64 @@System Upgrade tzdata-2023c-1.el8.noarch @baseos Upgraded tzdata-2022g-2.el8.noarch @@System Upgrade util-linux-2.32.1-42.el8.x86_64 @baseos Upgraded util-linux-2.32.1-41.el8.x86_64 @@System Upgrade which-2.21-20.el8.x86_64 @baseos Upgraded which-2.21-18.el8.x86_64 @@System Upgrade xfsprogs-5.0.0-12.el8.x86_64 @baseos Upgraded xfsprogs-5.0.0-10.el8.x86_64 @@System Upgrade yum-4.7.0-18.el8.noarch @baseos Upgraded yum-4.7.0-15.el8.noarch @@System Upgrade yum-utils-4.0.21-23.el8.noarch @baseos Upgraded yum-utils-4.0.21-18.el8.noarch @@System Upgrade zlib-1.2.11-25.el8.x86_64 @baseos Upgraded zlib-1.2.11-21.el8.x86_64 @@System Upgrade centos-release-ovirt45-8.9-1.el8s.noarch @extras-common Upgraded centos-release-ovirt45-8.7-3.el8s.noarch @@System Upgrade ongres-scram-2.1-3.el8.noarch @centos-ovirt45 Upgraded ongres-scram-1.0.0~beta.2-5.el8.noarch @@System Upgrade ongres-scram-client-2.1-3.el8.noarch @centos-ovirt45 Upgraded ongres-scram-client-1.0.0~beta.2-5.el8.noarch @@System Upgrade ovirt-ansible-collection-3.1.2-1.el8.noarch @centos-ovirt45 Upgraded ovirt-ansible-collection-3.0.0-1.el8.noarch @@System Upgrade ovirt-dependencies-4.5.3-1.el8.noarch @centos-ovirt45 Upgraded ovirt-dependencies-4.5.2-1.el8.noarch @@System Upgrade ovirt-imageio-client-2.5.0-1.el8.x86_64 @centos-ovirt45 Upgraded ovirt-imageio-client-2.4.7-1.el8.x86_64 @@System Upgrade ovirt-imageio-common-2.5.0-1.el8.x86_64 @centos-ovirt45 Upgraded ovirt-imageio-common-2.4.7-1.el8.x86_64 @@System Upgrade ovirt-imageio-daemon-2.5.0-1.el8.x86_64 @centos-ovirt45 Upgraded ovirt-imageio-daemon-2.4.7-1.el8.x86_64 @@System Upgrade postgresql-jdbc-42.2.27-1.el8.noarch @centos-ovirt45 Upgraded postgresql-jdbc-42.2.14-2.el8.noarch @@System Upgrade python3-jmespath-0.9.0-11.5.el8.noarch @centos-ovirt45 Upgraded python3-jmespath-0.9.0-11.2.el8.noarch @@System Upgrade python3-netaddr-0.8.0-12.3.el8.noarch @centos-ovirt45 Upgraded python3-netaddr-0.7.19-8.1.2.el8.noarch @@System Upgrade python3-ovirt-engine-sdk4-4.6.2-1.el8.x86_64 @centos-ovirt45 Upgraded python3-ovirt-engine-sdk4-4.6.0-1.el8.x86_64 @@System Upgrade python3-passlib-1.7.4-3.3.el8.noarch @centos-ovirt45 Upgraded python3-passlib-1.7.4-1.el8.noarch @@System Upgrade python3-pycurl-7.45.2-2.2.el8.x86_64 @centos-ovirt45 Upgraded python3-pycurl-7.43.0.2-4.2.el8.x86_64 @@System Upgrade python3-cinder-common-1:20.3.0-1.el8.noarch @ovirt-45-centos-stream-openstack-yoga Upgraded python3-cinder-common-1:20.1.0-1.el8.noarch @@System Upgrade python3-os-brick-5.2.3-1.el8.noarch @ovirt-45-centos-stream-openstack-yoga Upgraded python3-os-brick-5.2.2-1.el8.noarch @@System Upgrade python3-oslo-messaging-12.13.1-1.el8.noarch @ovirt-45-centos-stream-openstack-yoga Upgraded python3-oslo-messaging-12.13.0-1.el8.noarch @@System Reason ChangeGConf2-3.2.6-22.el8.x86_64 @appstream Removed kernel-4.18.0-383.el8.x86_64 @@System Removed kernel-core-4.18.0-383.el8.x86_64 @@System Removed kernel-modules-4.18.0-383.el8.x86_64 @@System

1 1

CPU Compatibility with 4.5.4-1.el8 (4.7)
by mark.williams＠nist.gov 26 Jul '23

26 Jul '23

Having issue adding oVirt host using AlmaLinux 8/9 with systems using the sandybridge CPU Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz. Error give CPU not compatible with Ovirt "compatibility type 4.7". Works with creating another Cluster at "compatibility type 4.3", but not 4.7. These host were re-purposed from RHV 4.3 Cluster. Any thoughts?

1 0

Connection to ovirt-imageio has failed
by masth.ganesh＠gmail.com 26 Jul '23

26 Jul '23

I am trying to upload an ISO onto the OLVM and I get the "connection to ovirt-imageio has failed" message when I test the connection. I have uploaded the certificates onto the web browser but for some reason I am unable to test the connection successfully. I have tried it on other browsers like Edge and Firefox as well.

1 0

Problema VM with Disk blocked creating snapshot wrong
by José Pascual 25 Jul '23

25 Jul '23

Hi, I have a Virtual Machine Bloqued by the disk and i cant delete for restoreing de VM and i cant do anything. This is a error with the snapshot and never ends (the virtual machine now is shutdown). What can i do for deleteting de virtual machine from my engine and the disk? -- Saludos, José Pascual Gallud Martínez Nombre | Dpto. Ingeniería <http://telfy.com/>

1 0

Ovirt_Provider_Citrix-Xen
by rj.indramaya＠gmail.com 23 Jul '23

23 Jul '23

Hi All, First of all apology If i'm doing it wrong way. I could not find any solution so I hoped I'll get some answers here. In my Organization I started exploring the Ovirt-Engine, While I have created multiple VMs and all working fine I started facing one issue as in my organization we had Citrix Xen server which is out of date so I started working on migrating them directly to Ovirt-enigne. so I tried to add my Xen-server as a provider but its failing to load or connect with the Citrix-Xen. Let me know how should I move forward, Thanks in advance, people are amazing.

3 2

Obtain SSO token using username/password credentials] fails Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials.
by antonio.riggio＠mail.com 22 Jul '23

22 Jul '23

can anyone tell how I can fix this I have not been able to install ovirt. Im using the same password when I login to ovirt too. thanks INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ ERROR ] ovirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials. [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": false, "msg": "Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials."} [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch logs from the engine VM] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Find the local appliance image] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Copy engine logs] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Change ownership of copied engine logs] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Remove temporary entry in /etc/hosts for the local VM] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Destroy local storage-pool localvmxfo24vb0] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Undefine local storage-pool localvmxfo24vb0] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Destroy local storage-pool 9df88328-fb97-4230-a679-a9ab4cc59562] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Undefine local storage-pool 9df88328-fb97-4230-a679-a9ab4cc59562] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "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"}

1 0

oVirt Host EL9 with UEFI Secure Boot
by Jorge Visentini 21 Jul '23

21 Jul '23

Hi there! Is this information still valid? To use Enterprise Linux 9 on virtualization hosts, the UEFI Secure Boot option must be disabled due to *Bug 2081648 - dmidecode module fails to decode DMI data <https://bugzilla.redhat.com/show_bug.cgi?id=2081648>*. I read that it was fixed in *python-dmidecode-3.12.3-1.el9* but we still use *python-3.11*. Is this bug only for hosted-engine or for standalone too? BR. -- Att, Jorge Visentini +55 55 98432-9868

2 4

Processors compatibility matrix oVirt
by Jorge Visentini 21 Jul '23

21 Jul '23

Do you have any documentation or compatibility matrix between oVirt and processors? How can I know if a processor is compatible? I ask because in the *lscpu* command I see 2 sockets, but in the *engine* I only see 1 socket. BR. -- Att, Jorge Visentini +55 55 98432-9868

5 9

ovirt with rocky linux kvm
by cynthiaberbery＠outlook.com 20 Jul '23

20 Jul '23

Hello, after installing multiple machines as rocky linux, Ovirt was chosen to be used to manage this infra. But adding these machines as "hosts" on ovirt always give: Error while executing action: Cannot add Host. Connecting to host via SSH has failed, verify that the host is reachable (IP address, routable address etc.) You may refer to the engine.log file for further details. Is rocky kvm supported on ovirt 4.3.10.4-1.el7? Do you have any contact with a supporting company/team for ovirt to check their support plan?

4 3

How to re-enroll a host with an active workload whose certificate expired
by David Johnson 20 Jul '23

20 Jul '23

Good evening all, I have a three host installation with a separate dedicated bare metal system for the engine, running Ovirt 4.5.2.4-1.el8. This afternoon, the engine lost communication with one of the hosts. The engine log says the certificate is expired. The official solution appears to be to put the host into maintenance mode then re-enroll it. Unfortunately, because the certificate is expired, the engine cannot switch to maintenance mode or control the VM's to shut them down. Error while executing action: Cannot switch Host to Maintenance mode. Host still has running VMs on it and is in Non Responsive state. See log excerpt below What is the correct way to update/reinstate a certificate in a running cluster when the engine does not acknowledge the host is operational due to an expired certificate? Thank you. *David Johnson* Log excerpt: 2023-07-20 16:27:46,904-05 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] Connecting to /192.168.2.18 2023-07-20 16:27:46,904-05 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] *Connected to /192.168.2.18:54321 <http://192.168.2.18:54321>* 2023-07-20 16:27:46,912-05 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] *Unable to process messages Received fatal alert: certificate_expired* 2023-07-20 16:27:46,914-05 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-52) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: Received fatal alert: certificate_expired 2023-07-20 16:27:47,356-05 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-34) [] Unable to RefreshCapabilities: ClientConnectionException: SSL session is invalid 2023-07-20 16:27:47,356-05 WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-34) [] Trying to release exclusive lock which does not exist, lock key: 'f69d35b2-7666-4ac6-8645-2f119cf2ce1cVDS_INIT' 2023-07-20 16:27:47,356-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-34) [] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand' return value 'org.ovirt.engine.core.vdsbroker.vdsbroker.VDSInfoReturn@7d03f4f0' 2023-07-20 16:27:47,356-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-34) [] HostName = ovirt-host-03 2023-07-20 16:27:47,356-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-34) [] Command 'GetCapabilitiesAsyncVDSCommand(HostName = ovirt-host-03, VdsIdAndVdsVDSCommandParametersBase:{hostId='f69d35b2-7666-4ac6-8645-2f119cf2ce1c', vds='Host[ovirt-host-03,f69d35b2-7666-4ac6-8645-2f119cf2ce1c]'})' execution failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: *SSL session is invalid*

1 0

First time user/setup
by jmred88＠gmail.com 20 Jul '23

20 Jul '23

Could someone explain to me the proper documentation I should be using for a standalone setup? I have one host with local storage/resources and would like that to both host and manage my VMs but I keep getting into the weeds with which documentation to follow.

2 1

ovirt node 4.5 is not working on esxi8 on my lab
by poper＠windowslive.com 20 Jul '23

20 Jul '23

Hello there, May I ask why I have installed ovirt node 4.5 latest from iso on my esxi8 after I logged in to the web interface to manage this host I cannot find menu virtualization but when I tested on 4.4.6 everything is work. Do you have any idea? Thanks.

2 1

Commit or release history
by Jorge Visentini 20 Jul '23

20 Jul '23

Hi. I'm following the release of the 4.5.5 isos and I see that new isos are coming out almost every day. Is there any place where I can keep track of the changes that were made from one iso to another? Is it open for us to follow? Cheers! -- Att, Jorge Visentini +55 55 98432-9868

2 2

python sdk4 ovirt 4.5.5.0 master
by Jorge Visentini 19 Jul '23

19 Jul '23

Hi. I am testing oVirt 4.5.5-0.master.20230712143502.git07e865d650.el8. I missed the python scripts to download and upload discs and images... Will it still be possible to use them or should I consider using Ansible? BR. -- Att, Jorge Visentini +55 55 98432-9868

2 2

oVirt 4.4. Engine Deployment: Problems with Gluster Storage Domain
by Thyen, Niko 18 Jul '23

18 Jul '23

Hi everybody! I am having a hard time getting oVirt 4.4 to work. We want to update our 4.3 Cluster and i am trying to set up a fresh 4.4 Cluster (and restore the backup later on) in order to update to 4.5. It fails at the end of the engine deloyment, when the Gluster Storage Domain should be added. I installed oVirt Node 4.4.10 on an old PC and made the following modifications to the engine deployment process: - altered defaults in /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/defaults/main.yml: - "he_pause_before_engine_setup: true" (in this pause before engine setup, i ssh into the engine and exclude the package postgresql-jdbc from update, which otherwise breaks the deployment [1]) - "he_remove_appliance_rpm: false" (to avoid the large download every single try, i tried a lot) - "he_force_ip4: true" (to avoid problems with IPv6, see below) - in /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/fetch_host_ip.yml i added after "- name: Get host address resolution:" the following lines (to avoid a problem with an "invalid" IPv6-Adress, which otherwise breaks the deployment [2]): - name: Get host IP addresses ansible.builtin.command: hostname -I register: hostname_addresses_output changed_when: true Most times, i started deployment via shell but tried via webinterface of the node as well. It fails at the task "Add glusterfs storage domain" with the following message: "[ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Failed to fetch Gluster Volume List]". HTTP response code is 400." (See also [3]) When the setup asks for storage, i tried different answers (gluster.local:/volume, gluster.local:/path/to/brick/volume, 192.168.8.51:/volume ...), no mount options. I added firewall rules for glusterfs at node and engine. Even tried disabling the firewall. No firewall on the gluster servers running. On the Node, i also tested setting SELinux to permissive. Recorded the traffic at different interfaces ("ovirtmgmt" and "virbr0" on the node and "eth0" on the engine) and i can see the node and the gluster server talking: Node gets the volume with options (which are, btw, compliant to the docs, "storage.owner-gid: 36" "storage.owner-uid: 36" etc) but thats it, no further packets to mount the volume. I noticed some ARP packets as well, the node asks the IP from the engine (the configured static IP, which is not yet active). And the engine sends a dns request for the gluster server to the node (via interface virbr0), but doesnt connect to the gluster server. At least, thats what i can see, most of the traffic is TLS, which i couldnt decrypt yet. I appreciate any hint where to find the right keys. Anyway, i can ssh from the engine to the gluster server and mount the gluster volume manually on the node (mount -t glusterfs gluster.local:/volume /local/path), so there seem no connectivity issues. Since the engine deployment log is around 30MB i attached a log summary with findings i found relevant. I'll provide more logs if needed. I really wanna put this huge timesink to an end. Can anyone help me or point me in the right direction? Many thanks in advance :) Regards, Niko [1] This was the error message i got: "[ ERROR ] fatal: [localhost -> 192.168.222.195]: FAILED! => {"attempts": 30, "changed": false, "connection": "close", "content": "Error500 - Internal Server Error", "content_encoding": "identity", "content_length": "86", "content_type": "text/html; charset=UTF-8", "date": "Wed, 17 May 2023 22:42:27 GMT", "elapsed": 0, "msg": "Status code was 500 and not [200]: HTTP Error 500: Internal Server Error", "redirected": false, "server": "Apache/2.4.37 (centos) OpenSSL/1.1.1k mod_auth_gssapi/1.6.1 mod_wsgi/4.6.4 Python/3.6", "status": 500, "url": "http://localhost/ovirt-engine/services/health"}" [2] This was the error message i got: "VDSM ovirt.martinwi.local command HostSetupNetworksVDS failed: Internal JSON-RPC error: {'reason': "Invalid IP address: 'fe80::ea3f:67ff:fe7f:a029%ovirtmgmt' does not appear to be an IPv4 or IPv6 address"}" [3] /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20230718140628-rryscj.log: 2023-07-18 16:32:35,877+0200 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:106 {'msg': 'Fault reason is "Operation Failed". Fault detail is "[Failed to fetch Gluster Volume List]". HTTP response code is 400.', 'exception': 'Traceback (most recent call last):\n File "/tmp/ansible_ovirt_storage_domain_payload_b4ofbzxa/ansible_ovirt_storage_domain_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_domain.py", line 804, in main\n File "/tmp/ansible_ovirt_storage_domain_payload_b4ofbzxa/ansible_ovirt_storage_domain_payload.zip/ansible_collections/ovirt/ovirt/plugins/module_utils/ovirt.py", line 674, in create\n **kwargs\n File "/usr/lib64/python3.6/site-packages/ovirtsdk4/services.py", line 26258, in add\n return self._internal_add(storage_domain, headers, query, wait)\n File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 232, in _internal_add\n return future.wait() if wait else future\n File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 229, in callback\n self._check_fault(response)\n File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\novirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Failed to fetch Gluster Volume List]". HTTP response code is 400.\n', 'invocation': {'module_args': {'state': 'unattached', 'name': 'hosted_storage', 'host': 'ovirt.martinwi.local', 'data_center': 'Default', 'wait': True, 'glusterfs': {'address': 'gluster1.martinwi.local', 'path': '/gv3', 'mount_options': ''}, 'timeout': 180, 'poll_interval': 3, 'fetch_nested': False, 'nested_attributes': [], 'domain_function': 'data', 'id': None, 'description': None, 'comment': None, 'localfs': None, 'nfs': None, 'iscsi': None, 'managed_block_storage': None, 'posixfs': None, 'fcp': None, 'wipe_after_delete': None, 'backup': None, 'critical_space_action_blocker': None, 'warning_low_space': None, 'destroy': None, 'format': None, 'discard_after_delete': None}}, '_ansible_no_log': False, 'changed': False}

1 0

engine-setup failing on 4.3.2 -> 4.3.3 fails during Engine schema refresh fail
by Edward Berger 18 Jul '23

18 Jul '23

I was trying to upgrade a hyperconverged oVirt hosted engine and failed in the engine-setup command with these error and warnings. ... [ INFO ] Creating/refreshing Engine database schema [ ERROR ] schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0830_add_foreign_key_to_image_transfers.sql [ ERROR ] Failed to execute stage 'Misc configuration': Engine schema refresh failed ... [ INFO ] Yum Verify: 16/16: ovirt-engine-tools.noarch 0:4.3.3.5-1.el7 - e [WARNING] Rollback of DWH database postponed to Stage "Clean up" [ INFO ] Rolling back database schema ... [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed Attaching engine-setup logfile.

4 6

Local physical disk directly on the VM
by Jorge Visentini 17 Jul '23

17 Jul '23

Hi. Is it possible to deliver a physical disk straight to the VM? What's my idea... I have a local disk on the server and I want to deliver it directly to a VM, is it possible? For example, take the hypervisor disk /dev/disk/by-id/ata-INTEL_SSDSC2KB480G8_PHYF117203AA480BGN and hand it to the VM. BR. -- Att, Jorge Visentini +55 55 98432-9868

1 0

Re: Future of the oVirt CSI Driver
by Mike Rochefort 11 Jul '23

11 Jul '23

On 7/11/23 2:58 AM, Sandro Bonazzola wrote: > I think that if OKD is dropping the oVirt CSI Driver this also will mean > nobody will be actively developing it anymore. I asked about this on the Kubernetes Slack workspace and Vadim mentioned that in order for the OKD project to continue providing oVirt support, someone with oVirt knowledge and operator development would need to step up. It would also require forking the installer and a few other projects, which is something the OKD team spent a lot of effort to not have to do anymore during the 4.x series. https://github.com/openshift/installer Looking at the OpenShift Installer git, so far what's changed is an admin can no longer specify oVirt as a deployment target. According to Jira, there will be a second phase of the deprecation where the actual provisioning pieces (e.g. Terraform) will be removed, but that probably won't be for 4.14. https://issues.redhat.com//browse/OCPBUGS-14818 But not having anyone develop the CSI driver means it will likely end up with bit rot. With OpenShift 4.14 the oVirt platform becomes less attractive to use, though IPI/UPI installations should be possible. A different storage backend would probably be recommended, however. -- Mike Rochefort

2 1

Simple question - oVirt el8 with UEFI or el9 without UEFI?
by Jorge Visentini 11 Jul '23

11 Jul '23

We are in the process of migrating from version 4.4 to 4.5 and we are in doubt whether we use version el8 with UEFI or el9 without UEFI? What do you recommend? BR. -- Att, Jorge Visentini +55 55 98432-9868

1 0

Future of the oVirt CSI Driver
by Michael Rochefort 11 Jul '23

11 Jul '23

Starting with OpenShift / OKD 4.14, the oVirt CSI driver will no longer be delivered as part of the platform and the oVirt provisioning artifacts will not be included in the installer. Does this at all impact the development and maintenance plans for the driver itself? Original archived driver: https://github.com/oVirt/csi-driver OpenShift forked driver: https://github.com/openshift/ovirt-csi-driver Cheers, Mike

2 1

oVirt Self-Hosted Deploy in lopping during search available subnet
by Lucy Silvestre 11 Jul '23

11 Jul '23

Hi, I have been stuck for weeks in this problem during self-hosted deployment. Does someone have suggestions to resolve this? Error: The Deploy loops in this part until the Deployment Fail: [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get ip route] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if can't find an available subnet] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set new IPv4 subnet prefix] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Search again with another prefix] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Define 3rd chunk] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set 3rd chunk] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get ip route] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if can't find an available subnet] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set new IPv4 subnet prefix] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Search again with another prefix] [ INFO ] ok: [localhost] Details: OS: Oracle Linux 8.8 (minimum installation) and updated oVirt 4.4 ovirt-hosted-engine-setup and ovirt-engine-appliance installed Network device used in the Host machine: eno1 - 192.168.10.x and I also tried with Bond. I made a reservation on DHCP for these IPs used during the installation. I tried by terminal and Cockpit, and it is the same issue. I tried with the command: hosted-engine --deploy --4 I tried with DHCP and Static IP I will appreciate every help. Thank you.

2 1

ACTION_TYPE_FAILED_DISK_IS_BEING_TRANSFERRED
by eshwayri＠gmail.com 08 Jul '23

08 Jul '23

System unexpectedly lost power. Now when I try to start one of the VMs I get: "ACTION_TYPE_FAILED_DISK_IS_BEING_TRANSFERRED". This may be due to a failed backup earlier in the week. There are no active tasks against this VM or its disk at this time. The disk shows OK in the storage view. Any ideas?

1 3

Suggestion to switch to nightly
by Sandro Bonazzola 07 Jul '23

07 Jul '23

Hi, As you probably noticed there were no regular releases after oVirt 4.5.4 <https://ovirt.org/release/4.5.4/> in December 2022. Despite the calls to action to the community and to the companies involved with oVirt, there have been no uptake of the leading of the oVirt project yet. The developers at Red Hat still dedicating time to the project are now facing the fact they lack the time to do formal releases despite they keep fixing platform regressions like the recent ones due to the new ansible changes. That makes a nightly snapshot setup a more stable environment than oVirt 4.5.4. For this reason, we would like to suggest the user community to enable nightly repositories for oVirt by following the procedure at: https://www.ovirt.org/develop/dev-process/install-nightly-snapshot.html This will ensure that the latest fixes for the platform regressions will be promptly available. Regards, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle Operating System Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

5 9

GPU Passthrough issues with oVirt 4.5
by Vinícius Ferrão 07 Jul '23

07 Jul '23

Hello, does anyone is having issues with device passthrough on oVirt 4.5? I can passthrough the devices without issue to a given VM, but inside the VM it fails to recognize all the devices. In my case I’ve added 4x GPUs to a VM, but only one show up, and there’s the following errors inside the VM: [ 23.006655] nvidia 0000:0a:00.0: enabling device (0000 -> 0002) [ 23.008026] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR1 is 0M @ 0x0 (PCI:0000:0a:00.0) [ 23.008035] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR2 is 0M @ 0x0 (PCI:0000:0a:00.0) [ 23.008040] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR3 is 0M @ 0x0 (PCI:0000:0a:00.0) [ 23.008045] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR4 is 0M @ 0x0 (PCI:0000:0a:00.0) [ 23.008049] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR5 is 0M @ 0x0 (PCI:0000:0a:00.0) [ 23.012339] NVRM: The NVIDIA GPU 0000:0a:00.0 (PCI ID: 10de:1db1) NVRM: installed in this system is not supported by the NVRM: NVIDIA 535.54.03 driver release. NVRM: Please see 'Appendix A - Supported NVIDIA GPU Products' NVRM: in this release's README, available on the operating system NVRM: specific graphics driver download page at www.nvidia.com. [ 23.016175] nvidia: probe of 0000:0a:00.0 failed with error -1 [ 23.016838] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR0 is 0M @ 0x0 (PCI:0000:0b:00.0) [ 23.016842] nvidia: probe of 0000:0b:00.0 failed with error -1 [ 23.017211] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: NVRM: BAR0 is 0M @ 0x0 (PCI:0000:0c:00.0) [ 23.017215] nvidia: probe of 0000:0c:00.0 failed with error -1 [ 23.017248] NVRM: The NVIDIA probe routine failed for 3 device(s). [ 23.214409] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 535.54.03 Tue Jun 6 22:20:39 UTC 2023 [ 23.485704] [drm] [nvidia-drm] [GPU ID 0x00000900] Loading driver [ 23.485708] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:09:00.0 on minor 1 On the host this shows up on dmesg, but seems right: [ 709.572845] vfio-pci 0000:1a:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258 [ 709.572877] vfio-pci 0000:1a:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 [ 709.572883] vfio-pci 0000:1a:00.0: vfio_ecap_init: hiding ecap 0x23@0xac0 [ 710.660813] vfio-pci 0000:1d:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258 [ 710.660845] vfio-pci 0000:1d:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 [ 710.660851] vfio-pci 0000:1d:00.0: vfio_ecap_init: hiding ecap 0x23@0xac0 [ 711.748760] vfio-pci 0000:1e:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258 [ 711.748791] vfio-pci 0000:1e:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 [ 711.748797] vfio-pci 0000:1e:00.0: vfio_ecap_init: hiding ecap 0x23@0xac0 [ 712.836687] vfio-pci 0000:1c:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258 [ 712.836718] vfio-pci 0000:1c:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 [ 712.836725] vfio-pci 0000:1c:00.0: vfio_ecap_init: hiding ecap 0x23@0xac0 Thanks.

2 1

No bootable disk OVA
by cello86＠gmail.com 07 Jul '23

07 Jul '23

Hi all, we imported a rhel 9.2 image from an OVA generated on vmware and we tried to create a new VM but we had a no bootable disk error. The OVA has been imported with virt-2-v library and if we create a new VM we noticed that the disk is 2 GB size but we resized the disk to 50 GB. The VM has been started with Q35 Chipset with UEFI options and the disk has the flag bootable activated. We're using ovirt 4.5.4-1 Could you help us to sort this issue? Thanks, Marcello

4 4

Restoring HE Fails, engine-config cannot connect to database
by Levi Wilbert 06 Jul '23

06 Jul '23

I am attempting to restore n HE backup to a fresh host (not previously in the old environment) in order to restore our old environment but running into issues during the deployment. Basically my goal is to remove and redeploy an existing HE back into its same environment on a new storage domain. What I've done: backed up HE from prior environment Installed oVirt 4.5.10 on a fresh node that was not in the prior environment Ran the redeployment: hosted-engine --deploy --restore-from-file=<bkpfile> --4 The script pauses the deployment (even tho I told it not to), during this part I update /etc/dnf/dnf.conf w/ "exclude=ansible-core" since once ansible-core is updated it breaks the deployment script w/ Python incompatibilities. But I'm running into the following: [ ERROR ] fatal: [localhost -> 192.168.222.158]: FAILED! => {"changed": true, "cmd": "set -euo pipefail && engine-config -g DisableFenceAtStartupInSec | cut -d' ' -f2 > /root/DisableFenceAtStartupInSec.txt", "delta": "0:00:01.296169", "end": "2023-07-05 11:29:14.101292", "msg": "non-zero return code", "rc": 1, "start": "2023-07-05 11:29:12.805123", "stderr": "Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false", "stderr_lines": ["Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false"], "stdout": "", "stdout_lines": []} I see that it fails running the engine-config command on the new hosted engine, but when I SSH to it and try running it, I get: # engine-config -l Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false Connection to the Database failed. Please check that the hostname and port number are correct and that the Database service is up and running. I haven't been able to find anything specifically for this area searching through Google. Anyone have any idea where to go with this?

2 1

ovirt 4.5.4 deploy self-hosted engine
by Jorge Visentini 06 Jul '23

06 Jul '23

Hi. I'm trying to deploy the engine but I'm having some errors that I couldn't identify. I don't know if it's incompatibility with my hardware or some libvirt bug. Jul 05 10:06:21 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[690916]: 690917 still running (48505) Jul 05 10:06:21 ksmmi1r02ovirt36.kosmo.cloud libvirtd[701878]: Domain id=1 name='HostedEngineLocal' uuid=922a156c-7f4c-4815-a645-54ed07 794451 is tainted: custom-ga-command Jul 05 10:06:21 ksmmi1r02ovirt36.kosmo.cloud virtlogd[630980]: Client hit max requests limit 1. This may result in keep-alive timeouts. Consider tuning the max_client_requests server parameter Jul 05 10:06:22 ksmmi1r02ovirt36.kosmo.cloud libvirtd[701878]: Invalid value '-1' for 'cpu.max': Invalid argument Jul 05 10:06:26 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[690916]: 690917 still running (48500) Jul 05 10:06:31 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[690916]: 690917 still running (48495) Jul 05 10:06:31 ksmmi1r02ovirt36.kosmo.cloud systemd[1]: systemd-timedated.service: Deactivated successfully. Jul 05 10:06:36 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[690916]: 690917 still running (48490) Jul 05 10:06:37 ksmmi1r02ovirt36.kosmo.cloud libvirtd[701878]: Invalid value '-1' for 'cpu.max': Invalid argument Jul 05 10:06:41 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[690916]: 690917 still running (48485) Jul 05 10:06:46 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[690916]: 690917 still running (48480) Jul 05 10:06:51 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[690916]: 690917 still running (48475) Jul 05 10:06:52 ksmmi1r02ovirt36.kosmo.cloud libvirtd[701878]: Invalid value '-1' for 'cpu.max': Invalid argument Jul 05 10:06:56 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[690916]: 690917 still running (48470) Jul 05 10:07:01 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[690916]: 690917 still running (48465) *My config:* *CPU:* 2 x Intel(R) Xeon(R) Platinum 8276M CPU @ 2.20GHz *Memory:* 4TB *Disk:* 120GB RAID 1 *ISO:* ovirt-node-ng-installer-4.5.4-2022120615.el9.iso *Packages:* kernel-5.14.0-202.el9.x86_64 libvirt-8.9.0-2.el9.x86_64 centos-release-ovirt45-9.1-3.el9s.noarch python3-ovirt-engine-sdk4-4.6.0-1.el9.x86_64 ovirt-imageio-common-2.4.7-1.el9.x86_64 ovirt-imageio-client-2.4.7-1.el9.x86_64 ovirt-openvswitch-ovn-2.15-4.el9.noarch ovirt-openvswitch-ovn-common-2.15-4.el9.noarch ovirt-imageio-daemon-2.4.7-1.el9.x86_64 ovirt-openvswitch-ovn-host-2.15-4.el9.noarch python3-ovirt-setup-lib-1.3.3-1.el9.noarch ovirt-vmconsole-1.0.9-1.el9.noarch ovirt-vmconsole-host-1.0.9-1.el9.noarch ovirt-openvswitch-2.15-4.el9.noarch python3-ovirt-node-ng-nodectl-4.4.2-1.el9.noarch ovirt-node-ng-nodectl-4.4.2-1.el9.noarch ovirt-ansible-collection-3.0.0-1.el9.noarch ovirt-python-openvswitch-2.15-4.el9.noarch ovirt-openvswitch-ipsec-2.15-4.el9.noarch ovirt-hosted-engine-ha-2.5.0-1.el9.noarch ovirt-provider-ovn-driver-1.2.36-1.el9.noarch ovirt-host-dependencies-4.5.0-3.el9.x86_64 ovirt-hosted-engine-setup-2.7.0-1.el9.noarch ovirt-host-4.5.0-3.el9.x86_64 ovirt-release-host-node-4.5.4-1.el9.x86_64 ovirt-node-ng-image-update-placeholder-4.5.4-1.el9.noarch ovirt-engine-appliance-4.5-20221206125848.1.el9.x86_64 For better understanding, the deploy log is attached. I appreciate any tips that help me. Thank you! -- Att, Jorge Visentini +55 55 98432-9868

3 5

ovirt template import using ansible
by destfinal＠googlemail.com 05 Jul '23

05 Jul '23

Hi, I use a set of templates, generated in one cluster and re-used in multiple clusters. The clusters do not have direct connections between each other. My dev environment can talk to all the clusters. Currently, 1. I export the templates (as OVAs) to one of the nodes (example: node1.source.cluster), from the ovirt console (https://management.source.cluster) 2. scp the templates to my dev machine (example: scp -r node1.source.cluster:/tmp/ovirt_templates /tmp/ovirt_templates) 3. scp the templates from my dev environment to the target cluster (example: scp /tmp/ovirt_templates node1.target.cluster:/tmp) 4. Import the templates using the ovirt console of the target cluster (https://management.target.cluster) This is highly a manual job and I am trying to automate the process using ansible. I am unable to work it out using the ovit_template module documentation (https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_templ…) and could not able to see any other module in this relation. Has anybody done this before and point me to the right direction? Or if there is a better process than what I follow above, please suggest me one. Please let me know if you need more information in this regard. Thanks

4 10

Managing Ovirt Networks with Ansible
by William Roberts 29 Jun '23

29 Jun '23

Hi Team, So I'm setting up some automation to build an environment within an ovirt cluster of X amount of nodes. Part of that is the creation of the networks, and subsequently the attaching of those network to each host in the cluster. Seems pretty straight forward except for the fact you need the name of the interfaces to attach the networks to, unfortunately none of the ansible 2.9 modules I've been trying give you that information. Specifically ovirt_host_info, has a list item called "nics" which i assumed would give it but it doesn't return a value. Does anyone know of a module that would give this info? seems like a pretty crucial thing to be missing. TIA Will

1 0

securing ovirt vnc console
by Bill James 28 Jun '23

28 Jun '23

Our security requirements require that we disable tls1.0 and tla1.1 for VNC port, 59xx. I have not yet been able to find where this can be done, only for spice console. Can anyone assist in pointing me to what config file controls this? ovirt-engine 4.3.

1 0

Re: Customizing ovirt vm / user web portal
by R A 28 Jun '23

28 Jun '23

Hello, the idea was to run the vm portal from another host and connect it through REST-API with the host which run ovirt-engine for example for a dev environment. So it’s not possible? I guess importing the third Party CA local in to ovirt-engine should also work local with the vmportal. BR Peter Von: Patrick Hibbs <hibbsncc1701(a)gmail.com> Gesendet: Mittwoch, 28. Juni 2023 10:27 An: R A <Jarheadx(a)hotmail.de> Betreff: Re: [ovirt-users] Re: Customizing ovirt vm / user web portal Hello, oVirt doesn't use the system wide java keystore. It uses it's own at /etc/pki/ovirt-engine/.truststore If you want your third party cert to work with the java components, such as the disc image uploader function in the admin console, you'll either need to follow the official documentation for altering it. Or import the third party CA manually. (It uses the default keystore password.) -Patrick Hibbs

1 0

Bcp vm
by Ali Gusainov 27 Jun '23

27 Jun '23

Hello experts. Environment: 2 identical servers running CentOS Linux release 7.7.1908 oVirt Version:4.3.7.2-1.el7 No clusters configured. NFS share for backups on third server. Have some questions. 1. Need to create backups of virtual machines to NFS without downtime. Can an 'OVA export' be a complete policy for backups? 2. Is there a way to export vm to OVA via command line?

2 5

How to add alternate fqdn
by BJ一哥 27 Jun '23

27 Jun '23

Version 4.5.1 I try to modify the parameter of SSO_ALTERNATE_ENGINE_FQDNS in /etc/ovirt-engine/engine.conf.d/11-setup-sso.conf to a new domain name The web interface opens normally, but the management portal cannot be accessed. Entering the management portal prompts 500 internal Server error

1 0

Re: Customizing ovirt vm / user web portal
by Jorge Visentini 26 Jun '23

26 Jun '23

Following for being interesting... Em sex., 23 de jun. de 2023 às 10:01, R A <jarheadx(a)hotmail.de> escreveu: > Hello, > > > > i want to customize the interface and some functions in the ovirt user > portal. > > > > For example adding some Buttons with functionality or doing some style > changes. > > > > Is this possible? Is there any guide how to do that? > > > > BR > > Peter > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/RI23B7PVQTVHK… > -- Att, Jorge Visentini +55 55 98432-9868

3 2

HostEngine added alternate fqdn cannot be accessed
by ziyi Liu 26 Jun '23

26 Jun '23

I modified the parameter of SSO_ALTERNATE_ENGINE_FQDNS to the new fqdn in /etc/ovirt-engine/engine.conf.d/11-setup-sso.conf. After modifying the hosts, I can use the new fqdn to open the web but cannot enter the portal management, prompting 500 Internal Server Error

1 0

Re: ovirt 4.5 VNC Failed to complete handshake Error in the pull function on Windows
by Patrick Hibbs 25 Jun '23

25 Jun '23

Hello, On 6/23/23 13:23, R A wrote: > > Hello, > > i am using ovirt 4.5.4-1.el9 standalone on Rocky Linux and have some > struggle with vnc connection. > > I ve engine.mydomain.de which contains the ovirt-engine. I installed > third party certificate successfully. So when i call > engine.mydomain.de/ovirt-engine or node1.mydomain.de:9090 the browser > tell me that connection is secured. > > My first host is node1.mydomain.de, which has currently one VM up. > > On Linux Client (Rocky Linux 9.2) > > 1. When i run „remote-viewer --debug /home/user1/Downloads/console.vv > --gtk-vnc-debug“ everything works fine. RemoteViewer opens and i > can see the console of my vm > 2. When i try to open the console.vv directly via remoteViewer from > enngine-portal i get feedback from remoteViewer: „The certificate > is not trusted“ > Did you do that after opening console.vv manually? Or did you download a new console.vv before doing so? console.vv files are good for one use only. As they contain a one-time password that is revoked after use. > 1. 3. When i try to open via novnc a new tab opens and i get > „Something went wrong, connection is closed“ > Again, did you reuse that console.vv file? Or did you download a new one? FYI: The file should be deleted automatically after remote-viewer opens it. As it's not supposed to be reused. > > On Windows 11 > > 1. When i generate the console.vv and copy the password and > hostadress + port to TigerVNC client everything work fine. > TigerVNC tells me that connection is secured > 2. When opening console.vv directly via RemoteViewer i get „Filed to > complete handshake Error in the pull function > 3. When i try to open via novnc a new tab opens and i get „Something > went wrong, connection is closed“ > 4. When i run "C:\ProgramData\Microsoft\Windows\Start > Menu\Programs\VirtViewer\Remote viewer.lnk" --debug > C:\Users\rezaa\Downloads\console.vv --gtk-vnc-debug > > I get : > > C:\Users\rezaa>"C:\ProgramData\Microsoft\Windows\Start > Menu\Programs\VirtViewer\Remote viewer.lnk" --debug > C:\Users\rezaa\Downloads\console.vv --gtk-vnc-debug > > C:\Users\rezaa>(remote-viewer.exe:9460): virt-viewer-DEBUG: > 19:16:33.218: keymap string is empty - nothing to do > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.264: Opening > display to C:\Users\rezaa\Downloads\console.vv > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.265: Guest > (NULL) has a vnc display > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.271: > ../src/vncconnection.c Init VncConnection=00000000070f1c90 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.271: > ../src/vncdisplaykeymap.c Using Win32 virtual keycode mapping > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.272: > ../src/vncdisplay.c Grab sequence is now Control_L+Alt_L > > (remote-viewer.exe:9460): libsoup-WARNING **: 19:16:33.277: Could not > set SSL credentials from '/etc/pki/tls/certs/ca-bundle.crt': > Vertrauenswürdigkeitsliste konnte nicht aus > /etc/pki/tls/certs/ca-bundle.crt befüllt werden: Error while reading file. > > (remote-viewer.exe:9460): libsoup-WARNING **: 19:16:33.277: Could not > set SSL credentials from '/etc/pki/tls/certs/ca-bundle.crt': > Vertrauenswürdigkeitsliste konnte nicht aus > /etc/pki/tls/certs/ca-bundle.crt befüllt werden: Error while reading file. > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.278: Spice > foreign menu updated > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.278: After open > connection callback fd=-1 > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.279: Opening > connection to display at C:\Users\rezaa\Downloads\console.vv > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.289: fullscreen > display 0: 0 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.289: > ../src/vncconnection.c Open host=node1.mydomain.de port=5900 > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.289: notebook > show status 0000000004408580 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.875: > ../src/vncconnection.c Open coroutine starting > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.876: > ../src/vncconnection.c Started background coroutine > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.877: > ../src/vncconnection.c Resolving host node1.mydomain.de 5900 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.880: > ../src/vncconnection.c Trying one socket > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.881: > ../src/vncconnection.c Schedule socket timeout 00000000070f0a40 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.882: > ../src/vncconnection.c Socket pending > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.914: > ../src/vncconnection.c Finally connected > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.915: > ../src/vncconnection.c Remove timeout 00000000070f0a40 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.916: > ../src/vncconnection.c Emit main context 13 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.917: > ../src/vncdisplay.c Grab sequence is now > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.917: notebook > show status 0000000004408580 > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.919: Insert > display 0 0000000007572f80 > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.919: notebook > show status 0000000004408580 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.920: > ../src/vncdisplay.c Connected to VNC server > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.920: > ../src/vncconnection.c Protocol initialization > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.920: > ../src/vncconnection.c Schedule greeting timeout 00000000070f0a40 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.921: > ../src/vncconnection.c Read error Ein nicht blockierender > Socketvorgang konnte nicht sofort ausgeführt werden. > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.922: Allocated > 1024x768 > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:33.922: Child > allocate 1024x640 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.946: > ../src/vncconnection.c Remove timeout 00000000070f0a40 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.947: > ../src/vncconnection.c Server version: 3.8 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.950: > ../src/vncconnection.c Sending full greeting > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.951: > ../src/vncconnection.c Using version: 3.8 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.964: > ../src/vncconnection.c Read error Ein nicht blockierender > Socketvorgang konnte nicht sofort ausgeführt werden. > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.983: > ../src/vncconnection.c Possible auth 19 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.984: > ../src/vncconnection.c Emit main context 11 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.984: > ../src/vncconnection.c Thinking about auth type 19 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.985: > ../src/vncconnection.c Decided on auth type 19 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.985: > ../src/vncconnection.c Waiting for auth type > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.986: > ../src/vncconnection.c Choose auth 19 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.986: > ../src/vncconnection.c Checking if credentials are needed > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.987: > ../src/vncconnection.c No credentials required > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:33.987: > ../src/vncconnection.c Read error Ein nicht blockierender > Socketvorgang konnte nicht sofort ausgeführt werden. > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.019: > ../src/vncconnection.c Read error Ein nicht blockierender > Socketvorgang konnte nicht sofort ausgeführt werden. > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.050: > ../src/vncconnection.c Possible VeNCrypt sub-auth 261 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.051: > ../src/vncconnection.c Emit main context 12 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.052: > ../src/vncconnection.c Requested auth subtype 261 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.053: > ../src/vncconnection.c Waiting for VeNCrypt auth subtype > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.054: > ../src/vncconnection.c Choose auth 261 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.055: > ../src/vncconnection.c Checking if credentials are needed > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.056: > ../src/vncconnection.c No credentials required > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.056: > ../src/vncconnection.c Read error Ein nicht blockierender > Socketvorgang konnte nicht sofort ausgeführt werden. > > (remote-viewer.exe:9460): GLib-GIO-WARNING **: 19:16:34.073: > Unexpectedly, UWP app > `Microsoft.ScreenSketch_11.2303.17.0_x64__8wekyb3d8bbwe' (AUMId > `Microsoft.ScreenSketch_8wekyb3d8bbwe!App') supports 29 extensions but > has no verbs > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.088: > ../src/vncconnection.c Do TLS handshake > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.089: > ../src/vncconnection.c Checking if credentials are needed > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.092: > ../src/vncconnection.c Want a TLS clientname > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.094: > ../src/vncconnection.c Requesting missing credentials > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.102: > ../src/vncconnection.c Emit main context 10 > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:34.105: Got VNC > credential request for 1 credential(s) > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.105: > ../src/vncconnection.c Set credential 2 libvirt > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.106: > ../src/vncconnection.c Searching for certs in > /usr/x86_64-w64-mingw32/sys-root/mingw/etc/pki > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.108: > ../src/vncconnection.c Failed to find certificate CA/cacert.pem > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.109: > ../src/vncconnection.c No CA certificate provided, using GNUTLS global > trust > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.111: > ../src/vncconnection.c Failed to find certificate CA/cacrl.pem > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.113: > ../src/vncconnection.c Failed to find certificate > libvirt/private/clientkey.pem > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.113: > ../src/vncconnection.c Failed to find certificate libvirt/clientcert.pem > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.114: > ../src/vncconnection.c Waiting for missing credentials > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.117: > ../src/vncconnection.c Got all credentials > > ( > > remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.120: > ../src/vncconnection.c No CA certificate provided; trying the system > trust store instead > > (remote-viewer.exe:9460): GLib-GIO-WARNING **: 19:16:34.120: > Unexpectedly, UWP app > `Clipchamp.Clipchamp_2.6.2.0_neutral__yxz26nhyzhsrt' (AUMId > `Clipchamp.Clipchamp_yxz26nhyzhsrt!App') supports 41 extensions but > has no verbs > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.132: > ../src/vncconnection.c Using the system trust store and CRL > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.132: > ../src/vncconnection.c No client cert or key provided > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.133: > ../src/vncconnection.c No CA revocation list provided > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.133: > ../src/vncconnection.c Error: Failed to complete handshake Error in > the pull function. > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.134: > ../src/vncconnection.c Emit main context 16 > > (remote-viewer.exe:9460): virt-viewer-WARNING **: 19:16:34.134: > vnc-session: got vnc error Failed to complete handshake Error in the > pull function. > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.135: > ../src/vncdisplay.c VNC server error > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.135: > ../src/vncconnection.c Auth failed > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.135: > ../src/vncconnection.c Doing final VNC cleanup > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.136: > ../src/vncconnection.c Close VncConnection=00000000070f1c90 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.136: > ../src/vncconnection.c Emit main context 15 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.137: > ../src/vncdisplay.c Disconnected from VNC server > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:34.137: Not > removing main window 0 00000000044694d0 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:34.138: > ../src/vncdisplay.c Grab sequence is now > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:34.138: Disconnected > > (remote-viewer.exe:9460): virt-viewer-DEBUG: 19:16:47.126: close > vnc=00000000070ec090 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:47.127: > ../src/vncconnection.c Init VncConnection=00000000053f6af0 > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:47.127: > ../src/vncdisplaykeymap.c Using Win32 virtual keycode mapping > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:47.128: > ../src/vncdisplay.c Grab sequence is now Control_L+Alt_L > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:47.129: > ../src/vncdisplay.c Display destroy, requesting that VNC connection close > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:47.129: > ../src/vncdisplay.c Releasing VNC widget > > (remote-viewer.exe:9460): gtk-vnc-DEBUG: 19:16:47.129: > ../src/vncconnection.c Finalize VncConnection=00000000053f6af0 > This looks like your Windows host lacks the ovirt-engine CA in it's trust store. You should try importing the CA first before opening the console.vv file. It's not possible* to use a third party CA to secure the VNC connections. As the VNC connections originate on the virtualization hosts themselves, the CA that they use is the internal ovirt-engine CA that was automatically generated by engine-setup. If you don't want to import the ovirt-engine CA on the end-user machines, your best option is to force end users through the end-user portal. Alternatively, you could disable VNC encryption entirely and secure the link via other means. *: Technically it is possible to use a third party CA cert on the VNC connections, but it will only work until VDSM reboots the host or performs a host upgrade. As there is no way to force VDSM to ignore the "invalid" custom cert. -Patrick Hibbs > The solutions provided here was not successfull > https://access.redhat.com/solutions/6217601 > > BR > > R A > > > _______________________________________________ > Users mailing list --users(a)ovirt.org > To unsubscribe send an email tousers-leave(a)ovirt.org > Privacy Statement:https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct:https://www.ovirt.org/community/about/community-guidelines/ > List Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/XG7T…

2 1