June 2024 - Users - oVirt List Archives

Installing oVirt on RHEL vs CentOS Stream, Alma or Rocky Linux
by Richard W.M. Jones 06 Oct '25

06 Oct '25

I'm still struggling to get oVirt installed. It absolutely will not install on RHEL 8, the documentation here is flat out wrong: https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manage… javapackages-tools is not a module that exists in RHEL 8. Apparently it's a CentOS PowerTools module. Since original CentOS no longer really exists either, does anyone have any opinions or experience with installing oVirt on any of: - CentOS Stream 8 - Alma Linux 8.5 - Rocky Linux Alma in particular looks like a straight replacement for old CentOS. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top

8 10

Error when deploy Ovirt4.4 Hosted Engine
by staybox＠gmail.com 17 Feb '25

17 Feb '25

Hello, I get error, need help. [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The conditional check 'not ipv6_deployment|bool and route_rules_ipv4.stdout | from_json | selectattr('priority', 'equalto', 100) | selectattr('dst', 'equalto', virbr_cidr_ipv4 | ipaddr('address') ) | list | length == 0' failed. The error was: error while evaluating conditional (not ipv6_deployment|bool and route_rules_ipv4.stdout | from_json | selectattr('priority', 'equalto', 100) | selectattr('dst', 'equalto', virbr_cidr_ipv4 | ipaddr('address') ) | list | length == 0): 'dict object' has no attribute 'dst'\n\nThe error appears to be in '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/01_prepare_routing_rules.yml': line 81, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n changed_when: true\n - name: Add IPv4 inbound route rules\n ^ here\n"}

4 4

How to list all snapshots?
by jorgevisentini＠gmail.com 14 Feb '25

14 Feb '25

Hello everyone! First, I would like to thank everyone involved in this wonderful project. I leave here my sincere thanks! Does anyone know if it is possible to list all snapshots automatically? It can be by ansible, python, shell... any way that helps to list them all without having to enter Domain by Domain. Thank you all!

4 3

snapshot solution: Existing snapshots that were taken after this one will be erased.
by dhanaraj.ramesh＠yahoo.com 29 Jan '25

29 Jan '25

Hi Team, when I want to commit the older snapshots I'm getting warning stating " Existing snapshots that were taken after this one will be erased.". is there any way we can retain the latest snapshots as is in the chain? I knew cloning and template export options are there to secure that latest snapshot data but these are will consume additional space in storage and take time.

4 3

Restart oVirt-Engine
by Jeremey Wise 09 Jan '25

09 Jan '25

How ,without reboot of hosting system, do I restart the oVirt engine? # I tried below but do not seem to effect the virtual machine [root@thor iso]# systemctl restart ov ovirt-ha-agent.service ovirt-imageio.service ovn-controller.service ovs-delete-transient-ports.service ovirt-ha-broker.service ovirt-vmconsole-host-sshd.service ovsdb-server.service ovs-vswitchd.service [root@thor iso]# # You cannot restart the VM " HostedEngine " as it responses: Error while executing action: HostedEngine: - Cannot restart VM. This VM is not managed by the engine. Reason is I had to do some work on a node. Reboot it.. it is back up.. network is all fine.. Cockpit working fine... and gluster fine.. But oVirt-Engine refuses to accept the node is up. -- p <jeremey.wise(a)gmail.com>enguinpages

4 4

Host deploy failure: Configure OVN for oVirt
by stephan.badenhorst＠fnb.co.za 05 Jan '25

05 Jan '25

Good day, I am running into a problem during host deploy via the oVirt engine GUI since upgrading to ovirt-engine-4.5.5-1.el8. The "Configure OVN for oVirt" task seem to fail when trying to run the vdsm-tool ovn-config command. Host deploy used to work fine when the engine was on version 4.5.4. Anyone that can guide me on the right path to get past this issue? Does not seem to be a new problem - https://lists.ovirt.org/archives/list/users@ovirt.org/thread/IDLGSBQFX35EHH… Log extract: 2024-02-01 14:48:19 SAST - TASK [ovirt-provider-ovn-driver : Configure OVN for oVirt] ********************* . . . "stdout" : "fatal: [mob-r1-l-ovirt-aa-1-23.x.fnb.co.za]: FAILED! => {\"changed\": true, \"cmd\": [\"vdsm-tool\", \"ovn-config\", \"192.168.2.100\", \"host23.mydomain.com\"], \"delta\": \"0:00:00.538143\", \"end \": \"2024-02-01 14:48:20.596823\", \"msg\": \"non-zero return code\", \"rc\": 1, \"start\": \"2024-02-01 14:48:20.058680\", \"stderr\": \"Traceback (most recent call last):\\n File \\\"/usr/lib/python3.6/site-packages/vdsm/t ool/ovn_config.py\\\", line 117, in get_network\\n return networks[net_name]\\nKeyError: 'host23.mydomain.com'\\n\\nDuring handling of the above exception, another exception occurred:\\n\\nTraceback (most rec ent call last):\\n File \\\"/usr/bin/vdsm-tool\\\", line 195, in main\\n return tool_command[cmd][\\\"command\\\"](*args)\\n File \\\"/usr/lib/python3.6/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.6/site-packages/vdsm/tool/ovn_config.py\\\", line 119, in get_network\\n raise NetworkNotFoundError(net_name)\\nvdsm.tool.ovn _config.NetworkNotFoundError: host23.mydomain.com\", \"stderr_lines\": [\"Traceback (most recent call last):\", \" File \\\"/usr/lib/python3.6/site-packages/vdsm/tool/ovn_config.py\\\", line 117, in get_network \", \" return networks[net_name]\", \"KeyError: 'host23.mydomain.com'\", \"\", \"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.6/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.6/site-packages/vdsm/tool/ovn_config.py\\\", line 119, in get_network\", \" raise NetworkNotFoundError(net_name)\", \"vdsm.tool.ovn_config. NetworkNotFoundError: host23.mydomain.com\"], \"stdout\": \"\", \"stdout_lines\": []}", Thanks in advance!! Stephan

5 5

Unable to access ovirt Admin Screen from ovirt Host
by louisb＠ameritech.net 07 Dec '24

07 Dec '24

I've reinstalled ovirt 4.4 on my server remotely via cockpit terminal. I'm able to access the ovirt admin screen remotely from the laptop that I used for the install. However, using the same URL I'm unable to gain access to the admin screen. Following the instruction in the documentation I've modified the file: /etc/ovirt-engine/engine.conf.d/99-custom-sso-setup.conf, to reflect the DNS name and I enter in the IP address. But I'm still unable to access the screen from the server console. What else needs to change in order to gain access from the server console? Thanks

5 8

SPM and Task error ...
by Enrico 22 Nov '24

22 Nov '24

Hi all, my ovirt cluster has got 3 Hypervisors runnig Centos 7.5.1804 vdsm is 4.20.39.1-1.el7, ovirt engine is 4.2.4.5-1.el7, the storage systems are HP MSA P2000 and 2050 (fibre channel). I need to stop one of the hypervisors for maintenance but this system is the storage pool manager. For this reason I decided to manually activate SPM in one of the other nodes but this operation is not successful. In the ovirt engine (engine.log) the error is this: 2019-07-25 12:39:16,744+02 INFO [org.ovirt.engine.core.bll.storage.pool.ForceSelectSPMCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] Running command: ForceSelectSPMCommand internal: false. Entities affected : ID: 81c9bd3c-ae0a-467f-bf7f-63ab30cd8d9e Type: VDSAction group MANIPULATE_HOST with role type ADMIN 2019-07-25 12:39:16,745+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SpmStopOnIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, SpmStopOnIrsVDSCommand( SpmStopOnIrsVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false'}), log id: 37bf4639 2019-07-25 12:39:16,747+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ResetIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, ResetIrsVDSCommand( ResetIrsVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', vdsId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', ignoreStopFailed='false'}), log id: 2522686f 2019-07-25 12:39:16,749+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, SpmStopVDSCommand(HostName = infn-vm05.management, SpmStopVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7'}), log id: 1810fd8b 2019-07-25 12:39:16,758+02 *ERROR* [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] SpmStopVDSCommand::Not stopping SPM on vds 'infn-vm05.management', pool id '18d57688-6ed4-43b8-bd7c-0665b55950b7' as there are uncleared tasks 'Task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e', status 'running'' 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, SpmStopVDSCommand, log id: 1810fd8b 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ResetIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, ResetIrsVDSCommand, log id: 2522686f 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SpmStopOnIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, SpmStopOnIrsVDSCommand, log id: 37bf4639 2019-07-25 12:39:16,760+02 *ERROR* [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] EVENT_ID: USER_FORCE_SELECTED_SPM_STOP_FAILED(4,096), Failed to force select infn-vm07.management as the SPM due to a failure to stop the current SPM. while in the hypervisor (SPM) vdsm.log: 2019-07-25 12:39:16,744+02 INFO [org.ovirt.engine.core.bll.storage.pool.ForceSelectSPMCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] Running command: ForceSelectSPMCommand internal: false. Entities affected : ID: 81c9bd3c-ae0a-467f-bf7f-63ab30cd8d9e Type: VDSAction group MANIPULATE_HOST with role type ADMIN 2019-07-25 12:39:16,745+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SpmStopOnIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, SpmStopOnIrsVDSCommand( SpmStopOnIrsVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false'}), log id: 37bf4639 2019-07-25 12:39:16,747+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ResetIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, ResetIrsVDSCommand( ResetIrsVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', vdsId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', ignoreStopFailed='false'}), log id: 2522686f 2019-07-25 12:39:16,749+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, SpmStopVDSCommand(HostName = infn-vm05.management, SpmStopVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7'}), log id: 1810fd8b 2019-07-25 12:39:16,758+02 *ERROR* [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] SpmStopVDSCommand::Not stopping SPM on vds 'infn-vm05.management', pool id '18d57688-6ed4-43b8-bd7c-0665b55950b7' as there are uncleared tasks 'Task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e', status 'running'' 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, SpmStopVDSCommand, log id: 1810fd8b 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ResetIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, ResetIrsVDSCommand, log id: 2522686f 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SpmStopOnIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, SpmStopOnIrsVDSCommand, log id: 37bf4639 2019-07-25 12:39:16,760+02 *ERROR* [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] EVENT_ID: USER_FORCE_SELECTED_SPM_STOP_FAILED(4,096), Failed to force select infn-vm07.management as the SPM due to a failure to stop the current SPM. 2019-07-25 12:39:18,660+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Task id 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' has passed pre-polling period time and should be polled. Pre-polling period is 60000 millis. 2019-07-25 12:39:18,660+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Task id 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' has passed pre-polling period time and should be polled. Pre-polling period is 60000 millis. 2019-07-25 12:39:18,750+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Task id 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' has passed pre-polling period time and should be polled. Pre-polling period is 60000 millis. 2019-07-25 12:39:18,750+02 *ERROR* [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] BaseAsyncTask::logEndTaskFailure: Task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' (Parent Command 'Unknown', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended with failure: 2019-07-25 12:39:18,750+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' 2019-07-25 12:39:18,751+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: 34ae2b2f 2019-07-25 12:39:18,752+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, HSMClearTaskVDSCommand(HostName = infn-vm05.management, HSMTaskGuidBaseVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: d3a78ad 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, HSMClearTaskVDSCommand, log id: d3a78ad 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, SPMClearTaskVDSCommand, log id: 34ae2b2f 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: At time of attempt to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' the response code was 'TaskStateError' and message was 'Operation is not allowed in this task state: ("can't clean in state running",)'. Task will not be cleaned 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] BaseAsyncTask::onTaskEndSuccess: Task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' (Parent Command 'Unknown', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended successfully. 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' 2019-07-25 12:39:18,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: 42de0c2b 2019-07-25 12:39:18,759+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, HSMClearTaskVDSCommand(HostName = infn-vm05.management, HSMTaskGuidBaseVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: 4895c79c 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, HSMClearTaskVDSCommand, log id: 4895c79c 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, SPMClearTaskVDSCommand, log id: 42de0c2b 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: At time of attempt to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' the response code was 'TaskStateError' and message was 'Operation is not allowed in this task state: ("can't clean in state running",)'. Task will not be cleaned 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Task id 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' has passed pre-polling period time and should be polled. Pre-polling period is 60000 millis. 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Cleaning zombie tasks: Clearing async task 'Unknown' that started at 'Fri May 03 14:48:50 CEST 2019' 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' 2019-07-25 12:39:18,765+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: da77af2 2019-07-25 12:39:18,766+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, HSMClearTaskVDSCommand(HostName = infn-vm05.management, HSMTaskGuidBaseVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: 530694fb 2019-07-25 12:39:18,771+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, HSMClearTaskVDSCommand, log id: 530694fb 2019-07-25 12:39:18,771+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, SPMClearTaskVDSCommand, log id: da77af2 2019-07-25 12:39:18,771+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: At time of attempt to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' the response code was 'TaskStateError' and message was 'Operation is not allowed in this task state: ("can't clean in state running",)'. Task will not be cleaned there is some relation between this error and a task that has remained hanging, from SPM server: # vdsm-client Task getInfo taskID=fdcf4d1b-82fe-49a6-b233-323ebe568f8e { "verb": "prepareMerge", "id": "fdcf4d1b-82fe-49a6-b233-323ebe568f8e" } # vdsm-client Task getStatus taskID=fdcf4d1b-82fe-49a6-b233-323ebe568f8e { "message": "running job 1 of 1", "code": 0, "taskID": "fdcf4d1b-82fe-49a6-b233-323ebe568f8e", "taskResult": "", "taskState": "running" } How can I solve this problem ? Thanks a lot for your help !! Best Regards Enrico -- _______________________________________________________________________ Enrico Becchetti Servizio di Calcolo e Reti Istituto Nazionale di Fisica Nucleare - Sezione di Perugia Via Pascoli,c/o Dipartimento di Fisica 06123 Perugia (ITALY) Phone:+39 075 5852777 Mail: Enrico.Becchetti<at>pg.infn.it _______________________________________________________________________

5 15

oVirt CLI tool for automation tasks
by munnadawood＠gmail.com 15 Nov '24

15 Nov '24

We recently migrated from VMware to oVirt. I am looking for any CLI tool well suited for my automation tasks like VM create, clone, migrate 100s of Virtual machines in oVirt cluster. with VMware I was using govc (vSphere CLI built on top of govmomi). Another option I read is powercli, quite unsure if it works with oVirt. Any suggestions would be highly appreciated. Thanks!

5 6

Latest 4.5.5 centos node install username password not working.
by antonio.riggio＠mail.com 24 Oct '24

24 Oct '24

I been trying to install 4.5.5 testing and used the node installer iso. I cant login what is the username and password I have tried what others have done in the forums with no luck admin@ovirt . root admin . Also can the engine be installed from the node via the cockpit still? How can I get logged in to do this? I have used 4.3 and didnt have any of these problems. It was really simple to do. Any suggestions? grazie

4 8

Storage Domain Not synchronized, To synchronize them, please move them to maintenance and then activate.
by Arup Jyoti Thakuria 09 Sep '24

09 Sep '24

Dear All, In our Ovirt Engine Infrastructure, recently we have received an alert for one of our "Storage Domain" The alert is as mentioned below---- =================================== Storage domains with IDs [fb34e5b7-e850-4d66-ab47-3011d2000338] could not be synchronized. To synchronize them, please move them to maintenance and then activate. ========================================================== What is the consequence of this alert, if we ignore this what can happen to the infra, are we going to face any issue with the VMs, currently this infra is under production

2 1

Váltás a Centos Stream 9-re.
by tasnadi.peter＠kifu.gov.hu 04 Sep '24

04 Sep '24

Hello! We have a oVirt 4.5.6-1.el8 cluster. oVirt node Centos Stream 8 based. (5pcs) oVirt Hosted Engine Centos stream 8 based. We installed the hosts from an ISO image and the Hosted Engine we deployed from such a host. Link: https://resources.ovirt.org/pub/ovirt-4.5/iso/ovirt-node-ng-installer/4.5.5… How can we switch to Centos Stream 9 OS in the simplest way without downtime? Thanks in advance for the answer! Peter

2 1

oVirt networks
by Enrico Becchetti 28 Aug '24

28 Aug '24

Dear all, Ineed your help to understand how to configure the network of a new oVirt cluster. Mynew system will have a 4.3 engine thatruns in a virtual machine, andsome Dell R7525 AMD EPYC hypervisors, eachholding two 4-port PCI network cards. These servers will have node-ovirt image again in version 4.3. As for the network, there are two HPE Aruba 2540G, non-stackable, with 24 1Gbs ports and 2 10Gbs uplinks to the star center. This is a simplified scheme: My goal is to make the most of the server's 8 ethernet interfaces to have both reliability and maximum possible throughput. This cluster will have two virtual networks, one forovirt management and one for the traffic of individual virtual machines. With that said here's what my idea is. I would like to have two links aggregated by 4Gbs, one for ovrtmgt and the other for vmnet. With the ovirt web interface I can createan active-passive "Mode 1" bond, but this won'tallow me to go beyond 1Gbs. Alternatively I could create a "Mode 4" bond 802.3ad but unfortunately the switches are not stacked and therefore not even this solution applies. This is an example with active passive configuration: Can you tell me if ovirt can generate//nested bonds? Or do you have other solutions ? Thanks a lot ! Best Regards Enrico -- _______________________________________________________________________ Enrico Becchetti Servizio di Calcolo e Reti Istituto Nazionale di Fisica Nucleare - Sezione di Perugia Via Pascoli,c/o Dipartimento di Fisica 06123 Perugia (ITALY) Phone:+39 075 5852777 Skype:enrico_becchetti Mail: Enrico.Becchetti<at>pg.infn.it Pagina web personale: https://www.pg.infn.it/home/enrico-becchetti/ ______________________________________________________________________

5 6

boot from cdrom & error code 0005
by edp＠maddalena.it 21 Aug '24

21 Aug '24

Hi. I have created a new storage domain (data domain, storage type nfs) to use it to upload iso images. I have so uploaded a new iso and then attach the iso to a new vm. But when I try to boot the vm I obtain this error: booting from dvd/cd... boot failed: could not read from cdrom (code 0005) no bootable device The iso file has been uploaded with success in the data storage domain and so the vm lets my attach the iso to the vm in the boot settings. Can you help me? Thank you

4 6

Importing VM from Vmware
by domenc＠gmail.com 24 Jul '24

24 Jul '24

Hi, Migrating VMs from Vmware works nice in the UI but it's slow. With https://blogs.oracle.com/scoter/post/how-to-migrate-vmware-vsphere-to-oracl… i'm trying to import exported VM virt-v2v \ –o rhv-upload \ –oc https://<OLVM-ENGINE-PORTAL>/ovirt-engine/api \ -op /root/olvm-admin-password-file \ -oo rhv-cacert=/root/ovirt-cacert.pem \ -oo rhv-cluster=<OLVM-CLUSTER> \ -os <OLVM_STORAGE_DOMAIN> \ -of qcow2 \ -oo rhv-direct \ --network <OLVM-NETWORK> \ -i libvirtxml <LOCAL-XML-FILE> I tried everything possible but still there is an error virt-v2v: error: no -oo (output options) are allowed here If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...] Any idea?

3 2

Problem with Glusterfs Distributed-Replicated volume almost full but only less than 50% used by files.
by Olivier 22 Jul '24

22 Jul '24

Hi, I have a weird problem with my couple Glusterfs-oVirt: I had two data domain for my VMs on oVirt. The main one (data) is a Distributed-Replicate with 2 x 3 = 6 bricks of ~ 1,4 Tb on 3 servers (2 bricks by server). It was an extend of a previous 1 x 3 = 3 Replicated volume on the same servers. I had one new disk (and one new brick) on each of these 3 servers. My concern is the reported use of this volume (almost 100%). a df -h give me : df -h . Filesystem Size Used Avail Use% Mounted on ovirt1.pmmg.priv:/data 3.4T 3.3T 84G 98% /rhev/data-center/mnt/glusterSD/ovirt1.pmmg.priv:_data but a du of the same partition give me : du -hs /rhev/data-center/mnt/glusterSD/ovirt1.pmmg.priv:_data 1.4T /rhev/data-center/mnt/glusterSD/ovirt1.pmmg.priv:_data and there no hidden folder I could miss in this mount point. The weird point (the second one) is when I delete a VMs and is disks (main disk and snapshot) I doesn't get back some space on these volume. Does anyone have an idea of these problem ? Thank's Here the Info of the gluster volume : gluster volume info data Volume Name: data Type: Distributed-Replicate Volume ID: 22b7942e-2952-40d4-ab92-64636e3ce409 Status: Started Snapshot Count: 0 Number of Bricks: 2 x 3 = 6 Transport-type: tcp Bricks: Brick1: ovirt1.pmmg.priv:/gluster_bricks/data/data Brick2: ovirt2.pmmg.priv:/gluster_bricks/data/data Brick3: ovirt3.pmmg.priv:/gluster_bricks/data/data Brick4: ovirt1.pmmg.priv:/gluster_bricks/data_extend1/data Brick5: ovirt2.pmmg.priv:/gluster_bricks/data_extend1/data Brick6: ovirt3.pmmg.priv:/gluster_bricks/data_extend1/data Options Reconfigured: features.shard-block-size: 128MB cluster.lookup-optimize: off server.keepalive-count: 5 server.keepalive-interval: 2 server.keepalive-time: 10 server.tcp-user-timeout: 20 performance.client-io-threads: on nfs.disable: on storage.fips-mode-rchecksum: on transport.address-family: inet performance.quick-read: off performance.read-ahead: off performance.io-cache: off performance.low-prio-threads: 32 network.remote-dio: disable cluster.eager-lock: enable cluster.quorum-type: auto cluster.server-quorum-type: server cluster.data-self-heal-algorithm: full cluster.locking-scheme: granular cluster.shd-max-threads: 8 cluster.shd-wait-qlength: 10000 features.shard: on user.cifs: off cluster.choose-local: off client.event-threads: 4 server.event-threads: 4 storage.owner-uid: 36 storage.owner-gid: 36 network.ping-timeout: 20 performance.strict-o-direct: on cluster.granular-entry-heal: enable features.trash: off

2 4

oVirt 4.5.5 compatibility with CPU
by jakov.jelinic＠adriatic.hr 18 Jul '24

18 Jul '24

Hi, We plan to install ovirt node 4.5.5 (https://resources.ovirt.org/pub/ovirt-4.5/iso/ovirt-node-ng-installer/) on our 2 new servers, but looking at the documentation (https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engin…) it seems that oVirt is not compatible with our CPU Intel Xeon Silver 4410Y 12C 150 W 2 .0 GHz processor? Can you help us?

6 6

Start VM with option -machine smm=off
by Kalil de A. Carvalho 16 Jul '24

16 Jul '24

Hello all. I'm trying to workaround the problem reported here: https://gitlab.com/qemu-project/qemu/-/issues/1198 but I did not find out how to start up the VM with the option -machine smm=off like sead on the lsit above. I guess that it is possible to run the command using the qemu command but I think that I will lose the management of it. It is possible to startup up a VM with this option using the oVirt GUI ou virsh? Best regards -- Atenciosamente, Kalil de A. Carvalho

3 2

New oVirt release ???
by Diggy 15 Jul '24

15 Jul '24

Any movement towards a new oVirt release now that CentOS Stream 8 is officially at EOL and the current engine is based on it? Do I see oVirt v4.6 in my near future? I'm looking for a reason to build a fresh oVirt environment and migrate our 100+ VMs to it. :) ---

6 10

engine-setup fails: "Failed to execute stage 'Misc configuration': Command '/usr/bin/ovirt-aaa-jdbc-tool' failed to execute"
by brent.saner＠netfire.com 11 Jul '24

11 Jul '24

I can find no reason why this would be happening. AlmaLinux 9.4, oVirt 4.5.6, brand new/fresh cluster/install. From the log, these seem to be the only relevant lines: 2024-06-18 22:02:52,720+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.config.aaajdbc plugin.execute:918 execute-output: ('/usr/bin/ovirt-aaa-jdbc-tool', '--db-config=/etc/ovirt-engine/aaa/internal.properties', 'query', '--what= user', '--pattern=name=admin') stdout: 2024-06-18 22:02:52,720+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.config.aaajdbc plugin.execute:923 execute-output: ('/usr/bin/ovirt-aaa-jdbc-tool', '--db-config=/etc/ovirt-engine/aaa/internal.properties', 'query', '--what= user', '--pattern=name=admin') stderr: Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false Jun 18, 2024 10:02:52 PM org.ovirt.engine.extension.aaa.jdbc.binding.cli.Cli main SEVERE: Unexpected Exception invoking Cli: com/ongres/scram/common/stringprep/StringPreparation 2024-06-18 22:02:52,720+0000 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/config/aaajdbc.py", line 414, in _misc self._setupAdminUser() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/config/aaajdbc.py", line 298, in _setupAdminUser if not self._userExists( File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/config/aaajdbc.py", line 49, in _userExists rc, stdout, stderr = self.execute( File "/usr/lib/python3.9/site-packages/otopi/plugin.py", line 929, in execute raise RuntimeError( RuntimeError: Command '/usr/bin/ovirt-aaa-jdbc-tool' failed to execute 2024-06-18 22:02:52,721+0000 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Misc configuration': Command '/usr/bin/ovirt-aaa-jdbc-tool' failed to execute 2024-06-18 22:02:52,721+0000 DEBUG otopi.transaction transaction.abort:124 aborting 'DNF Transaction' Any ideas?

5 7

VM Migration Failed
by KSNull Zero 10 Jul '24

10 Jul '24

Running oVirt 4.4.5 VM cannot migrate between hosts. vdsm.log contains the following error: libvirt.libvirtError: operation failed: Failed to connect to remote libvirt URI qemu+tls://ovhost01.local/system: authentication failed: Failed to verify peer's certificate Certificates on hosts was renewed some time ago. How this issue can be fixed ? Thank you.

4 6

problem on dnf update
by g.vasilopoulos＠uoc.gr 09 Jul '24

09 Jul '24

Hi I tried dnf update today and got the error bellow. Is there a solution for this?: [root@*****~]# dnf update Last metadata expiration check: 3:42:36 ago on Mon 17 Jun 2024 08:47:59 AM EEST. Error: Problem 1: package python3-boto3-1.18.58-1.el9s.noarch from @System requires (python3.9dist(botocore) < 1.22 with python3.9dist(botocore) >= 1.21.58), but none of the providers can be installed - cannot install both python3-botocore-1.31.62-1.el9.noarch from appstream and python3-botocore-1.21.58-1.el9s.noarch from @System - cannot install both python3-botocore-1.21.58-1.el9s.noarch from ovirt-master-centos-stream-openstack-yoga-testing and python3-botocore-1.31.62-1.el9.noarch from appstream - cannot install the best update candidate for package python3-botocore-1.21.58-1.el9s.noarch - cannot install the best update candidate for package python3-boto3-1.18.58-1.el9s.noarch Problem 2: package python3-pyngus-2.3.0-8.el9s.noarch from @System requires python3.9dist(python-qpid-proton), but none of the providers can be installed - cannot install both python3-qpid-proton-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing and python3-qpid-proton-0.35.0-2.el9s.x86_64 from @System - cannot install both python3-qpid-proton-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing and python3-qpid-proton-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing - cannot install the best update candidate for package python3-qpid-proton-0.35.0-2.el9s.x86_64 - cannot install the best update candidate for package python3-pyngus-2.3.0-8.el9s.noarch Problem 3: package python3-oslo-messaging-12.13.3-1.el9s.noarch from @System requires python3-pyngus, but none of the providers can be installed - package python3-pyngus-2.3.0-8.el9s.noarch from @System requires python3.9dist(python-qpid-proton), but none of the providers can be installed - package python3-pyngus-2.3.0-8.el9s.noarch from ovirt-master-centos-stream-openstack-yoga-testing requires python3.9dist(python-qpid-proton), but none of the providers can be installed - package python3-qpid-proton-0.35.0-2.el9s.x86_64 from @System requires qpid-proton-c(x86-64) = 0.35.0-2.el9s, but none of the providers can be installed - package python3-qpid-proton-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing requires qpid-proton-c(x86-64) = 0.35.0-2.el9s, but none of the providers can be installed - cannot install both qpid-proton-c-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing and qpid-proton-c-0.35.0-2.el9s.x86_64 from @System - cannot install both qpid-proton-c-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing and qpid-proton-c-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing - cannot install the best update candidate for package qpid-proton-c-0.35.0-2.el9s.x86_64 - cannot install the best update candidate for package python3-oslo-messaging-12.13.3-1.el9s.noarch (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

2 2

Disk blocked
by Louis Barbonnais 03 Jul '24

03 Jul '24

Hello, I apologize, I am new to oVirt and I am lost. I have just installed oVirt on CentOS 9 with local storage. I am trying to add ISO images to my disk, but they are blocked. I cannot delete or unblock them. Could you please assist me?

2 6

Install the oVirt engine on CentOS 9 Stream. However, I encountered an error while enabling the Java package tool, pki-deps, and the PostgreSQL
by Sachendra Shukla 02 Jul '24

02 Jul '24

Hi All, I am trying to install the oVirt engine on CentOS 9 Stream. However, I encountered an error while enabling the Java package tool, pki-deps, and the PostgreSQL module. Below is the error message I received. Could anyone please assist with a resolution for this issue? [image: image.png] -- Regards, *Sachendra Shukla* IT Administrator Yagna iQ, Inc. and subsidiaries Email: Sachendra.shukla(a)yagnaiq.com <dnyanesh.tisge(a)yagnaiq.com> Website: https://yagnaiq.com Privacy Policy: https://www.yagnaiq.com/privacy-policy/ <https://www.linkedin.com/company/yagnaiq/mycompany/> <https://www.youtube.com/channel/UCeHXOpcUxWvOJO0aegD99Jg> This communication and any attachments may contain confidential information and/or Yagna iQ, Inc. copyright material. All unauthorized use, disclosure, or distribution is prohibited. If you are not the intended recipient, please notify Yagna iQ immediately by replying to the email and destroy all copies of this communication. This email has been scanned for all known viruses. The sender does not accept liability for any damage inflicted by viewing the content of this email.

2 1

Any plans on oVirt Major release with new feature?
by De Lee 28 Jun '24

28 Jun '24

Hi, I would like to know if there is any plans for major release with new feature for consider alternative of other hypervisor? I've been using the oracle ovirt for couple of years pretty good one. I would like know the future of oVirt as well along with feature plans.

9 10

How to re-enroll (or renew) host certificates for a single-host hosted-engine deployment?
by Derek Atkins 28 Jun '24

28 Jun '24

Hi, I've got a single-host hosted-engine deployment that I originally installed with 4.0 and have upgraded over the years to 4.3.10. I and some of my users have upgraded remote-viewer and now I get an error when I try to view the console of my VMs: (remote-viewer:8252): Spice-WARNING **: 11:30:41.806: ../subprojects/spice-common/common/ssl_verify.c:477:openssl_verify: Error in server certificate verification: CA signature digest algorithm too weak (num=68:depth0:/O=<My Org Name>/CN=<Host's Name>) I am 99.99% sure this is because the old certs use SHA1. I reran engine-setup on the engine and it asked me if I wanted to renew the PKI, and I answered yes. This replaced many[1] of the certificates in /etc/pki/ovirt-engine/certs on the engine, but it did not update the Host's certificate. All the documentation I've seen says that to refresh this certificate I need to put the host into maintenance mode and then re-enroll.. However I cannot do that, because this is a single-host system so I cannot put the host in local mode -- there is no place to migrate the VMs (let alone the Engine VM). So.... Is there a command-line way to re-enroll manually and update the host certs? Or some other way to get all the leftover certs renewed? Thanks, -derek [1] Not only did it not update the Host's cert, it did not update any of the vmconsole-proxy certs, nor the certs in /etc/pki/ovirt-vmconsole/, and obviously nothing in /etc/pki/ on the host itself. -- Derek Atkins 617-623-3745 derek(a)ihtfp.com www.ihtfp.com Computer and Internet Security Consultant

8 16

python-nmstate 2.2.27 and ovirt network setup
by Bill James 28 Jun '24

28 Jun '24

We have a ovirt-host-4.5.0-3.el9.x86_64 cluster. I just recently ran yum update and it upgraded python-nmstate from python3-libnmstate-2.0.0-2.el9.noarch to python3-libnmstate- 2.2.27-2.el9_4.x86_64. This broken ovirt's ability to update the network config: 2024-06-27 13:22:39,716-07 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (EE-ManagedThreadFa ctory-engine-Thread-24) [ea3bc347-156d-4631-a196-c93a9f79c6c1] Command 'HostSetupNetworksVDSCommand(HostName = ovirt-b2n.j2n oc.com, HostSetupNetworksVdsCommandParameters:{hostId='12cd7cbc-0f02-4474-aaa5-b29cde8b56a4', vds='Host[ovirt-b2n.j2noc.com, 12cd7cbc-0f02-4474-aaa5-b29cde8b56a4]', rollbackOnFailure='true', commitOnSuccess='true', connectivityTimeout='120', network s='[HostNetwork:{defaultRoute='true', bonding='false', networkName='ovirtmgmt', vdsmName='ovirtmgmt', nicName='eno12429', vl an='110', vmNetwork='false', stp='false', properties='[]', ipv4BootProtocol='DHCP', ipv4Address='null', ipv4Netmask='null', ipv4Gateway='null', ipv6BootProtocol='NONE', ipv6Address='null', ipv6Prefix='null', ipv6Gateway='null', nameServers='null'}] ', removedNetworks='[]', bonds='[]', removedBonds='[]', clusterSwitchType='LEGACY', managementNetworkChanged='true'})' execu tion failed: VDSGenericException: VDSErrorException: Failed to HostSetupNetworksVDS, error = Internal JSON-RPC error: {'reas on': "[Errno 2] No such file or directory: ' */usr/lib/python3.9/site-packages/libnmstate/VERSION*'"}, code = -32603 that VERSION file, along with many other files, are not in 2.2.27 version of python-nmstate rpm. My fix was to downgrade the rpm. dnf install python3-libnmstate-2.0.0-2.el9.noarch I'm sure that's not the best solution as I can no longer run dnf update. Ideas?

1 0

Re: 4.5.4 Hosted-Engine: change hosted-engine storage
by Novak, Sam 27 Jun '24

27 Jun '24

I'm in the midst of deploying a new EL9 hosted-engine for an existing cluster and it has been an absolute nightmare, and I haven't found any documentation or guidance to account for this type of scenario, which is odd, considering that the EOL for Cent 8 was announced a while ago. I know this is all best effort type work, and I'm very appreciative of that effort, but it's really making me re-think my use case unfortunately. * Sam

1 0

Re: Failed to read or parse '/etc/pki/ovirt-engine/keys/engine.p12'
by Novak, Sam 27 Jun '24

27 Jun '24

Yeah I has to convert all of my P12's to use AES cd /etc/pki/ovirt-engine/keys/ for E in $(ls *.p12); do openssl pkcs12 -in $E -out $E.key -nocerts -nodes -passin file:pass.txt openssl pkcs12 -in $E -out $E.crt -nokeys -nodes -passin file:pass.txt openssl pkcs12 -in ./$E.crt -inkey ./$E.key -export -out $E.test.p12 -keypbe aes-256-cbc -certpbe aes-256-cbc -passin file:pass.txt done You'll also need to make sure you set the file owners and permissions like the original files.

1 0

Re: [ovirt-announce] Re: Reminder: CentOS Stream 8 is now EOL
by Sandro Bonazzola 27 Jun '24

27 Jun '24

Sadly I have no procedure ready for it and no time for working on it. My best advice would be to migrate from a hosted engine on el8 to a stand alone engine on el9 by installing a fresh centos stream 9 engine and re-importing the backup there. Il giorno gio 27 giu 2024 alle ore 12:01 <trockey(a)uw.edu> ha scritto: > Hi Sanbro, > I have 3 production oVirt clusters running and I missed upgrading HE > before May 31, 2024. If I am reading everything that you stated correctly I > will need to point HE CentOS Stream release 8 to vault.centos.org and > then upgrade to CentOS Stream 9. > Do you have the procedures for taking a HE CentOS Stream release 8 pointed > at vault.contos.org and upgrading it to CentOS Stream 9? > _______________________________________________ > Announce mailing list -- announce(a)ovirt.org > To unsubscribe send an email to announce-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/announce@ovirt.org/message/M5HSQFLZLF… > -- Sandro Bonazzola

1 0

Problem importing storage domain from oVirt 4.3.10 to 4.5.5
by Sumit Basu 26 Jun '24

26 Jun '24

Hi, I want to import a FC storage domain from an oVirt 4.3.10 setup to a fresh installed oVirt 4.5.5. I could move domain to maintenance, detach, remove from 4.3.10 and import with activate option to 4.5.5 for one FC LUN fine. When i tried for the second FC lun - during import,activate i get "Error while executing action Attach Storage Domain: Internal Engine Error" and in engine.log i get " Query 'GetUnregisteredDisksQuery' failed: null', and on the standalone engine, i get :- 2024-06-26 07:15:07,277+05 ERROR [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-102) [] An error occurred while fetching unregistered disks from Storage Domain id 'a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429' 2024-06-26 07:15:07,277+05 ERROR [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-102) [] Command 'org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand' failed: Failed to retrieve unregistered disks 2024-06-26 07:15:07,277+05 ERROR [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-102) [] Exception: java.lang.RuntimeException: Failed to retrieve unregistered disks I have checked using "Scan Disk" on the FC lun before exporting from 4.3.10 and there were no floating disks. I have checked if any of the VM's on the domain have any of their disks on any other storage domain - there are none. On the host used for importing the domain, i get :- 2024-06-26 07:15:04,829+0530 INFO (jsonrpc/5) [storage.hba] Scanning FC devices (hba:42) 2024-06-26 07:15:04,938+0530 INFO (periodic/0) [vdsm.api] START repoStats(domains=()) from=internal, task_id=9f03d412-56a7-4f3f-85b6-c3fd72a68817 (api:31) 2024-06-26 07:15:04,938+0530 INFO (periodic/0) [vdsm.api] FINISH repoStats return={'7c9e748c-442b-48d0-9b35-a769d349c73b': {'code': 0, 'lastCheck': '3.7', 'delay': '0.000974057', 'valid': True, 'version': 0, 'acquired': True, 'actual': True}, 'a589fe14-f40a-4d67-afcd-ec74b07009cf': {'code': 0, 'lastCheck': '3.7', 'delay': '0.000501601', 'valid': True, 'version': 0, 'acquired': True, 'actual': True}, '6b625ecb-1cd1-43c5-b533-32000cd050ec': {'code': 0, 'lastCheck': '3.7', 'delay': '0.000570869', 'valid': True, 'version': 5, 'acquired': True, 'actual': True}} from=internal, task_id=9f03d412-56a7-4f3f-85b6-c3fd72a68817 (api:37) 2024-06-26 07:15:04,968+0530 INFO (jsonrpc/5) [storage.hba] Scanning FC devices: 0.14 seconds (utils:373) 2024-06-26 07:15:04,968+0530 INFO (jsonrpc/5) [storage.multipath] Waiting until multipathd is ready (multipath:95) 2024-06-26 07:15:07,003+0530 INFO (jsonrpc/5) [storage.multipath] Waited 2.04 seconds for multipathd (tries=2, ready=2) (multipath:120) 2024-06-26 07:15:07,003+0530 INFO (jsonrpc/5) [storage.multipath] Resizing multipath devices (multipath:223) 2024-06-26 07:15:07,014+0530 INFO (jsonrpc/5) [storage.multipath] Resizing multipath devices: 0.01 seconds (utils:373) 2024-06-26 07:15:07,014+0530 INFO (jsonrpc/5) [storage.storagedomaincache] Refreshing storage domain cache: 2.60 seconds (utils:373) 2024-06-26 07:15:07,263+0530 INFO (jsonrpc/5) [storage.volumemanifest] Creating image directory '/rhev/data-center/mnt/blockSD/a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429/images/f054c394-2b49-4087-9e9d-0490b23e34e4' (blockVolume:106) 2024-06-26 07:15:07,263+0530 ERROR (jsonrpc/5) [storage.volumemanifest] Unexpected error (blockVolume:110) Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/vdsm/storage/blockVolume.py", line 108, in validateImagePath os.mkdir(imageDir, 0o755) FileNotFoundError: [Errno 2] No such file or directory: '/rhev/data-center/mnt/blockSD/a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429/images/f054c394-2b49-4087-9e9d-0490b23e34e4' 2024-06-26 07:15:07,263+0530 INFO (jsonrpc/5) [vdsm.api] FINISH prepareImage error=Image path does not exist or cannot be accessed/created: ('/rhev/data-center/mnt/blockSD/a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429/images/f054c394-2b49-4087-9e9d-0490b23e34e4',) from=::ffff:10.10.99.100,51116, flow_id=872d7930-e487-4fe4-8e0a-599074105d7b, task_id=523690f8-24b3-4f1f-801e-8391ebb087a2 (api:35) 2024-06-26 07:15:07,263+0530 ERROR (jsonrpc/5) [storage.taskmanager.task] (Task='523690f8-24b3-4f1f-801e-8391ebb087a2') Unexpected error (task:860) Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/vdsm/storage/blockVolume.py", line 108, in validateImagePath os.mkdir(imageDir, 0o755) FileNotFoundError: [Errno 2] No such file or directory: '/rhev/data-center/mnt/blockSD/a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429/images/f054c394-2b49-4087-9e9d-0490b23e34e4' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/vdsm/storage/task.py", line 867, in _run return fn(*args, **kargs) File "<decorator-gen-169>", line 2, in prepareImage File "/usr/lib/python3.9/site-packages/vdsm/common/api.py", line 33, in method ret = func(*args, **kwargs) File "/usr/lib/python3.9/site-packages/vdsm/storage/hsm.py", line 2958, in prepareImage legality = dom.produceVolume(imgUUID, volUUID).getLegality() File "/usr/lib/python3.9/site-packages/vdsm/storage/sd.py", line 1188, in produceVolume return self.getVolumeClass()(self.mountpoint, self.sdUUID, imgUUID, File "/usr/lib/python3.9/site-packages/vdsm/storage/volume.py", line 881, in __init__ self._manifest = self.manifestClass(repoPath, sdUUID, imgUUID, volUUID) File "/usr/lib/python3.9/site-packages/vdsm/storage/blockVolume.py", line 40, in __init__ volume.VolumeManifest.__init__(self, repoPath, sdUUID, imgUUID, File "/usr/lib/python3.9/site-packages/vdsm/storage/volume.py", line 67, in __init__ self.validate() File "/usr/lib/python3.9/site-packages/vdsm/storage/blockVolume.py", line 135, in validate volume.VolumeManifest.validate(self) File "/usr/lib/python3.9/site-packages/vdsm/storage/volume.py", line 99, in validate self.validateImagePath() File "/usr/lib/python3.9/site-packages/vdsm/storage/blockVolume.py", line 111, in validateImagePath raise se.ImagePathError(imageDir) vdsm.storage.exception.ImagePathError: Image path does not exist or cannot be accessed/created: ('/rhev/data-center/mnt/blockSD/a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429/images/f054c394-2b49-4087-9e9d-0490b23e34e4',) 2024-06-26 07:15:07,263+0530 INFO (jsonrpc/5) [storage.taskmanager.task] (Task='523690f8-24b3-4f1f-801e-8391ebb087a2') aborting: Task is aborted: "value=Image path does not exist or cannot be accessed/created: ('/rhev/data-center/mnt/blockSD/a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429/images/f054c394-2b49-4087-9e9d-0490b23e34e4',) abortedcode=254" (task:1165) 2024-06-26 07:15:07,264+0530 ERROR (jsonrpc/5) [storage.dispatcher] FINISH prepareImage error=Image path does not exist or cannot be accessed/created: ('/rhev/data-center/mnt/blockSD/a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429/images/f054c394-2b49-4087-9e9d-0490b23e34e4',) (dispatcher:66) 2024-06-26 07:15:07,264+0530 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call Image.prepare failed (error 254) in 2.85 seconds (__init__:300) Any help will be useful, we are moving from 4.3.10 on IBM servers and storage to 4.5.5 on DELL servers and storage Regards Sumit Basu

1 0

4.5.4 with Ceph only storage
by Maurice Burrows 25 Jun '24

25 Jun '24

Hey ... A long story short ... I have an existing Red Hat Virt / Gluster hyperconverged solution that I am moving away from. I have an existing Ceph cluster that I primarily use for OpenStack and a small requirement for S3 via RGW. I'm planning to build a new oVirt 4.5.4 cluster on RHEL9 using Ceph for all storage requirements. I've read many online articles on oVirt and Ceph, and they all seem to use the Ceph iSCSI gateway, which is now in maintenance, so I'm not real keen to commit to iSCSI. So my question is, IS there any reason I cannot use CephFS for both hosted-engine and as a data storage domain? I'm currently running Ceph Pacific FWIW. Cheers

5 10

After restoring the failed host and synchronizing the data, it prompts that there are unsynchronized items
by ziyi Liu 25 Jun '24

25 Jun '24

gluster volume info Volume Name: data Type: Replicate Number of Bricks: 1 x (2 + 1) = 3 Bricks: Brick1: node-gfs1:/gluster_bricks/data/data1 Brick2: node-gfs2:/gluster_bricks/data/data1 Brick3: node-gfs3:/gluster_bricks/data/data1 (arbiter) gluster volume heal data info Number of entries: 39 /var/log/glusterfs/glustershd.log The log appears client-rpc-fops_v2.c:785:client4_0_fsync_cbk] 0-data-client-0: remote operation failed. [{errno=5}, {error=Input/output error}] How should I solve these unrepaired entries

2 2

Error importing OVA on Ovirt-4.5.4 - no value for $TERM is defined
by raulmevi2＠hotmail.com 21 Jun '24

21 Jun '24

Hello, I'm facing an issue where, in a new fresh installed Oracle OLVM - Ovirt 4.5.4, self-hosted engine with NFS shared storage. That an .OVA file cannot be imported. Steps to reproduce: - Created test virtual machine in an NFS storage domain, installed it, allright working fine. - Shutdown test VM - Export test VM to a purposedly created directory /home/vdsm, whose owner is vdsm:kvm with full permissions. - Export .OVA file concludes successfully and the file is created at that location Then, in the exact same server, same datacenter. - Rename source VM so it doesn't conflict because the same name (same result if I delete the source VM) - try to import the .OVA. using the GUI. It finds successfully the file at the specified location and begins the procedure -# up to a given point, it fails without more indications at the web GUI. No more info at the "events" than "Failed to import vm Test to Datacenter". Fiddling into the logs, I was able to find in the hosted-engine VM, at /var/log/ovirt-engine/ova the log that goes by "ovirt-ova-external-data-ansible-DATE-HostFQDN-uuid.log" an error that specifiies stdout_lines" : [ "tput: No value for $TERM and no -T specified", "tput: No value for $TERM and no -T specified", "tput: No value for $TERM and no -T specified" I tinkered with the ansible role that calls a python script called "get_ova_data.py" (located at /usr/share/ovirt-engine/ansible-runner-service-project/project/roles-/ovirt-ova-external-data/) I tried to define the variable TERM into null or into xterm but then it fails in another manner complaining about that variable. By surfing the webs, it seems something calls "tput" like if it was in console mode but then it breaks. Can I have some help with this, please? Thanks

1 0

HE deployment on FC (fibre-channel) disk fails at 99% completed at final "hosted-engine --reinitialize-lockspace --force"
by Jeffrey Slapp 21 Jun '24

21 Jun '24

This identical to many others who have encountered this issue, yet nothing definitive has been suggested. The entire HE deployment nearly finishes, but after the copy of the HE VM to the shared disk, shortly after that I reach the "initialize lockspace" section and the following error occurs: 20083 2024-06-19 13:24:01,777-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'changed': True, 'stdout': '', 'stderr': 'Traceback (most recent call last):\n File "/usr/lib64/python3.9/runpy.py", line 197, in _run_module_as_main\n return _run_ code(code, main_globals, None,\n File "/usr/lib64/python3.9/runpy.py", line 87, in _run_code\n exec(code, run_globals)\n File "/usr/lib/p ython3.9/site-packages/ovirt_hosted_engine_setup/reinitialize_lockspace.py", line 30, in <module>\n ha_cli.reset_lockspace(force)\n File " /usr/lib/python3.9/site-packages/ovirt_hosted_engine_ha/client/client.py", line 286, in reset_lockspace\n stats = broker.get_stats_from_sto rage()\n File "/usr/lib/python3.9/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 148, in get_stats_from_storage\n result = self._proxy.get_stats()\n File "/usr/lib64/python3.9/xmlrpc/client.py", line 1122, in __call__\n ret urn self.__send(self.__name, args)\n File "/usr/lib64/python3.9/xmlrpc/client.py", line 1464, in __request\n response = self.__transport.request(\n File "/usr/lib64/python3.9/ xmlrpc/client.py", line 1166, in request\n return self.single_request(host, handler, request_body, verbose)\n File "/usr/lib64/python3.9/x mlrpc/client.py", line 1178, in single_request\n http_conn = self.send_request(host, handler, request_body, verbose)\n File "/usr/lib64/py thon3.9/xmlrpc/client.py", line 1291, in send_request\n self.send_content(connection, request_body)\n File "/usr/lib64/python3.9/xmlrpc/cl ient.py", line 1321, in send_content\n connection.endheaders(request_body)\n File "/usr/lib64/python3.9/http/client.py", line 1280, in end headers\n self._send_output(message_body, encode_chunked=encode_chunked)\n File "/usr/lib64/python3.9/http/client.py", line 1040, in _send _output\n self.send(msg)\n File "/usr/lib64/python3.9/http/cl ient.py", line 980, in send\n self.connect()\n File "/usr/lib/python3.9/s ite-packages/ovirt_hosted_engine_ha/lib/unixrpc.py", line 76, in connect\n self.sock.connect(base64.b16decode(self.host))\nFileNotFoundErro r: [Errno 2] No such file or directory', 'rc': 1, 'cmd': ['hosted-engine', '--reinitialize-lockspace', '--force'], 'start': '2024-06-19 13:24: 01.438386', 'end': '2024-06-19 13:24:01.618227', 'delta': '0:00:00.179841', 'msg': 'non-zero return code', 'invocation': {'module_args': {'_ra w_params': 'hosted-engine --reinitialize-lockspace --force', '_uses_shell': False, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv' : None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': [], 'stderr_lines': ['Traceback (most recent call last):', ' File "/usr/lib64/python3.9/runpy.py", line 197, in _run_module_as_main', ' return _run_code(code, main_global s, None,', ' File "/usr/l ib64/python3.9/runpy.py", line 87, in _run_code', ' exec(code, run_globals)', ' File "/usr/lib/python3.9/site-pa ckages/ovirt_hosted_engine_setup/reinitialize_lockspace.py", line 30, in <module>', ' ha_cli.reset_lockspace(force)', ' File "/usr/lib/pyt hon3.9/site-packages/ovirt_hosted_engine_ha/client/client.py", line 286, in reset_lockspace', ' stats = broker.get_stats_from_storage()', ' File "/usr/lib/python3.9/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 148, in get_stats_from_storage', ' result = self._ proxy.get_stats()', ' File "/usr/lib64/python3.9/xmlrpc/client.py", line 1122, in __call__', ' return self.__send(self.__name, args)', ' File "/usr/lib64/python3.9/xmlrpc/client.py", line 1464, in __request', ' response = self.__transport.request(', ' File "/usr/lib64/python 3.9/xmlrpc/client.py", line 1166, in request', ' return self.single_request(host, handler, request_body, verbose)', ' File "/usr/li b64/pyt hon3.9/xmlrpc/client.py", line 1178, in single_request', ' http_conn = self.send_request(host, handler, request_body, verbose)', ' File "/ usr/lib64/python3.9/xmlrpc/client.py", line 1291, in send_request', ' self.send_content(connection, request_body)', ' File "/usr/lib64/pyt hon3.9/xmlrpc/client.py", line 1321, in send_content', ' connection.endheaders(request_body)', ' File "/usr/lib64/python3.9/http/client.py ", line 1280, in endheaders', ' self._send_output(message_body, encode_chunked=encode_chunked)', ' File "/usr/lib64/python3.9/http/client. py", line 1040, in _send_output', ' self.send(msg)', ' File "/usr/lib64/python3.9/http/client.py", line 980, in send', ' self.connect() ', ' File "/usr/lib/python3.9/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py", line 76, in connect', ' self.sock.connect(base64.b16de code(self.host))', 'FileNotFoundError: [Errno 2] No such file or directory'], '_ansible_no_log': False, 'attempts': 5} No errors in /var/log/messages or /var/log/sanlock.log. I have this working with iSCSI on another storage system, but can't seem to get this to work on FC. I have read that the sector sizes could possible cause this. On my iSCSI system I have [PHY-SEC:LOG-SEC] as [512:512] but on my FC system I have [4096:512]. Hoping that someone can confirm whether this is the issue or not. Interestingly all previous "initialize lockspace" phases of the install are fine, it just appears to be this final one.

2 1

New host cannot connect to master domain
by ovirt＠kirschke.de 21 Jun '24

21 Jun '24

Hi, i just installed a new host, which cannot connect to the master domain. The domain is an iscsi device on a nas, and ovirt is actually fine with it, other hosts have no problem. I'sure , I#m just overlooking something. What I see in the log is: 024-04-16 11:10:06,320-0400 INFO (jsonrpc/3) [storage.storagepoolmemorybackend] new storage pool master version 302 and domains map {'6f018fbd-de93-4c56-880d-8ede2aad2674': 'Active', '2c870e06-6c70-45ec-b665-ce29408c8a8e': 'Active', 'a154 96dc-c241-4658-af9d-0dfe11783916': 'Active', '41012bfb-b802-4092-b699-7f5284d95c8e': 'Active'} (spbackends:417) 2024-04-16 11:10:06,320-0400 INFO (jsonrpc/3) [storage.storagepool] updating pool 5836aaac-0030-0064-024d-0000000002e4 backend from type NoneType instance 0x7f10d667fb70 to type StoragePoolMemoryBackend instance 0x7f10702d7408 (sp:149) 2024-04-16 11:10:06,320-0400 INFO (jsonrpc/3) [storage.storagepool] Connect host #2 to the storage pool 5836aaac-0030-0064-024d-0000000002e4 with master domain: a15496dc-c241-4658-af9d-0dfe11783916 (ver = 302) (sp:699) 2024-04-16 11:10:06,320-0400 INFO (jsonrpc/3) [storage.storagedomaincache] Invalidating storage domain cache (sdc:57) 2024-04-16 11:10:06,320-0400 INFO (jsonrpc/3) [storage.storagedomaincache] Clearing storage domain cache (sdc:182) 2024-04-16 11:10:06,320-0400 INFO (jsonrpc/3) [storage.storagedomaincache] Refreshing storage domain cache (resize=True) (sdc:63) 2024-04-16 11:10:06,320-0400 INFO (jsonrpc/3) [storage.iscsi] Scanning iSCSI devices (iscsi:445) 2024-04-16 11:10:06,456-0400 INFO (jsonrpc/3) [storage.iscsi] Scanning iSCSI devices: 0.14 seconds (utils:373) 2024-04-16 11:10:06,456-0400 INFO (jsonrpc/3) [storage.hba] Scanning FC devices (hba:42) 2024-04-16 11:10:06,481-0400 INFO (jsonrpc/3) [storage.hba] Scanning FC devices: 0.03 seconds (utils:373) 2024-04-16 11:10:06,481-0400 INFO (jsonrpc/3) [storage.multipath] Waiting until multipathd is ready (multipath:95) 2024-04-16 11:10:08,498-0400 INFO (jsonrpc/3) [storage.multipath] Waited 2.02 seconds for multipathd (tries=2, ready=2) (multipath:122) 2024-04-16 11:10:08,498-0400 INFO (jsonrpc/3) [storage.multipath] Resizing multipath devices (multipath:223) 2024-04-16 11:10:08,499-0400 INFO (jsonrpc/3) [storage.multipath] Resizing multipath devices: 0.00 seconds (utils:373) 2024-04-16 11:10:08,499-0400 INFO (jsonrpc/3) [storage.storagedomaincache] Refreshing storage domain cache: 2.18 seconds (utils:373) 2024-04-16 11:10:08,499-0400 INFO (jsonrpc/3) [storage.storagedomaincache] Looking up domain a15496dc-c241-4658-af9d-0dfe11783916 (sdc:154) 2024-04-16 11:10:08,536-0400 INFO (jsonrpc/3) [storage.storagedomaincache] Looking up domain a15496dc-c241-4658-af9d-0dfe11783916: 0.04 seconds (utils:373) 2024-04-16 11:10:08,537-0400 INFO (jsonrpc/3) [vdsm.api] FINISH connectStoragePool error=Cannot find master domain: 'spUUID=5836aaac-0030-0064-024d-0000000002e4, msdUUID=a15496dc-c241-4658-af9d-0dfe11783916' from=::ffff:10.2.0.4,44914, flo w_id=44d9e674, task_id=32f0ea2a-044b-4a81-a12e-a269e59a802b (api:35) 2024-04-16 11:10:08,537-0400 ERROR (jsonrpc/3) [storage.taskmanager.task] (Task='32f0ea2a-044b-4a81-a12e-a269e59a802b') Unexpected error (task:860) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/sp.py", line 1550, in setMasterDomain domain = sdCache.produce(msdUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 98, in produce domain.getRealDomain() File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 34, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 122, in _realProduce domain = self._findDomain(sdUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 139, in _findDomain return findMethod(sdUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 169, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) vdsm.storage.exception.StorageDomainDoesNotExist: Storage domain does not exist: ('a15496dc-c241-4658-af9d-0dfe11783916',) During handling of the above exception, another exception occurred: .... The domain a15496dc-c241-4658-af9d-0dfe11783916 definitely exist, and works on other systems. THe new host can acces the iscsi targets, and i am able to log into them. Any one who knows, which blinder I have to remove, so I see the actual problem? Thanks and best regards Steffen

1 1

Admin interface broken
by ovirt＠kirschke.de 21 Jun '24

21 Jun '24

Hi i tried to migrate my ovirt engine form a centos 8 to a 9 machine. So, I made a backup, created and configured a new machine, stopped the old one, started the new one with identical network configuration, restored the backup and tried engine-setup to set up the new site, exping it to work. It did not, but I thought, no prob, I still have my old one. Now, going back to the old mache, when logging into Admin Portal, I get error messages: - Error while executing action: A Request to the Server failed: Type 'org.ovirt.engine.core.common.queries.QueryType' was not assignable to 'com.google.gwt.user.client.rpc.IsSerializable' and did not have a custom field serializer. For security purposes, this type will not be deserialized. - Error while executing query: null Each in a Box, which I clicked away getting the messages toggeling. After a while, the abckground of the admin Portal's dashboad is becomes visible, but remains empty, with the 'loading' spinner. In the serverlog I only see the following exveption: Caused by: com.google.gwt.user.client.rpc.SerializationException: Type 'org.ovirt.engine.core.common.queries.QueryType' was not assignable to 'com.google.gwt.user.client.rpc.IsSerializable' and did not have a custom field serializer. For security purposes, this type will not be deserialized. at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.impl.LegacySerializationPolicy.validateDeserialize(LegacySerializationPolicy.java:128) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deserialize(ServerSerializationStreamReader.java:676) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.readObject(ServerSerializationStreamReader.java:592) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.core.java.util.Collection_ServerCustomFieldSerializerBase.deserialize(Collection_ServerCustomFieldSerializerBase.java:38) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.core.java.util.ArrayList_ServerCustomFieldSerializer.deserialize(ArrayList_ServerCustomFieldSerializer.java:40) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.core.java.util.ArrayList_ServerCustomFieldSerializer.deserializeInstance(ArrayList_ServerCustomFieldSerializer.java:54) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.core.java.util.ArrayList_ServerCustomFieldSerializer.deserializeInstance(ArrayList_ServerCustomFieldSerializer.java:33) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deserializeImpl(ServerSerializationStreamReader.java:887) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deserialize(ServerSerializationStreamReader.java:687) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.readObject(ServerSerializationStreamReader.java:592) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader$ValueReader$8.readValue(ServerSerializationStreamReader.java:149) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deserializeValue(ServerSerializationStreamReader.java:434) at deployment.engine.ear.webadmin.war//com.google.gwt.user.server.rpc.RPC.decodeRequest(RPC.java:312) ... 64 more Which , of course I do not understand, what it tries to tell me. The VM-Portal is still reachable, and seems to work. Has anybody had an effect like that, or, even better, an idea, what I am doing wrong and how I can fix that, or where I can look to find the main cause for the bahaviour- Forgot to mention: Desperate, as I am, I also tried to upgrade to 4.5.7-master, which worked without any problem or warning, but the effect is still the same. Thanks and best regards Steffen

1 0

Ovirt4.5 installation failure on Rocky 8
by 盛家杰 20 Jun '24

20 Jun '24

Hello Ovit Devs, I am new to ovirt and am trying to install Ovirt4.5 on Rocky8 machine, and I am stuck at the first step, enable ovirt engine repo. 1. I follow the manual to do some yum repo configuration staff, with bash code in "Rocky" part , https://www.ovirt.org/download/install_on_rhel.html # On Rocky there's an issue with centos-release-nfv package from extras dnf install -y dnf-plugins-core dnf config-manager --set-disabled extras 2. I try to install ovirt4.5 with "dnf install -y centos-release-ovirt45", but it fails with "unable to find a match". I find centos-release-ovirt45 is listed in extras repo and extras repo is disabled. If extras repo needs to be disabled, how can I install centos-release-ovirt45? Any suggestions would be highly appreciated! Jiajie

1 0

How to access the ovirt node individually?
by De Lee 19 Jun '24

19 Jun '24

Hi, I've installed the ovirt manager on top of the oVirt node. For some reason the node went to offline and unable to start the ovrit manager. Do we have option to enable the auto start of the ovrit manager and can I able to connect the console of the ovirt node try to power on the VM?

2 1

Re: ovirt keycloak intergration user search not working
by Kevin Köllmann 19 Jun '24

19 Jun '24

We also noticed this and are just adding them by knowing the full username. A functioning search would be helpful though.

1 0

Please tell me how to deal with the error
by d_hashima＠sagaidc.co.jp 19 Jun '24

19 Jun '24

I'm currently installing oVirt45 self-host on RHEL9. Installation fails due to the following error. Could you please give me some advice? error contents: "Failed to download metadata for repo 'centos-ceph-pacific': Cannot prepare internal mirrorlist: No URLs in mirrorlist"

3 3

Add new host fail and reinstall fail
by max.tseng＠extremedata.com.tw 19 Jun '24

19 Jun '24

Hi Sir, I want crate new host server , always get error message 2024-06-19 14:52:59,440+08 WARN [org.apache.sshd.client.session.ClientConnectionService] (sshd-SshClient[79ddc832]-nio2-thread-8) globalRequest(ClientConnectionService[ClientSessionImpl[root@/172.16.1.40:22]])[hostkeys-00@openssh.com, want-reply=false] failed (SshException) to process: EdDSA provider not supported

1 0

Out-of-sync - Host Network's configurations differ from DC
by munnadawood＠gmail.com 18 Jun '24

18 Jun '24

Hello Team, We had a power outage last week and we started observing the error on our oVirt cluster, where all the hosts went out-of-sync. When I select my ovirtmgmt interface it shows the out-of-sync symbol and shows IPv4 gateway ( Host - Null, DC - 10.xx..xx.xx) Same with my VM traffic network, it shows the out-of-sync symbol and shows IPv4 gateway ( Host - Null, DC - 10.xx..xx.xx) Please help me with my troubleshooting as we lost access to VM's access after our power outage. Thanks, Dawood.

2 2

Deployment Failure with oVirt Hosted Engine on CentOS Stream 9
by khaltarabien＠gmail.com 17 Jun '24

17 Jun '24

Hello, I've encountered a failure while trying to deploy the oVirt Hosted Engine using the oVirt Node NG Installer on a system running CentOS Stream 9. Here are the details: Environment: OS: CentOS Stream 9 (oVirt Node 4.5.5) oVirt Version: 4.5.5 Installer ISO: oVirt Node NG Installer 4.5.5-2023113015 for el9 Issue: During the deployment of the hosted engine, the process failed with several error messages, notably failing to download metadata for the 'centos-ceph-pacific' repository due to no URLs in the mirrorlist, and a failure deploying the engine on the local VM. Error Messages: Failed to download metadata for repo 'centos-ceph-pacific': Cannot prepare internal mirrorlist: No URLs in mirrorlist There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch. Deprecation warning for the Python crypt module. Steps Taken: Attempted deployment using the hosted-engine --deploy command. Used the specified installer ISO. Seeking Help: Has anyone faced similar issues, or does anyone have suggestions on how to resolve the mirrorlist problem and the deployment issue? Any help or guidance would be greatly appreciated!ERY, status: NOERROR, id: 52241 2024-06-13 00:07:19,621+0000 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost -> 192.168.222.192]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'centos-ceph-pacific': Cannot prepare internal mirrorlist: No URLs in mirrorlist", "rc": 1, "results": []} 2024-06-13 00:07:48,484+0000 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": false, "msg": "There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} 2024-06-13 00:07:49,088+0000 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:238 b'[DEPRECATION WARNING]: Encryption using the Python crypt module is deprecated. \n' 2024-06-13 00:07:49,088+0000 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:238 b'The Python crypt module is deprecated and will be removed from Python 3.13. \n' 2024-06-13 00:07:49,089+0000 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:238 b'Install the passlib library for continued encryption functionality. This \n' 2024-06-13 00:07:49,089+0000 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:238 b'feature will be removed in version 2.17. Deprecation warnings can be disabled \n' 2024-06-13 00:07:49,090+0000 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:238 b'by setting deprecation_warnings=False in ansible.cfg.\n' 2024-06-13 00:07:49,094+0000 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Closing up': Failed executing ansible-playbook 2024-06-13 00:08:11,089+0000 ERROR otopi.plugins.gr_he_common.core.misc misc._terminate:164 Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch.

3 4

problem on dnf update
by g.vasilopoulos＠uoc.gr 17 Jun '24

17 Jun '24

Hi I tried dnf update today and the result was [root@kmanage ~]# dnf update Last metadata expiration check: 3:42:36 ago on Mon 17 Jun 2024 08:47:59 AM EEST. Error: Problem 1: package python3-boto3-1.18.58-1.el9s.noarch from @System requires (python3.9dist(botocore) < 1.22 with python3.9dist(botocore) >= 1.21.58), but none of the providers can be installed - cannot install both python3-botocore-1.31.62-1.el9.noarch from appstream and python3-botocore-1.21.58-1.el9s.noarch from @System - cannot install both python3-botocore-1.21.58-1.el9s.noarch from ovirt-master-centos-stream-openstack-yoga-testing and python3-botocore-1.31.62-1.el9.noarch from appstream - cannot install the best update candidate for package python3-botocore-1.21.58-1.el9s.noarch - cannot install the best update candidate for package python3-boto3-1.18.58-1.el9s.noarch Problem 2: package python3-pyngus-2.3.0-8.el9s.noarch from @System requires python3.9dist(python-qpid-proton), but none of the providers can be installed - cannot install both python3-qpid-proton-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing and python3-qpid-proton-0.35.0-2.el9s.x86_64 from @System - cannot install both python3-qpid-proton-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing and python3-qpid-proton-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing - cannot install the best update candidate for package python3-qpid-proton-0.35.0-2.el9s.x86_64 - cannot install the best update candidate for package python3-pyngus-2.3.0-8.el9s.noarch Problem 3: package python3-oslo-messaging-12.13.3-1.el9s.noarch from @System requires python3-pyngus, but none of the providers can be installed - package python3-pyngus-2.3.0-8.el9s.noarch from @System requires python3.9dist(python-qpid-proton), but none of the providers can be installed - package python3-pyngus-2.3.0-8.el9s.noarch from ovirt-master-centos-stream-openstack-yoga-testing requires python3.9dist(python-qpid-proton), but none of the providers can be installed - package python3-qpid-proton-0.35.0-2.el9s.x86_64 from @System requires qpid-proton-c(x86-64) = 0.35.0-2.el9s, but none of the providers can be installed - package python3-qpid-proton-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing requires qpid-proton-c(x86-64) = 0.35.0-2.el9s, but none of the providers can be installed - cannot install both qpid-proton-c-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing and qpid-proton-c-0.35.0-2.el9s.x86_64 from @System - cannot install both qpid-proton-c-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing and qpid-proton-c-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing - cannot install the best update candidate for package qpid-proton-c-0.35.0-2.el9s.x86_64 - cannot install the best update candidate for package python3-oslo-messaging-12.13.3-1.el9s.noarch (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

1 0

Incremental backup in Ovirt 4.5.7-el9 and 4.5.6 -el8 not working...
by rvks＠protonmail.com 15 Jun '24

15 Jun '24

Hi All, We are trying out ovirt (self-hosted engine) to replace Vmware and it's important to test the Incremental backup but so far we had no luck to make it work. Full backup working fine but subsequent incrementals are not happening, instead it's doing full backup. Using REST api but we can't enable incremental on disk ( DiskBackupMode enum). Any tips and help appreciated..... thanks, rvks

1 0

oVirt engine installation
by andremi001＠gmail.com 14 Jun '24

14 Jun '24

Hi, I'm trying to deploy oVirt engine self hosted, from my Centos 9 stream node, but when I try to run the deploy I always got the error: "FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'centos-ceph-pacific': Cannot prepare internal mirrorlist: No URLs in mirrorlist", "rc": 1, "results": []}" I thinks it is correlated with the end of life of Centos 8 stream. How can I fix it?

2 1

oVirt 4.5.5 Fresh Installation
by Clemilton 14 Jun '24

14 Jun '24

Hope this helps the project to get better; [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "hostname 'host01' doesn't uniquely match the interface 'eno1' selected for the management bridge; it matches also interface with IP ['fe80::5a8a:5aff:fe68:4981%2']. Please make sure that the hostname got from the interface for the management network resolves only there.\n"} - THIS IS NOT MENSIONED (AT LEAST I DIDNT SEE ANYWHERE) IN THE DOCUMENTATION. [ INFO ] TASK [ovirt.ovirt.engine_setup : Check if Engine health page is up] [ INFO ] ok: [localhost -> 192.168.222.43] - THIS IS NOT THE RIGHT IP ADDRESS. THIS NETWORK DOES NOT EXIST [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up] - 25 MINUTES WAITING... [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"} - COURSE! THE SCRIPT IGNORED THE IP ADDRESS I'VE PUT [ ERROR ] b'[DEPRECATION WARNING]: Encryption using the Python crypt module is deprecated. \n' [ ERROR ] b'The Python crypt module is deprecated and will be removed from Python 3.13. \n' [ ERROR ] b'Install the passlib library for continued encryption functionality. This \n' [ ERROR ] b'feature will be removed in version 2.17. Deprecation warnings can be disabled \n' [ ERROR ] b'by setting deprecation_warnings=False in ansible.cfg.\n' [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook

2 1

Reminder: CentOS Stream 8 is now EOL
by Sandro Bonazzola 13 Jun '24

13 Jun '24

Hi, just a reminder that CentOS Stream 8 reached its end of life at the end of last month on Friday, May 31, 2024. As it has been announced by CentOS project[1], all the CentOS Stream 8 repositories are going to be archived at vault.centos.org . Who didn't update yet to CentOS Stream 9 will probably hit several errors related to this archiving: you'll need to manually adjust the repository url to point to the new location at vault.centos.org. The archiving is going to happen today [2] with the decommissioning of the nodes used by the CentOS Community Build System used for oVirt builds for Stream 8 within the CentOS Virtualization SIG. At this point, the recommendation is to upgrade to CentOS Stream 9 (or derived) as soon as practical. For those who are pushing changes to the oVirt project, please note GitHub actions may start to fail on CentOS Stream 8 (and with that, the builds for oVirt Node and oVirt Appliance). It's up to you to decide if you want to change the config there to use a different el8 distribution for running the tests or just turn off el8 and rely only on CentOS Stream 9 tests. [1] https://lists.centos.org/hyperkitty/list/announce@lists.centos.org/thread/D… [2] https://lists.centos.org/hyperkitty/list/devel@lists.centos.org/thread/P3HD… -- Sandro Bonazzola

6 9

No valid authentication mechanism found
by Mathieu Valois 13 Jun '24

13 Jun '24

Hi everyone, we've configured oVirt 4.5.5 with KeyCloak OIDC using an LDAP (FreeIPA) backend. When we wish to login on the portal, i.e https://example.org/ovirt-engine, using the "Administration Portal" or login directly with the button in the upper-right corner, it works (we get redirected to keycloack and so on). However, if we first try to login by clicking on the "VM portal", it fails. We get redirected back to the portal having a "No valid authentication mechanism found" error, as seen on the following screenshot. Then, we're stuck until we clear the cache and cookies of the browser, even when clicking on "Admin portal". Backend logs only show this : 2024-06-04 11:56:24,319-04 ERROR [org.ovirt.engine.core.sso.service.SsoService] (default task-86) [] Aucun mécanisme d'authentification valide trouvé. which translates to the message seen on the screenshot. Do you get any lead to resolve such an issue? Thanks for your kind support, Mathieu Valois Ingénieur sécurité, systèmes et réseaux Bureau Caen : Quartier Kœnig - 153, rue Géraldine MOCK - 14760 Bretteville-sur-Odon Bureau Vitré : Zone de la baratière - 12, route de Domalain - 35500 Vitré 02 72 34 13 20 | https://teicee.com?pk_campaign=Email https://www.facebook.com/teicee https://www.linkedin.com/company/t-c-e

1 0

ovirt keycloak intergration user search not working
by g.vasilopoulos＠uoc.gr 13 Jun '24

13 Jun '24

Hello and thank you for all your efforts to provide such a quality software. I have followd the instructions from the blog https://blogs.ovirt.org/2019/01/federate-ovirt-engine-authentication-to-ope… and I managed to intergrate ovirt with keycloak partialy. I say partialy because I cannot execute a user search from the admin portal. I can add the user if I know his username say do a search with the full username like gvas(a)test.domain. The thing is in the admin portal when I perform a user search using internalkeycloack-authz whatever I write in the search returns as a result. It does not seem to matter if it is an existing user or not. If the user exists, then the user cal login and is granted the appropriate rights, but user search does not work . What should I look for?

1 0

Backup bug in latest version
by Giulio Casella 13 Jun '24

13 Jun '24

Hi, yesterday we upgraded engine: ovirt-engine-4.5.7-0.master.20240506114300.git0a1ba8203f.el8.noarch -> ovirt-engine-4.5.7-0.master.20240527152413.gited023e5e0a.el8.noarch Since then our backups (made by Storware backup and recovery, vprotect) are failing. It seems that engine tries to add backup twice, and db primary key constraint obviously fails. Find below a snippet from engine.log. The snapshot part of backup process is executed correctly (but snapshot named "Auto-generated for Backup VM" remains after failure). Also script /usr/share/doc/python3-ovirt-engine-sdk4/examples/backup_vm.py fails to finalize/terminate backup. Has anyone seen this and filed a bug on github? ------------------------------------------------------ 2024-06-13 10:36:47,481+02 INFO [org.ovirt.engine.core.bll.storage.backup.HybridBackupCommand] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Lock Acquired to object 'EngineLock:{exclusiveLocks='[09db7fdc-c4d3-4fbd-a50e-1b04de2b1341=DISK, 32f9b481-8431-4cbc-ad3e-bb226374e693=DISK]', sharedLocks=''}' 2024-06-13 10:36:47,535+02 INFO [org.ovirt.engine.core.bll.storage.backup.HybridBackupCommand] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Running command: HybridBackupCommand internal: false. Entities affected : ID: dc6d9b23-e2f7-4744-a633-d4e532ef190f Type: VMAction group BACKUP_DISK with role type ADMIN, ID: 09db7fdc-c4d3-4fbd-a50e-1b04de2b1341 Type: DiskAction group BACKUP_DISK with role type ADMIN, ID: 32f9b481-8431-4cbc-ad3e-bb226374e693 Type: DiskAction group BACKUP_DISK with role type ADMIN 2024-06-13 10:36:47,541+02 INFO [org.ovirt.engine.core.bll.storage.backup.HybridBackupCommand] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Created VmBackup entity 'd5bed8c5-f172-47c7-9827-5dda51490ee8' for VM 'dc6d9b23-e2f7-4744-a633-d4e532ef190f' 2024-06-13 10:36:47,596+02 INFO [org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Lock Acquired to object 'EngineLock:{exclusiveLocks='[dc6d9b23-e2f7-4744-a633-d4e532ef190f=VM]', sharedLocks=''}' 2024-06-13 10:36:47,640+02 INFO [org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Running command: CreateSnapshotForVmCommand internal: true. Entities affected : ID: dc6d9b23-e2f7-4744-a633-d4e532ef190f Type: VMAction group MANIPULATE_VM_SNAPSHOTS with role type USER 2024-06-13 10:36:47,668+02 INFO [org.ovirt.engine.core.bll.snapshots.CreateSnapshotDiskCommand] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Running command: CreateSnapshotDiskCommand internal: true. Entities affected : ID: dc6d9b23-e2f7-4744-a633-d4e532ef190f Type: VMAction group MANIPULATE_VM_SNAPSHOTS with role type USER 2024-06-13 10:36:47,731+02 INFO [org.ovirt.engine.core.bll.snapshots.CreateSnapshotCommand] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Running command: CreateSnapshotCommand internal: true. Entities affected : ID: 00000000-0000-0000-0000-000000000000 Type: Storage 2024-06-13 10:36:47,767+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] START, CreateVolumeVDSCommand( CreateVolumeVDSCommandParameters:{storagePoolId='42135536-980b-4ea9-ab66-b850ed8c1f2b', ignoreFailoverLimit='false', storageDomainId='459011cf-ebb6-46ff-831d-8ccfafd82c8a', imageGroupId='32f9b481-8431-4cbc-ad3e-bb226374e693', imageSizeInBytes='107374182400', volumeFormat='COW', newImageId='754b091f-eaa9-4fd8-afbf-1caa0e747eb6', imageType='Sparse', newImageDescription='', imageInitialSizeInBytes='0', imageId='06289dbc-fc0a-4d7b-bd13-92a2df199971', sourceImageGroupId='32f9b481-8431-4cbc-ad3e-bb226374e693', shouldAddBitmaps='false', legal='true', sequenceNumber='1', bitmap='bf62fab5-fb82-4c03-ac60-ddb9943c9f0d'}), log id: 128fa930 2024-06-13 10:36:47,883+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] FINISH, CreateVolumeVDSCommand, return: 754b091f-eaa9-4fd8-afbf-1caa0e747eb6, log id: 128fa930 2024-06-13 10:36:47,895+02 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] CommandAsyncTask::Adding CommandMultiAsyncTasks object for command '43b174d8-3b84-46a3-abe6-e825e9ce7c81' 2024-06-13 10:36:47,896+02 INFO [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] CommandMultiAsyncTasks::attachTask: Attaching task '86720608-b5bd-4a28-b7ee-b1a3507592aa' to command '43b174d8-3b84-46a3-abe6-e825e9ce7c81'. 2024-06-13 10:36:47,918+02 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Adding task '86720608-b5bd-4a28-b7ee-b1a3507592aa' (Parent Command 'CreateSnapshot', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling hasn't started yet.. 2024-06-13 10:36:47,947+02 INFO [org.ovirt.engine.core.bll.snapshots.CreateSnapshotCommand] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Running command: CreateSnapshotCommand internal: true. Entities affected : ID: 00000000-0000-0000-0000-000000000000 Type: Storage 2024-06-13 10:36:47,963+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] START, CreateVolumeVDSCommand( CreateVolumeVDSCommandParameters:{storagePoolId='42135536-980b-4ea9-ab66-b850ed8c1f2b', ignoreFailoverLimit='false', storageDomainId='459011cf-ebb6-46ff-831d-8ccfafd82c8a', imageGroupId='09db7fdc-c4d3-4fbd-a50e-1b04de2b1341', imageSizeInBytes='53687091200', volumeFormat='COW', newImageId='1407954a-6d41-4f01-928b-98afa8ef215f', imageType='Sparse', newImageDescription='', imageInitialSizeInBytes='0', imageId='5d65f77d-25fa-4879-8144-6147a16f3ae3', sourceImageGroupId='09db7fdc-c4d3-4fbd-a50e-1b04de2b1341', shouldAddBitmaps='false', legal='true', sequenceNumber='2', bitmap='bf62fab5-fb82-4c03-ac60-ddb9943c9f0d'}), log id: 5ce87935 2024-06-13 10:36:48,055+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] FINISH, CreateVolumeVDSCommand, return: 1407954a-6d41-4f01-928b-98afa8ef215f, log id: 5ce87935 2024-06-13 10:36:48,058+02 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] CommandAsyncTask::Adding CommandMultiAsyncTasks object for command 'a3f817d8-ca15-4fff-a411-ac0294e2ea70' 2024-06-13 10:36:48,058+02 INFO [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] CommandMultiAsyncTasks::attachTask: Attaching task '60e6899b-f59f-404d-af8f-d2ef73e0c908' to command 'a3f817d8-ca15-4fff-a411-ac0294e2ea70'. 2024-06-13 10:36:48,067+02 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Adding task '60e6899b-f59f-404d-af8f-d2ef73e0c908' (Parent Command 'CreateSnapshot', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling hasn't started yet.. 2024-06-13 10:36:48,080+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] BaseAsyncTask::startPollingTask: Starting to poll task '86720608-b5bd-4a28-b7ee-b1a3507592aa'. 2024-06-13 10:36:48,081+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] BaseAsyncTask::startPollingTask: Starting to poll t ask '60e6899b-f59f-404d-af8f-d2ef73e0c908'. 2024-06-13 10:36:48,147+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] EVENT_ID: USER_CREATE_SNAPS HOT(45), Snapshot 'Auto-generated for Backup VM' creation for VM 'mercurio' was initiated by admin@internal. 2024-06-13 10:36:48,151+02 ERROR [org.ovirt.engine.core.bll.storage.backup.HybridBackupCommand] (default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Command 'org.ovirt.engine.core.bll. storage.backup.HybridBackupCommand' failed: CallableStatementCallback; SQL [{call insertvmbackup(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}]; ERROR: duplicate key value violates unique constraint "vm_backups_pkey" Detail: Key (backup_id)=(d5bed8c5-f172-47c7-9827-5dda51490ee8) already exists. Where: SQL statement "INSERT INTO vm_backups ( backup_id, from_checkpoint_id, to_checkpoint_id, vm_id, host_id, phase, _create_date, _update_date, description, backup_type, snapshot_id ) VALUES ( v_backup_id, v_from_checkpoint_id, v_to_checkpoint_id, v_vm_id, v_host_id, v_phase, v__create_date, v__update_date, v_description, v_backup_type, v_snapshot_id )" PL/pgSQL function insertvmbackup(uuid,uuid,uuid,uuid,uuid,text,timestamp with time zone,timestamp with time zone,character varying,character varying,uuid) line 3 at SQL statement; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "vm_backups_pkey" Detail: Key (backup_id)=(d5bed8c5-f172-47c7-9827-5dda51490ee8) already exists. Where: SQL statement "INSERT INTO vm_backups ( backup_id, from_checkpoint_id, to_checkpoint_id, vm_id, host_id, phase, _create_date, _update_date, description, backup_type, snapshot_id ) VALUES ( v_backup_id, v_from_checkpoint_id, v_to_checkpoint_id, v_vm_id, v_host_id, v_phase, v__create_date, v__update_date, v_description, v_backup_type, v_snapshot_id )" PL/pgSQL function insertvmbackup(uuid,uuid,uuid,uuid,uuid,text,timestamp with time zone,timestamp with time zone,character varying,character varying,uuid) line 3 at SQL statement ------------------------------------------------------ Thanks in advance, Giulio

2 1

VM Windows 2022 always been shutdown
by Kalil de A. Carvalho 13 Jun '24

13 Jun '24

Hello all. Here, in my company, we have oVirt verson 4.5.4-1.el9 running with a lots of VM's but all Windows 2022 and 11 has a strange behaviour, sometimes just going down with this message: "VM VM-NAME is down with error. Exit message: Lost connection with qemu process." Looking for any answer on logs I found out this message: "Code=qemu-kvm: ../hw/core/cpu-sysemu.c:77: int cpu_asidx_from_attrs(CPUState *, MemTxAttrs): Assertion `ret < cpu->num_ases && ret >= 0' failed. 2024-06-03 13:59:46.809+0000: shutting down, reason=crashed" We don't understand why it just has problems with Windwos 2022 and 11. Windows 2019 run without problem. Can any one have this kind of situation? Does it have any fixed action? Best regars -- Atenciosamente, Kalil de A. Carvalho

2 1

New installation of oVirt 4.5.6: issues with bll.jar
by samu.paaso＠liberator.fi 12 Jun '24

12 Jun '24

Hello, We are having issues with a brand new deployment of oVirt. After installation, the users are unable to access the Administration or VM portals, they'll face error 500. Other panels, like Keycloak and Grafana work as expected. Digging deeper, there seems to be an issue with file /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar as described in the log /var/log/ovirt-engine/server.log: 2024-06-11 22:18:12,459+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment restapi.war 2024-06-11 22:18:12,468+03 INFO [org.wildfly.security] (MSC service thread 1-2) ELY00001: WildFly Elytron version 1.16.1.Final 2024-06-11 22:18:12,665+03 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 6.0.22.Final 2024-06-11 22:18:12,762+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) WFLYUT0021: Registered web context: '/ovirt-engine/web-ui' for server 'default-server' 2024-06-11 22:18:12,761+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 49) WFLYUT0021: Registered web context: '/ovirt-engine/apidoc' for server 'default-server' 2024-06-11 22:18:12,845+03 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool -- 44) ISPN000128: Infinispan version: Infinispan 'Taedonggang' 12.1.4.Final 2024-06-11 22:18:13,041+03 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool -- 49) ISPN000556: Starting user marshaller 'org.wildfly.clustering.infinispan.marshalling.jboss.JBossMarshaller' 2024-06-11 22:18:13,061+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "enginesso.war") 2024-06-11 22:18:13,061+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: "bll.jar") 2024-06-11 22:18:13,062+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "webadmin.war") 2024-06-11 22:18:13,062+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: "docs.war") 2024-06-11 22:18:13,068+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: "root.war") 2024-06-11 22:18:13,068+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "welcome.war") 2024-06-11 22:18:13,069+03 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0207: Starting subdeployment (runtime-name: "services.war") 2024-06-11 22:18:13,080+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/utils.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,080+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/uutils.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,093+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/sshd-core.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,093+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/sshd-common.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,093+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/jcl-over-slf4j.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,093+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/commons-beanutils.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,093+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/commons-logging.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,093+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/commons-compress.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/commons-lang.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/commons-codec.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/glance-client.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/glance-model.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/cinder-client.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/cinder-model.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/cors-filter.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/compat.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/common.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/hibernate-validator.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/classmate.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/jboss-modules.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/dal.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-jdbc.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-tx.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/java-client-kubevirt.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/vdsm-jsonrpc-java-client.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/commons-lang3.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/commons-collections.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/snakeyaml.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/aaa.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/httpcore.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/httpclient.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/extensions-manager.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/builtin.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/searchbackend.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/branding.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/ovirt-engine-extensions-api.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/keystone-client.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/openstack-client.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/keystone-model.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/quantum-client.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/quantum-model.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/resteasy-connector.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/mail.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/jboss-interceptors-api_1.1_spec.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/xmlrpc-client.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/xmlrpc-common.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/ws-commons-util.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/xml-apis.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-core.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,099+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-jcl.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,099+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-beans.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,099+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-context.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,099+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-aop.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,099+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-expression.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,099+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/jboss-logging.jar in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does not point to a valid jar for a Class-Path reference. 2024-06-11 22:18:13,162+03 INFO [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 3.1.7 (SP1) 2024-06-11 22:18:13,426+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) WFLYCLINF0002: Started authenticationSessions cache from keycloak container 2024-06-11 22:18:13,426+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 54) WFLYCLINF0002: Started authorization cache from keycloak container 2024-06-11 22:18:13,428+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 51) WFLYCLINF0002: Started work cache from keycloak container 2024-06-11 22:18:13,428+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 45) WFLYCLINF0002: Started clientSessions cache from keycloak container 2024-06-11 22:18:13,429+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 44) WFLYCLINF0002: Started offlineClientSessions cache from keycloak container 2024-06-11 22:18:13,429+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 46) WFLYCLINF0002: Started sessions cache from keycloak container 2024-06-11 22:18:13,429+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 47) WFLYCLINF0002: Started loginFailures cache from keycloak container 2024-06-11 22:18:13,429+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 49) WFLYCLINF0002: Started offlineSessions cache from keycloak container 2024-06-11 22:18:13,430+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 50) WFLYCLINF0002: Started keys cache from keycloak container 2024-06-11 22:18:13,430+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 52) WFLYCLINF0002: Started realms cache from keycloak container 2024-06-11 22:18:13,430+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 55) WFLYCLINF0002: Started users cache from keycloak container 2024-06-11 22:18:13,430+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 53) WFLYCLINF0002: Started actionTokens cache from keycloak container 2024-06-11 22:18:13,456+03 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0273: Excluded subsystem webservices via jboss-deployment-structure.xml does not exist. 2024-06-11 22:18:14,479+03 WARN [org.jboss.as.dependency.deprecated] (MSC service thread 1-1) WFLYSRV0221: Deployment "deployment.engine.ear.bll.jar" is using a deprecated module ("sun.jdk") which may be removed in future versions without notice. 2024-06-11 22:18:14,499+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment engine.ear 2024-06-11 22:18:14,588+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment root.war 2024-06-11 22:18:14,665+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment services.war 2024-06-11 22:18:14,674+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment docs.war 2024-06-11 22:18:14,703+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment webadmin.war 2024-06-11 22:18:14,709+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment enginesso.war 2024-06-11 22:18:14,731+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment welcome.war 2024-06-11 22:18:14,783+03 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment bll.jar 2024-06-11 22:18:14,798+03 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'LockManager' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: java:global/engine/bll/LockManager!org.ovirt.engine.core.utils.lock.LockManager java:app/bll/LockManager!org.ovirt.engine.core.utils.lock.LockManager java:module/LockManager!org.ovirt.engine.core.utils.lock.LockManager java:global/engine/bll/LockManager java:app/bll/LockManager java:module/LockManager 2024-06-11 22:18:14,798+03 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'Backend' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: java:global/engine/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler java:app/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler java:module/Backend!org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler java:global/engine/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendInternal java:app/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendInternal java:module/Backend!org.ovirt.engine.core.bll.interfaces.BackendInternal java:global/engine/bll/Backend!org.ovirt.engine.core.common.interfaces.BackendLocal java:app/bll/Backend!org.ovirt.engine.core.common.interfaces.BackendLocal java:module/Backend!org.ovirt.engine.core.common.interfaces.BackendLocal 2024-06-11 22:18:14,798+03 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'OvirtGlusterSchedulingService' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: java:global/engine/bll/OvirtGlusterSchedulingService!org.ovirt.engine.core.bll.scheduling.OvirtGlusterSchedulingService java:app/bll/OvirtGlusterSchedulingService!org.ovirt.engine.core.bll.scheduling.OvirtGlusterSchedulingService java:module/OvirtGlusterSchedulingService!org.ovirt.engine.core.bll.scheduling.OvirtGlusterSchedulingService java:global/engine/bll/OvirtGlusterSchedulingService java:app/bll/OvirtGlusterSchedulingService java:module/OvirtGlusterSchedulingService 2024-06-11 22:18:14,799+03 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'InitBackendServicesOnStartupBean' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: java:global/engine/bll/InitBackendServicesOnStartupBean!org.ovirt.engine.core.bll.InitBackendServicesOnStartup java:app/bll/InitBackendServicesOnStartupBean!org.ovirt.engine.core.bll.InitBackendServicesOnStartup java:module/InitBackendServicesOnStartupBean!org.ovirt.engine.core.bll.InitBackendServicesOnStartup java:global/engine/bll/InitBackendServicesOnStartupBean java:app/bll/InitBackendServicesOnStartupBean java:module/InitBackendServicesOnStartupBean 2024-06-11 22:18:14,799+03 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'ManagedBlockStorageDiskUtil' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: java:global/engine/bll/ManagedBlockStorageDiskUtil!org.ovirt.engine.core.bll.storage.disk.managedblock.util.ManagedBlockStorageDiskUtil java:app/bll/ManagedBlockStorageDiskUtil!org.ovirt.engine.core.bll.storage.disk.managedblock.util.ManagedBlockStorageDiskUtil java:module/ManagedBlockStorageDiskUtil!org.ovirt.engine.core.bll.storage.disk.managedblock.util.ManagedBlockStorageDiskUtil java:global/engine/bll/ManagedBlockStorageDiskUtil java:app/bll/ManagedBlockStorageDiskUtil java:module/ManagedBlockStorageDiskUtil 2024-06-11 22:18:14,799+03 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'MacPoolPerCluster' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: java:global/engine/bll/MacPoolPerCluster!org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster java:app/bll/MacPoolPerCluster!org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster java:module/MacPoolPerCluster!org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster java:global/engine/bll/MacPoolPerCluster java:app/bll/MacPoolPerCluster java:module/MacPoolPerCluster 2024-06-11 22:18:14,934+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 55) WFLYCLINF0002: Started realmRevisions cache from keycloak container 2024-06-11 22:18:14,943+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 55) WFLYCLINF0002: Started userRevisions cache from keycloak container 2024-06-11 22:18:14,950+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 55) WFLYCLINF0002: Started authorizationRevisions cache from keycloak container 2024-06-11 22:18:15,074+03 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool -- 50) ISPN000556: Starting user marshaller 'org.wildfly.clustering.infinispan.marshalling.jboss.JBossMarshaller' 2024-06-11 22:18:15,095+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 50) WFLYCLINF0002: Started dashboard cache from ovirt-engine container 2024-06-11 22:18:15,095+03 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 52) WFLYCLINF0002: Started inventory cache from ovirt-engine container 2024-06-11 22:18:18,858+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 56) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.ovirt.engine.api.restapi.BackendApplication 2024-06-11 22:18:18,859+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 56) RESTEASY002220: Adding singleton resource org.ovirt.engine.api.restapi.resource.BackendApiResource from Application class org.ovirt.engine.api.restapi.BackendApplication 2024-06-11 22:18:18,859+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 56) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.JsonExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2024-06-11 22:18:18,859+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 56) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.IOExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2024-06-11 22:18:18,859+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 56) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.MalformedIdExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2024-06-11 22:18:18,859+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 56) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2024-06-11 22:18:18,860+03 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 56) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.MappingExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2024-06-11 22:18:18,919+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 56) WFLYUT0021: Registered web context: '/ovirt-engine/api' for server 'default-server' 2024-06-11 22:18:19,391+03 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 55) HHH000204: Processing PersistenceUnitInfo [ name: keycloak-default ...] 2024-06-11 22:18:19,455+03 INFO [org.hibernate.Version] (ServerService Thread Pool -- 55) HHH000412: Hibernate Core {5.3.20.Final} 2024-06-11 22:18:19,457+03 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 55) HHH000206: hibernate.properties not found 2024-06-11 22:18:19,589+03 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 55) HCANN000001: Hibernate Commons Annotations {5.0.5.Final} 2024-06-11 22:18:19,778+03 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 55) HHH000400: Using dialect: org.hibernate.dialect.PostgreSQL95Dialect 2024-06-11 22:18:19,851+03 INFO [org.hibernate.engine.jdbc.env.internal.LobCreatorBuilderImpl] (ServerService Thread Pool -- 55) HHH000424: Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException 2024-06-11 22:18:19,856+03 INFO [org.hibernate.type.BasicTypeRegistry] (ServerService Thread Pool -- 55) HHH000270: Type registration [java.util.UUID] overrides previous : org.hibernate.type.UUIDBinaryType@71c04561 2024-06-11 22:18:19,865+03 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 55) Envers integration enabled? : true 2024-06-11 22:18:20,282+03 INFO [org.hibernate.orm.beans] (ServerService Thread Pool -- 55) HHH10005002: No explicit CDI BeanManager reference was passed to Hibernate, but CDI is available on the Hibernate ClassLoader. 2024-06-11 22:18:21,006+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-001125: Illegal bean type org.ovirt.engine.core.dao.DefaultGenericDao<org.ovirt.engine.core.common.businessentities.Provider<?>, org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2024-06-11 22:18:21,016+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-001125: Illegal bean type interface org.ovirt.engine.core.dao.ReadDao<org.ovirt.engine.core.common.businessentities.Provider<?>,class org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2024-06-11 22:18:21,016+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-001125: Illegal bean type class org.ovirt.engine.core.dao.DefaultReadDao<org.ovirt.engine.core.common.businessentities.Provider<?>,class org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2024-06-11 22:18:21,016+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-001125: Illegal bean type org.ovirt.engine.core.dao.GenericDao<org.ovirt.engine.core.common.businessentities.Provider<?>, org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2024-06-11 22:18:21,016+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-001125: Illegal bean type interface org.ovirt.engine.core.dao.ModificationDao<org.ovirt.engine.core.common.businessentities.Provider<?>,class org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2024-06-11 22:18:21,016+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-001125: Illegal bean type org.ovirt.engine.core.dao.SearchDao<org.ovirt.engine.core.common.businessentities.Provider<?>> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2024-06-11 22:18:21,061+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type org.springframework.jdbc.core.RowMapper<org.ovirt.engine.core.common.businessentities.Provider<?>> ignored on [EnhancedAnnotatedTypeImpl] private static class org.ovirt.engine.core.dao.provider.ProviderDaoImpl$ProviderRowMapper 2024-06-11 22:18:21,788+03 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 55) HHH000397: Using ASTQueryTranslatorFactory 2024-06-11 22:18:22,098+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 51) WFLYUT0021: Registered web context: '/ovirt-engine/docs' for server 'default-server' 2024-06-11 22:18:22,103+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 56) WFLYUT0021: Registered web context: '/' for server 'default-server' 2024-06-11 22:18:22,113+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 51) WFLYUT0021: Registered web context: '/ovirt-engine/services' for server 'default-server' 2024-06-11 22:18:22,159+03 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 51) IJ000407: No lazy enlistment available for ENGINEDataSource 2024-06-11 22:18:22,171+03 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 51) IJ000407: No lazy enlistment available for DWHDataSource 2024-06-11 22:18:22,182+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 49) WFLYUT0021: Registered web context: '/ovirt-engine' for server 'default-server' 2024-06-11 22:18:22,201+03 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 51) WFLYUT0021: Registered web context: '/ovirt-engine/webadmin' for server 'default-server' Per my understanding, this doesn't seem like an issue with the PostgreSQL JDBC connector as referenced here https://lists.ovirt.org/archives/list/users@ovirt.org/thread/SBCWNXLFLJBKTA… , but I could be mistaken. What further steps could be taken to mitigate this issue? This is a new deployment, so I'd assume there'd be issues if upgrading older instances but not with new deployments.. The server is running AlmaLinux 9.4 so maybe this would affect this? Best regards, Samu Paaso

2 1

PKIX path validation failed
by Ali Gusainov 12 Jun '24

12 Jun '24

Hello experts. Environment: oVirt: Software Version:4.4.10.7-1.el8 OS: CentOS Linux release 8.5.2111 Symptoms: 1. At login prompt I see this: "PKIX path validation failed: java.security.certCertPathValidatorException: validity check failed" which successfully resolved by "engine-setup --offline" 2. Now the host at 'Unassigned' status and all VMs marked with '?' symbol. At vdsm.log I found message: ERROR (Reactor thread) [ProtocolDetector.SSLHandshakeDispatcher] ssl handshake: socket error, address: ::ffff:..... (sslutils:272) At engine.log I found messages: ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-2) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed ... 2024-06-10 17:54:13,576+05 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-8) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed Cause: Certificate expired. Questions: 1. How to bring host 'Online'? 2. How to properly update SSL?

2 1

Can't access (ping) other 10G interface on host from Hosted Engine
by Patrick Lomakin 10 Jun '24

10 Jun '24

Hello community. I am using the edge version of the Ovirt installation and hosts with Rocky 9. One of my tasks was to partition the networks in the cluster. To make the networks work more properly in Ovirt, I divided the network into VLANs. VLAN 2 is for “ovirtmgmt” network, VLAN 3 is for “gluster-net”, VLAN - 4 is for “migration”. I configured routing between VLANs. Each host has a 10G NIC for the gluster network, and two 1G Bonded NICs for the management network. In the cluster settings, I switched the gluster network to the configured VLAN3 in ovirt. Before that I configured a gluster network for each host via Ovirt, attached it to the 10G interface, assigned static IPs and synchronized the networks. Then I tried to connect bricks and create volume through Ovirt panel, but I got an error to access IP from VLAN3. I pinged HOST1 <---> HOST2 <---> HOST3 and the gluster network pings perfectly in either direction from any host. But the problem is that Hosted Engine can't ping the gluster IP from the 10G interface on any host. Consequently, Hosted Engine does not see the configured IP on the second 10G interface of the host. Only the first interface in the VLAN2 subnet is pinged. What can be the problem? In my eyes this is a pretty common solution that is used everywhere. Thank for any help

1 0

Unable to access the oVirt Manager console and are also unable to connect via SSH
by Sachendra Shukla 10 Jun '24

10 Jun '24

HI Team, We are currently unable to access the oVirt Manager console and are also unable to connect via SSH. The error message we are receiving is: "The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later." Please provide a resolution if you have one. Note: We are able to ping the oVirt Manager IP also vms are working . Below are the snapshots for your reference. [image: image.png] [image: image.png] [image: image.png] -- Regards, *Sachendra Shukla* IT Administrator Yagna iQ, Inc. and subsidiaries Email: Sachendra.shukla(a)yagnaiq.com <dnyanesh.tisge(a)yagnaiq.com> Website: https://yagnaiq.com Privacy Policy: https://www.yagnaiq.com/privacy-policy/ <https://www.linkedin.com/company/yagnaiq/mycompany/> <https://www.youtube.com/channel/UCeHXOpcUxWvOJO0aegD99Jg> This communication and any attachments may contain confidential information and/or Yagna iQ, Inc. copyright material. All unauthorized use, disclosure, or distribution is prohibited. If you are not the intended recipient, please notify Yagna iQ immediately by replying to the email and destroy all copies of this communication. This email has been scanned for all known viruses. The sender does not accept liability for any damage inflicted by viewing the content of this email.

3 2

Re: HCI Gluster Hosted Engine unexpected behavior
by Patryk Lamakin 09 Jun '24

09 Jun '24

And when using a 2 + 1 arbiter replica, if I understand correctly, you can only disable 1 replica host other than the arbiter? What happens in this case if you disable only the host with the arbiter and leave the other 2 replicas running?

1 0

HCI Gluster Hosted Engine unexpected behavior
by Patrick Lomakin 09 Jun '24

09 Jun '24

Hey, everybody. I have 3 hosts on which Gluster replica 3 volume called “engine” is deployed. When I try to put 2 of the 3 hosts into maintenance mode, my deployment crashes. I originally expected that with replica 3 I could shut down 2 of the hosts and everything would work. However, I saw that the default for Gluster is quorum server not allowing more than one host to be disabled. But even after disabling the quorum and verifying that the Gluster disk is available with one host enabled, Hosted Engine still does not access the storage. Who can explain me then the point of using replica 3 if I can't disable 2 hosts and is there any way to fix this behavior?

2 1

Re: Problems with RHEL 9.4 hosts
by Devin A. Bougie 07 Jun '24

07 Jun '24

Unfortunately I’m not exactly sure what the problem was, but I was able to get the fully-updated EL9.4 host back in the cluster after manually deleting all of the iSCSI nodes. Some of the iscsiadm commands printed worked fine: ——— [root@lnxvirt06 ~]# /sbin/iscsiadm -m iface bond1 tcp,<empty>,<empty>,bond1,<empty> default tcp,<empty>,<empty>,<empty>,<empty> iser iser,<empty>,<empty>,<empty>,<empty> [root@lnxvirt06 ~]# /sbin/iscsiadm -m node -T iqn.2002-10.com.infortrend:raid.sn8087428.012 -I bond1 -p 192.168.56.54:3260,1 --op=new New iSCSI node [tcp:[hw=,ip=,net_if=bond1,iscsi_if=bond1] 192.168.56.54,3260,1 iqn.2002-10.com.infortrend:raid.sn8087428.012] added [root@lnxvirt06 ~]# iscsiadm -m node 192.168.56.54:3260,1 iqn.2002-10.com.infortrend:raid.sn8073743.001 192.168.56.54:3260,1 iqn.2002-10.com.infortrend:raid.sn8073743.001 192.168.56.56:3260,1 iqn.2002-10.com.infortrend:raid.sn8073743.101 192.168.56.56:3260,1 iqn.2002-10.com.infortrend:raid.sn8073743.101 192.168.56.55:3260,1 iqn.2002-10.com.infortrend:raid.sn8087428.012 192.168.56.55:3260,1 iqn.2002-10.com.infortrend:raid.sn8087428.012 192.168.56.57:3260,1 iqn.2002-10.com.infortrend:raid.sn8087428.112 192.168.56.57:3260,1 iqn.2002-10.com.infortrend:raid.sn8087428.112 192.168.56.50:3260,1 iqn.2002-10.com.infortrend:raid.uid58204.001 192.168.56.50:3260,1 iqn.2002-10.com.infortrend:raid.uid58204.001 192.168.56.51:3260,1 iqn.2002-10.com.infortrend:raid.uid58204.012 192.168.56.51:3260,1 iqn.2002-10.com.infortrend:raid.uid58204.012 192.168.56.52:3260,1 iqn.2002-10.com.infortrend:raid.uid58204.101 192.168.56.52:3260,1 iqn.2002-10.com.infortrend:raid.uid58204.101 192.168.56.53:3260,1 iqn.2002-10.com.infortrend:raid.uid58204.112 192.168.56.53:3260,1 iqn.2002-10.com.infortrend:raid.uid58204.112 192.168.56.50:3260,1 iqn.2002-10.com.infortrend:raid.uid58207.001 192.168.56.50:3260,1 iqn.2002-10.com.infortrend:raid.uid58207.001 192.168.56.51:3260,1 iqn.2002-10.com.infortrend:raid.uid58207.012 192.168.56.52:3260,1 iqn.2002-10.com.infortrend:raid.uid58207.101 192.168.56.53:3260,1 iqn.2002-10.com.infortrend:raid.uid58207.112 ——— But others didn’t, where the only difference is the portal: ——— [root@lnxvirt06 ~]# /sbin/iscsiadm -m node -T iqn.2002-10.com.infortrend:raid.sn8087428.012 -I bond1 -p 192.168.56.55:3260,1 --op=new iscsiadm: Error while adding record: invalid parameter ——— Likewise, I could delete some nodes using iscsiadm but not others: ——— [root@lnxvirt06 ~]# /sbin/iscsiadm -m node -T iqn.2002-10.com.infortrend:raid.sn8087428.012 -I bond1 -p 192.168.56.54:3260,1 --op=delete [root@lnxvirt06 ~]# /sbin/iscsiadm -m node -T iqn.2002-10.com.infortrend:raid.sn8087428.012 -I bond1 -p 192.168.56.55:3260,1 --op=delete iscsiadm: Could not execute operation on all records: invalid parameter [root@lnxvirt06 ~]# iscsiadm -m node -p 192.168.56.50 -o delete iscsiadm: Could not execute operation on all records: invalid parameter ——— At this point I wiped out /var/lib/iscsi/, rebooted, and everything just worked. Thanks so much for your time and help! Sincerely, Devin > On Jun 7, 2024, at 10:26 AM, Jean-Louis Dupond <jean-louis(a)dupond.be> wrote: > > 2024-06-07 09:59:16,720-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) > 2024-06-07 09:59:16,751-0400 INFO (jsonrpc/0) [storage.iscsi] Adding iscsi node for target 192.168.56.55:3260,1 iqn.2002-10.com.infortrend:raid.sn8087428.012 iface bond1 (iscsi:192) > 2024-06-07 09:59:16,751-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'node', '-T', 'iqn.2002-10.com.infortrend:raid.sn8087428.012', '-I', 'bond1', '-p', '192.168.56.55:3260,1', '--op=new'] (iscsiadm:104) > 2024-06-07 09:59:16,785-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) > 2024-06-07 09:59:16,825-0400 ERROR (jsonrpc/0) [storage.storageServer] Could not configure connection to 192.168.56.55:3260,1 iqn.2002-10.com.infortrend:raid.sn8087428.012 and iface <IscsiInterface name='bond1' transport='tcp' netIfaceName='bond1'>: (7, b'', b'iscsiadm: Error while adding record: invalid parameter\n') (storageServer:580) > Can you try to run those commands manually on the host? > And see what it gives :) > On 7/06/2024 16:13, Devin A. Bougie wrote: >> Thank you! I added a warning at the line you indicated, which produces the following output: >> >> ——— >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,452-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,493-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,532-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,565-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,595-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,636-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,670-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,720-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,751-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'node', '-T', 'iqn.2002-10.com.infortrend:raid.sn8087428.012', '-I', 'bond1', '-p', '192.168.56.55:3260,1', '--op=new'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,785-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,825-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'node', '-T', 'iqn.2002-10.com.infortrend:raid.sn8073743.001', '-I', 'bond1', '-p', '192.168.56.54:3260,1', '--op=new'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,856-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,889-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'node', '-T', 'iqn.2002-10.com.infortrend:raid.sn8073743.101', '-I', 'bond1', '-p', '192.168.56.56:3260,1', '--op=new'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,924-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,957-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'node', '-T', 'iqn.2002-10.com.infortrend:raid.sn8087428.112', '-I', 'bond1', '-p', '192.168.56.57:3260,1', '--op=new'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:16,987-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:17,018-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'node', '-T', 'iqn.2002-10.com.infortrend:raid.uid58204.012', '-I', 'bond1', '-p', '192.168.56.51:3260,1', '--op=new'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:17,051-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:17,079-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'node', '-T', 'iqn.2002-10.com.infortrend:raid.uid58204.001', '-I', 'bond1', '-p', '192.168.56.50:3260,1', '--op=new'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:17,112-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:17,142-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'node', '-T', 'iqn.2002-10.com.infortrend:raid.uid58204.112', '-I', 'bond1', '-p', '192.168.56.53:3260,1', '--op=new'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:17,174-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:17,204-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'node', '-T', 'iqn.2002-10.com.infortrend:raid.uid58204.101', '-I', 'bond1', '-p', '192.168.56.52:3260,1', '--op=new'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:17,237-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:44,186-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:44,234-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:44,268-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:44,310-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:44,343-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:44,370-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:44,408-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> /var/log/vdsm/vdsm.log:2024-06-07 09:59:44,442-0400 WARN (jsonrpc/0) [storage.iscsiadm] iscsiadm executing: ['/sbin/iscsiadm', '-m', 'iface'] (iscsiadm:104) >> ——— >> >> The full vdsm.log is below. >> >> Thanks again, >> Devin >> >> >> >> >> > On Jun 7, 2024, at 8:14 AM, Jean-Louis Dupond <jean-louis(a)dupond.be> wrote: >> > >> > Weird, I have the same 6.2.1.9-1 version, and here it works. >> > You can try to add some print here: https://github.com/oVirt/vdsm/blob/4d11cae0b1b7318b282d9f90788748c0ef3cc965… >> > >> > This should print all executed iscsiadm commands. >> > >> > >> > On 6/06/2024 20:50, Devin A. Bougie wrote: >> >> Awesome, thanks again. Yes, the host is fixed by just downgrading the iscsi-initiator-utils and iscsi-initiator-utils-iscsiuio packages from: >> >> 6.2.1.9-1.gita65a472.el9.x86_64 >> >> to: >> >> 6.2.1.4-3.git2a8f9d8.el9.x86_64 >> >> >> >> Any additional pointers of where to look or how to debug the iscsiadm calls would be greatly appreciated. >> >> >> >> Many thanks! >> >> Devin >> >> >> >>> On Jun 6, 2024, at 2:04 PM, Jean-Louis Dupond <jean-louis(a)dupond.be> wrote: >> >>> >> >>> 2024-06-06 13:28:10,478-0400 ERROR (jsonrpc/5) [storage.storageServer] Could not configure connection to 192.168.56.57:3260,1 iqn.2002-10.com.infortrend:raid.sn8087428.112 and iface <IscsiInterface name='bond1' transport='tcp' netIfaceName='bond1'>: (7, b'', b'iscsiadm: Error while adding record: invalid parameter\n') (storageServer:580) >> >>> >> >>> Seems like some issue with iscsiadm calls. >> >>> Might want to debug which calls it does or what version change there is for iscsiadm. >> >>> >> >>> >> >>> >> >>> "Devin A. Bougie" <devin.bougie(a)cornell.edu> schreef op 6 juni 2024 19:32:29 CEST: >> >>> Thanks so much! Yes, that patch fixed the “out of sync network” issue. However, we’re still unable to join a fully updated 9.4 host to the cluster - now with "Failed to connect Host to Storage Servers”. Downgrading all of the updated packages fixes the issue. >> >>> >> >>> Please see the attached vdsm.log and supervdsm.log from the host after updating it to EL 9.4 and then trying to activate it. Any more suggestions would be greatly appreciated. >> >>> >> >>> Thanks again, >> >>> Devin >> >>> >> >>> >> >>> >> >>> >> >>> >> >>>> On Jun 5, 2024, at 2:35 AM, Jean-Louis Dupond <jean-louis(a)dupond.be> wrote: >> >>>> >> >>>> You most likely need the following patch: >> >>>> https://github.com/oVirt/vdsm/commit/49eaf70c5a14eb00e85eac5f91ac36f010a9a3… >> >>>> >> >>>> Test with that, guess it's fixed then :) >> >>>> >> >>>> On 4/06/2024 22:33, Devin A. Bougie wrote: >> >>>>> Are there any known incompatibilities with RHEL 9.4 (and derivatives)? >> >>>>> >> >>>>> We are running a 7-node ovirt 4.5.5-1.el8 self hosted engine cluster, with all of the hosts running AlmaLinux 9. After upgrading from 9.3 to 9.4, every node started flapping between “Up” and “NonOperational,” with VMs in turn migrating between hosts. >> >>>>> >> >>>>> I believe the underlying issue (or at least the point I got stuck at) was with two of our logical networks being stuck “out of sync” on all hosts. I was unable to synchronize networks or setup the networks using the UI. A reinstall of a host succeeded but then the host immediately reverted to the same state with the same networks being out of sync. >> >>>>> >> >>>>> I eventually found that if I downgraded the host from 9.4 to 9.3, it immediately became stable and back online. >> >>>>> >> >>>>> Are there any known incompatibilities with RHEL 9.4 (and derivatives)? If not, I’m happy to upgrade a single node to test. Please just let me know what log files and details would be most helpful in debugging what goes wrong. >> >>>>> >> >>>>> (And yes, I know we need to upgrade the hosted engine VM itself now that CentOS Stream 8 is now EOL). >> >>>>> >> >>>>> Many thanks, >> >>>>> Devin >> >>>>> >> >>>>> _______________________________________________ >> >>>>> 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/PIROQCVLPVBNJ… >> >> >> >> _______________________________________________ >> 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/AIRCRFWLSG5ZC… >>

1 0

Problems with RHEL 9.4 hosts
by Devin A. Bougie 07 Jun '24

07 Jun '24

Are there any known incompatibilities with RHEL 9.4 (and derivatives)? We are running a 7-node ovirt 4.5.5-1.el8 self hosted engine cluster, with all of the hosts running AlmaLinux 9. After upgrading from 9.3 to 9.4, every node started flapping between “Up” and “NonOperational,” with VMs in turn migrating between hosts. I believe the underlying issue (or at least the point I got stuck at) was with two of our logical networks being stuck “out of sync” on all hosts. I was unable to synchronize networks or setup the networks using the UI. A reinstall of a host succeeded but then the host immediately reverted to the same state with the same networks being out of sync. I eventually found that if I downgraded the host from 9.4 to 9.3, it immediately became stable and back online. Are there any known incompatibilities with RHEL 9.4 (and derivatives)? If not, I’m happy to upgrade a single node to test. Please just let me know what log files and details would be most helpful in debugging what goes wrong. (And yes, I know we need to upgrade the hosted engine VM itself now that CentOS Stream 8 is now EOL). Many thanks, Devin

2 6

No valid authentication mechanism found
by Mathieu Valois 06 Jun '24

06 Jun '24

Hi everyone, we've configured oVirt 4.5.5 with KeyCloak OIDC using an LDAP (FreeIPA) backend. When we wish to login on the portal, i.e https://example.org/ovirt-engine, using the "Administration Portal" or login directly with the button in the upper-right corner, it works (we get redirected to keycloack and so on). However, if we first try to login by clicking on the "VM portal", it fails. We get redirected back to the portal having a "No valid authentication mechanism found" error, as seen on the following screenshot. Then, we're stuck until we clear the cache and cookies of the browser, even when clicking on "Admin portal". Backend logs only show this : 2024-06-04 11:56:24,319-04 ERROR [org.ovirt.engine.core.sso.service.SsoService] (default task-86) [] Aucun mécanisme d'authentification valide trouvé. which translates to the message seen on the screenshot. Do you get any lead to resolve such an issue? Thanks for your kind support, Mathieu Valois Ingénieur sécurité, systèmes et réseaux Bureau Caen : Quartier Kœnig - 153, rue Géraldine MOCK - 14760 Bretteville-sur-Odon Bureau Vitré : Zone de la baratière - 12, route de Domalain - 35500 Vitré 02 72 34 13 20 | https://teicee.com?pk_campaign=Email https://www.facebook.com/teicee https://www.linkedin.com/company/t-c-e

1 0

Connection to ovirt-imageio service has failed
by Денис Панкратьев 05 Jun '24

05 Jun '24

Hello! I have ovirt hypervisor hosts (4.5.5, CentOS Stream 8) and hosted-engine VM (4.5.6-1.el8). I want to upload .ISO to storage domain and get the following error: "Connection to ovirt-imageio service has failed. Ensure that ovirt-engine certificate is registered as a valid CA in the browser." But: 1. Valid CA installed in browser 2. On hosted-engine VM service ovirt-imageio is running (no prolbem) What could be the problem, maybe someone has encountered it?

1 0

Re: Any plans on oVirt Major release with new feature?
by Alessandro 01 Jun '24

01 Jun '24

I don’t understand why Oracle isn’t taking the lead seriously. Olvm and oVirt could really be the “new vsphere” for on prem IaaS. Customer are still using VM, thousands of VMs. I am struggling inside my company to try oVirt/olvm alongside vmware but how can we be sure that oVirt/olvm will not disappear in 1 or 2 years? I saw an interview a month ago with storware and Oracle and althogh I understood that Oracle Linux KVM will still be here for many years, I didn’t feel the same for the management part hence the engine which is OLVM. So, the question is for Oracle (which also contribute to oVirt) for how long (how many years) will they support and develop OLVM? I hope to receive an answare. Regards, Alessandro

1 0

VM Snapshot tab error Code 500
by doboscsongor＠gmail.com 01 Jun '24

01 Jun '24

Hi everybody, I'm new to the oVirt environment, so I started with a fresh install on two physical servers using a hosted engine scenario. Currently, I have version 4.5.6-1.el8 installed. For storage, I am using FC to access our storage. I have created a test VM for testing purposes where I installed MS Windows Server 2022. On the VM, I installed the guest tools, and everything is working fine except for the snapshots tab. If I don't have any snapshots for the VM, I can view the snapshots tab, but if I create a snapshot, the snapshots tab shows an error: "Error while executing action: A request to the server failed with the following status code: 500." Does anyone have any idea why I am getting this error? Thanks in advance!

2 1