May 2023 - Users - Ovirt List Archives

Error when deploy Ovirt4.4 Hosted Engine

by staybox＠gmail.com

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"}

3 months, 1 week

4
4
0 / 0

How to list all snapshots?

by jorgevisentini＠gmail.com

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!

3 months, 1 week

4
3
0 / 0

snapshot solution: Existing snapshots that were taken after this one will be erased.

by dhanaraj.ramesh＠yahoo.com

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.

3 months, 4 weeks

4
3
0 / 0

Restart oVirt-Engine

by Jeremey Wise

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 months, 2 weeks

4
4
0 / 0

Unable to access ovirt Admin Screen from ovirt Host

by louisb＠ameritech.net

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 months, 3 weeks

5
8
0 / 0

SPM and Task error ...

by Enrico

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 _______________________________________________________________________

6 months

5
15
0 / 0

oVirt networks

by Enrico Becchetti

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/ ______________________________________________________________________

9 months

5
6
0 / 0

boot from cdrom & error code 0005

by edp＠maddalena.it

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

9 months, 1 week

4
6
0 / 0

VM Migration Failed

by KSNull Zero

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.

10 months, 3 weeks

4
6
0 / 0

How to re-enroll (or renew) host certificates for a single-host hosted-engine deployment?

by Derek Atkins

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

11 months

8
16
0 / 0

4.5.4 with Ceph only storage

by Maurice Burrows

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

11 months

5
10
0 / 0

i can't access console with noVNC or VNC client(console.vv)

by z84614242＠163.com

i installed the ovirt 4.5 engine on centos stream 9 and add a ovirt node(ovirt node 4.5 iso) to this engine. i am going to run my vm on this node. i follow the instruction to create the data center, the cluster, the storage domain, upload the image. everything is fine. and after i create a vm with ubuntu image attach, i found that i can't visit the console. when i using the noVNC, it says "Something went wrong, connection is closed", when i visit vnc with virt-viewver, is says "Failed to complete handshake Error in the pull function". i try to change the console type to Bochs one and it appear the same. i change to QXL mode and the vm can't start any more. i check the log, it says "unsupported configuration: domain configuration does not support video model 'qxl'". so now i can't visit my vm by anyway. i deploy the engine follow the official instruction and keep mostly option default but why still have this issue. why the noVNC says "Something went wrong" instead of telling me what is actually wrong

1 year

2
1
0 / 0

Changing disk QoS causes segfault with IO-Threads enabled (oVirt 4.3.0.4-1.el7)

by jloh＠squiz.net

We recently upgraded to 4.3.0 and have found that when changing disk QoS settings on VMs whilst IO-Threads is enabled causes them to segfault and the VM to reboot. We've been able to replicate this across several VMs. VMs with IO-Threads disabled/turned off do not segfault when changing the QoS. Mar 1 11:49:06 srvXX kernel: IO iothread1[30468]: segfault at fffffffffffffff8 ip 0000557649f2bd24 sp 00007f80de832f60 error 5 in qemu-kvm[5576498dd000+a03000] Mar 1 11:49:06 srvXX abrt-hook-ccpp: invalid number 'iothread1' Mar 1 11:49:11 srvXX libvirtd: 2019-03-01 00:49:11.116+0000: 13365: error : qemuMonitorIORead:609 : Unable to read from monitor: Connection reset by peer Happy to supply some more logs to someone if they'll help but just wondering whether anyone else has experienced this or knows of a current fix other than turning io-threads off. Cheers.

1 year, 1 month

4
3
0 / 0

Deploy oVirt Engine fail behind proxy

by Matteo Bonardi

Hi, I am trying to deploy the ovirt engine following self-hosted engine installation procedure on documentation. Deployment servers are behind a proxy and I have set it in environment and in yum.conf before run deploy. Deploy fails because ovirt engine vm cannot resolve AppStream repository url: [ INFO ] TASK [ovirt.engine-setup : Install oVirt Engine package] [ ERROR ] fatal: [localhost -> ovirt-manager.mydomain]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'AppStream': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=... [Could not resolve host: mirrorlist.centos.org]", "rc": 1, "results": []} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch logs from the engine VM] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Find the local appliance image] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Copy engine logs] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove local vm dir] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove temporary entry in /etc/hosts for the local VM] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Clean local storage pools] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Destroy local storage-pool {{ he_local_vm_dir | basename }}] [ INFO ] TASK [ovirt.hosted_engine_setup : Undefine local storage-pool {{ he_local_vm_dir | basename }}] [ INFO ] TASK [ovirt.hosted_engine_setup : Destroy local storage-pool {{ local_vm_disk_path.split('/')[5] }}] [ INFO ] TASK [ovirt.hosted_engine_setup : Undefine local storage-pool {{ local_vm_disk_path.split('/')[5] }}] [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20201109165237.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20201109164244-b3e8sd.log How I can set proxy for the engine vm? Ovirt version: [root@myhost ~]# rpm -qa | grep ovirt-engine-appliance ovirt-engine-appliance-4.4-20200916125954.1.el8.x86_64 [root@myhost ~]# rpm -qa | grep ovirt-hosted-engine-setup ovirt-hosted-engine-setup-2.4.6-1.el8.noarch OS version: [root@myhost ~]# cat /etc/centos-release CentOS Linux release 8.2.2004 (Core) [root@myhost ~]# uname -a Linux myhost.mydomain 4.18.0-193.28.1.el8_2.x86_64 #1 SMP Thu Oct 22 00:20:22 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Thanks for the help. Regards, Matteo

1 year, 2 months

7
20
6 / 1

The oVirt Counter

by Sandro Bonazzola

Hi, for those who remember the Linux Counter project, if you'd like other to know you're using oVirt and know some details about your deployment, here's a way to count you in: https://ovirt.org/community/ovirt-counter.html Enjoy! -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D PERFORMANCE & SCALE Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 year, 3 months

1
1
0 / 0

Cannot restart ovirt after massive failure.

by Gilboa Davara

Hello all, During the night, one of my (smaller) setups, a single node self hosted engine (localhost NFS) crashed due to what-looks-like a massive disk failure (Software RAID6, with 10 drives + spare). After a reboot, I let the RAID resync with a fresh drive) and went on to start oVirt. However, no such luck. Two issues: 1. ovirt-ha-broker fails due to broken hosted engine state (log attached). 2. ovirt-ha-agent fails due to network test (tcp) even though both remote-host and DNS servers are active. (log attached). Two questions: 1. Can I somehow force the agent to disable the network liveliness test? 2. Can I somehow force the broker to rebuild / fix the hosted engine state? - Gilboa

1 year, 4 months

4
17
1 / 0

Please, Please Help - New oVirt Install/Deployment Failing - "Host is not up..."

by Matthew J Black

Hi Everyone, Could someone please help me - I've been trying to do an install of oVirt for *weeks* (including false starts and self-inflicted wounds/errors) and it is still not working. My setup: - oVirt v4.5.3 - A brand new fresh vanilla install of RockyLinux 8.6 - all working AOK - 2*NICs in a bond (802.3ad) with a couple of sub-Interfaces/VLANs - all working AOK - All relevant IPv4 Address in DNS with Reverse Lookups - all working AOK - All relevant IPv4 Address in "/etc/hosts" file - all working AOK - IPv6 (using "method=auto" in the interface config file) enabled on the relevant sub-Interface/VLAN - I'm not using IPv6 on the network, only IPv4, but I'm trying to cover all the bases. - All relevant Ports (as per the oVirt documentation) set up on the firewall - ie firewall-cmd --add-service={{ libvirt-tls | ovirt-imageio | ovirt-vmconsole | vdsm }} - All the relevant Repositories installed (ie RockyLinux BaseOS, AppStream, & PowerTools, and the EPEL, plus the ones from the oVirt documentation) I have followed the oVirt documentation (including the special RHEL-instructions and RockyLinux-instructions) to the letter - no deviations, no special settings, exactly as they are written. All the dnf installs, etc, went off without a hitch, including the "dnf install centos-release-ovirt45", "dnf install ovirt-engine-appliance", and "dnf install ovirt-hosted-engine-setup" - no errors anywhere. Here is the results of a "dnf repolist": - appstream Rocky Linux 8 - AppStream - baseos Rocky Linux 8 - BaseOS - centos-ceph-pacific CentOS-8-stream - Ceph Pacific - centos-gluster10 CentOS-8-stream - Gluster 10 - centos-nfv-openvswitch CentOS-8 - NFV OpenvSwitch - centos-opstools CentOS-OpsTools - collectd - centos-ovirt45 CentOS Stream 8 - oVirt 4.5 - cs8-extras CentOS Stream 8 - Extras - cs8-extras-common CentOS Stream 8 - Extras common packages - epel Extra Packages for Enterprise Linux 8 - x86_64 - epel-modular Extra Packages for Enterprise Linux Modular 8 - x86_64 - ovirt-45-centos-stream-openstack-yoga CentOS Stream 8 - oVirt 4.5 - OpenStack Yoga Repository - ovirt-45-upstream oVirt upstream for CentOS Stream 8 - oVirt 4.5 - powertools Rocky Linux 8 - PowerTools So I kicked-off the oVirt deployment with: "hosted-engine --deploy --4 --ansible-extra-vars=he_offline_deployment=true". I used "--ansible-extra-vars=he_offline_deployment=true" because without that flag I was getting "DNF timout" issues (see my previous post `Local (Deployment) VM Can't Reach "centos-ceph-pacific" Repo`). I answer the defaults to all of questions the script asked, or entered the deployment-relevant answers where appropriate. In doing this I double-checked every answer before hitting <Enter>. Everything progressed smoothly until the deployment reached the "Wait for the host to be up" task... which then hung for more than 30 minutes before failing. From the ovirt-hosted-engine-setup... log file: - 2022-10-20 17:54:26,285+1100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"} I checked the following log files and found all of the relevant ERROR lines, then checked several 10s of proceeding and succeeding lines trying to determine what was going wrong, but I could not determine anything. - ovirt-hosted-engine-setup... - ovirt-hosted-engine-setup-ansible-bootstrap_local_vm... - ovirt-hosted-engine-setup-ansible-final_clean... - not really relevant, I believe I can include the log files (or the relevant parts of the log files) if people want - but that are very large: several 100 kilobytes each. I also googled "oVirt Host is not up" and found several entries, but after reading them all the most relevant seems to be a thread from these mailing list: `Install of RHV 4.4 failing - "Host is not up, please check logs, perhaps also on the engine machine"` - but this seems to be talking about an upgrade and I didn't gleam anything useful from it - I could, of course, be wrong about that. So my questions are: - Where else should I be looking (ie other log files, etc, and possible where to find them)? - Does anyone have any idea why this isn't working? - Does anyone have a work-around (including a completely manual process to get things working - I don't mind working in the CLI with virsh, etc)? - What am I doing wrong? Please, I'm really stumped with this, and I really do need help. Cheers Dulux-Oz

1 year, 4 months

8
22
0 / 0

how to renew expired ovirt node vdsm cert manually ?

by dhanaraj.ramesh＠yahoo.com

below are the steps to renew the expired vdsm cert of ovirt node # To check CERT expired # openssl x509 -in /etc/pki/vdsm/certs/vdsmcert.pem -noout -dates 1. Backup vdsm folder # cd /etc/pki # mv vdsm vdsm.orig # mkdir vdsm ; chown vdsm:kvm vdsm # cd vdsm # mkdir libvirt-vnc certs keys libvirt-spice libvirt-migrate # chown vdsm:kvm libvirt-vnc certs keys libvirt-spice libvirt-migrate 2. Regenerate cert & keys # vdsm-tool configure --module certificates 3. Copy the cert to destination location chmod 440 /etc/pki/vdsm/keys/vdsmkey.pem chown root /etc/pki/vdsmcerts/*pem chmod 644 /etc/pki/vdsmcerts/*pem cp /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/libvirt-spice/ca-cert.pem cp /etc/pki/vdsm/keys/vdsmkey.pem /etc/pki/vdsm/libvirt-spice/server-key.pem cp /etc/pki/vdsm/certs/vdsmcert.pem /etc/pki/vdsm/libvirt-spice/server-cert.pem cp /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/libvirt-vnc/ca-cert.pem cp /etc/pki/vdsm/keys/vdsmkey.pem /etc/pki/vdsm/libvirt-vnc/server-key.pem cp /etc/pki/vdsm/certs/vdsmcert.pem /etc/pki/vdsm/libvirt-vnc/server-cert.pem cp -p /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/libvirt-migrate/ca-cert.pem cp -p /etc/pki/vdsm/keys/vdsmkey.pem /etc/pki/vdsm/libvirt-migrate/server-key.pem cp -p /etc/pki/vdsm/certs/vdsmcert.pem /etc/pki/vdsm/libvirt-migrate/server-cert.pem chown root:qemu /etc/pki/vdsm/libvirt-migrate/server-key.pem cp -p /etc/pki/vdsm.orig/keys/libvirt_password /etc/pki/vdsm/keys/ mv /etc/pki/libvirt/clientcert.pem /etc/pki/libvirt/clientcert.pem.orig mv /etc/pki/libvirt/private/clientkey.pem /etc/pki/libvirt/private/clientkey.pem.orig mv /etc/pki/CA/cacert.pem /etc/pki/CA/cacert.pem.orig cp -p /etc/pki/vdsm/certs/vdsmcert.pem /etc/pki/libvirt/clientcert.pem cp -p /etc/pki/vdsm/keys/vdsmkey.pem /etc/pki/libvirt/private/clientkey.pem cp -p /etc/pki/vdsm/certs/cacert.pem /etc/pki/CA/cacert.pem 3. cross check the backup folder /etc/pki/vdsm.orig vs /etc/pki/vdsm # refer to /etc/pki/vdsm.orig/*/ and set the correct owner & group permission in /etc/pki/vdsm/*/ 4. restart services # Make sure both services are up systemctl restart vdsmd libvirtd

1 year, 4 months

5
4
0 / 0

Unable to install oVirt on RHEL7.5

by SS00514758＠techmahindra.com

Hi All, I am unable to install oVirt on RHEL7.5, to install it I am taking reference of below link, https://www.ovirt.org/documentation/install-guide/chap-Installing_oVirt.html But though it is not working for me, couple of dependencies is not getting installed, and because of this I am not able to run the ovirt-engine, below are the depencies packages that unable to install, Error: Package: collectd-write_http-5.8.0-6.1.el7.x86_64 (@ovirt-4.2-centos-opstools) Requires: collectd(x86-64) = 5.8.0-6.1.el7 Removing: collectd-5.8.0-6.1.el7.x86_64 (@ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-6.1.el7 Updated By: collectd-5.8.1-1.el7.x86_64 (epel) collectd(x86-64) = 5.8.1-1.el7 Available: collectd-5.7.2-1.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.7.2-1.el7 Available: collectd-5.7.2-3.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.7.2-3.el7 Available: collectd-5.8.0-2.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-2.el7 Available: collectd-5.8.0-3.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-3.el7 Available: collectd-5.8.0-5.el7.x86_64 (ovirt-4.2-centos-opstools) collectd(x86-64) = 5.8.0-5.el7 Help me to install this. Looking forward to resolve this issue. Regards Sumit Sahay

1 year, 4 months

6
8
0 / 0

Grafana - Origin Not Allowed

by Maton, Brett

oVirt 4.5.0.8-1.el8 I tried to connect to grafana via the monitoring portal link from the dash and all panels are failing to display any data with varying error messages, but all include 'Origin Not Allowed' I navigated to Data Sources and ran a test on the PostgreSQL connection (localhost) which threw the same Origin Not Allowed error message. Any suggestions?

1 year, 5 months

6
8
3 / 0

Multiple hosts stuck in Connecting state waiting for storage pool to go up.

by ivan.lezhnjov.iv＠gmail.com

Hi! We have a problem with multiple hosts stuck in Connecting state, which I hoped somebody here could help us wrap our heads around. All hosts, except one, seem to have very similar symptoms but I'll focus on one host that represents the rest. So, the host is stuck in Connecting state and this what we see in oVirt log files. /var/log/ovirt-engine/engine.log: 2023-04-20 09:51:53,021+03 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-37) [] Command 'GetCapabilitiesAsyncVDSCommand(HostName = ABC010-176-XYZ, VdsIdAndVdsVDSCommandParametersBase:{hostId='2c458562-3d4d-4408-afc9-9a9484984a91', vds='Host[ABC010-176-XYZ,2c458562-3d4d-4408-afc9-9a9484984a91]'})' execution failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: SSL session is invalid 2023-04-20 09:55:16,556+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-67) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ABC010-176-XYZ command Get Host Capabilities failed: Message timeout which can be caused by communication issues /var/log/vdsm/vdsm.log: 2023-04-20 17:48:51,977+0300 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList() from=internal, task_id=ebce7c8c-6ded-454e-9aee-86edf72764ef (api:31) 2023-04-20 17:48:51,977+0300 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=ebce7c8c-6ded-454e-9aee-86edf72764ef (api:37) 2023-04-20 17:48:51,978+0300 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723) Both engine.log and vdsm.log are flooded with these messages. They are repeated at regular intervals ad infinitum. This is one common symptom shared by multiple hosts in our deployment. They all have these message loops in engine.log and vdsm.log files. On all Running vdsm-client Host getConnectedStoragePools also returns an empty list represented by [] on all hosts (but interestingly there is one that showed Storage Pool UUID and yet it was still stuck in Connecting state). This particular host (ABC010-176-XYZ) is connected to 3 CEPH iSCSI Storage Domains and lsblk shows 3 block devices with matching UUIDs in their device components. So, the storage seems to be connected but the Storage Pool is not? How is that even possible? Now, what's even more weird is that we tried rebooting the host (via Administrator Portal) and it didn't help. We even tried removing and re-adding the host in Administrator Portal but to no avail. Additionally, the host refused to go into Maintenance mode so we had to enforce it by manually updating Engine DB. We also tried reinstalling the host via Administrator Portal and ran into another weird problem, which I'm not sure if it's a related one or a problem that deserves a dedicated discussion thread but, basically, the underlying Ansible playbook exited with the following error message: "stdout" : "fatal: [10.10.10.176]: UNREACHABLE! => {\"changed\": false, \"msg\": \"Data could not be sent to remote host \\\"10.10.10.176\\\". Make sure this host can be reached over ssh: \", \"unreachable\": true}", Counterintuitively, just before running Reinstall via Administrator Portal we had been able to reboot the same host (which as you know oVirt does via Ansible as well). So, no changes on the host in between just different Ansible playbooks. To confirm that we actually had access to the host over ssh we successfully ran ssh -p $PORT root(a)10.10.10.176 -i /etc/pki/ovirt-engine/keys/engine_id_rsa and it worked. That made us scratch our heads for a while but what seems to had fixed Ansible's ssh access problems was manual full stop of all VDSM-related systemd services on the host. It was just a wild guess but as soon as we stopped all VDSM services Ansible stopped complaining about not being able to reach the target host and successfully did its job. I'm sure you'd like to see more logs but I'm not certain what exactly is relevant. There are a ton of logs as this deployment is comprised of nearly 80 hosts. So, I guess it's best if you just request to see specific logs, messages or configuration details and I'll cherry-pick what's relevant. We don't really understand what's going on and would appreciate any help. We tried just about anything we could think of to resolve this issue and are running out of ideas what to do next. If you have any questions just ask and I'll do my best to answer them.

1 year, 6 months

2
4
0 / 0

Re: Failed to synchronize networks of Provider ovirt-provider-ovn

by Mail SET Inc. Group

Yes, i use same manual to change WebUI SSL. ovirt-ca-file= is a same SSL file which use WebUI. Yes, i restart ovirt-provider-ovn, i restart engine, i restart all what i can restart. Nothing... > 12 сент. 2018 г., в 16:11, Dominik Holler <dholler(a)redhat.com> написал(а): > > On Wed, 12 Sep 2018 14:23:54 +0300 > "Mail SET Inc. Group" <mail(a)set-pro.net> wrote: > >> Ok! > > Not exactly, please use users(a)ovirt.org for such questions. > Other should benefit from this questions, too. > Please write the next mail to users(a)ovirt.org and keep me in CC. > >> What i did: >> >> 1) install oVirt «from box» (4.2.5.2-1.el7); >> 2) generate own ssl for my engine using my FreeIPA CA, Install it and > > What means "Install it"? You can use the doc from the following link > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/... > > Ensure that ovirt-ca-file= in > /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf > points to the correct file and ovirt-provider-ovn is restarted. > >> get tis issue; >> >> >> [root@engine ~]# tail -n 50 /var/log/ovirt-provider-ovn.log >> 2018-09-12 14:10:23,828 root [SSL: CERTIFICATE_VERIFY_FAILED] >> certificate verify failed (_ssl.c:579) Traceback (most recent call >> last): File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py", >> line 133, in _handle_request method, path_parts, content >> File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py", >> line 175, in handle_request return >> self.call_response_handler(handler, content, parameters) File >> "/usr/share/ovirt-provider-ovn/handlers/keystone.py", line 33, in >> call_response_handler return response_handler(content, parameters) >> File "/usr/share/ovirt-provider-ovn/handlers/keystone_responses.py", >> line 62, in post_tokens user_password=user_password) File >> "/usr/share/ovirt-provider-ovn/auth/plugin_facade.py", line 26, in >> create_token return auth.core.plugin.create_token(user_at_domain, >> user_password) File >> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/plugin.py", line >> 48, in create_token timeout=self._timeout()) File >> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 75, >> in create_token username, password, engine_url, ca_file, timeout) >> File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line >> 91, in _get_sso_token timeout=timeout File >> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 54, >> in wrapper response = func(*args, **kwargs) File >> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 47, >> in wrapper raise BadGateway(e) BadGateway: [SSL: >> CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:579) >> >> >> [root@engine ~]# tail -n 20 /var/log/ovirt-engine/engine.log >> 2018-09-12 14:10:23,773+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685] Lock >> Acquired to object >> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]', >> sharedLocks=''}' 2018-09-12 14:10:23,778+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685] >> Running command: SyncNetworkProviderCommand internal: true. >> 2018-09-12 14:10:23,836+03 ERROR >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685] >> Command >> 'org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand' >> failed: EngineException: (Failed with error Bad Gateway and code >> 5050) 2018-09-12 14:10:23,837+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685] Lock >> freed to object >> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]', >> sharedLocks=''}' 2018-09-12 14:14:12,477+03 INFO >> [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default >> task-6) [] User admin@internal successfully logged in with scopes: >> ovirt-app-admin ovirt-app-api ovirt-app-portal >> ovirt-ext=auth:sequence-priority=~ ovirt-ext=revoke:revoke-all >> ovirt-ext=token-info:authz-search >> ovirt-ext=token-info:public-authz-search >> ovirt-ext=token-info:validate ovirt-ext=token:password-access >> 2018-09-12 14:14:12,587+03 INFO >> [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default >> task-6) [1bf1b763] Running command: CreateUserSessionCommand >> internal: false. 2018-09-12 14:14:12,628+03 INFO >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (default task-6) [1bf1b763] EVENT_ID: USER_VDC_LOGIN(30), User >> admin@internal-authz connecting from '10.0.3.61' using session >> 's8jAm7BUJGlicthm6yZBA3CUM8QpRdtwFaK3M/IppfhB3fHFB9gmNf0cAlbl1xIhcJ2WX+ww7e71Ri+MxJSsIg==' >> logged in. 2018-09-12 14:14:30,972+03 INFO >> [org.ovirt.engine.core.bll.provider.ImportProviderCertificateCommand] >> (default task-6) [ee3cc8a7-4485-4fdf-a0c2-e9d67b5cfcd3] Running >> command: ImportProviderCertificateCommand internal: false. Entities >> affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: >> SystemAction group CREATE_STORAGE_POOL with role type ADMIN >> 2018-09-12 14:14:30,982+03 INFO >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (default task-6) [ee3cc8a7-4485-4fdf-a0c2-e9d67b5cfcd3] EVENT_ID: >> PROVIDER_CERTIFICATE_IMPORTED(213), Certificate for provider >> ovirt-provider-ovn was imported. (User: admin@internal-authz) >> 2018-09-12 14:14:31,006+03 INFO >> [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand] >> (default task-6) [a48d94ab-b0b2-42a2-a667-0525b4c652ea] Running >> command: TestProviderConnectivityCommand internal: false. Entities >> affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: >> SystemAction group CREATE_STORAGE_POOL with role type ADMIN >> 2018-09-12 14:14:31,058+03 ERROR >> [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand] >> (default task-6) [a48d94ab-b0b2-42a2-a667-0525b4c652ea] Command >> 'org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand' >> failed: EngineException: (Failed with error Bad Gateway and code >> 5050) 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'default' is using 0 threads out of 1, 5 threads waiting for >> tasks. 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'engine' is using 0 threads out of 500, 16 threads waiting for >> tasks and 0 tasks in queue. 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'engineScheduled' is using 0 threads out of 100, 100 threads >> waiting for tasks. 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'engineThreadMonitoring' is using 1 threads out of 1, 0 threads >> waiting for tasks. 2018-09-12 14:15:10,954+03 INFO >> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] >> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread >> pool 'hostUpdatesChecker' is using 0 threads out of 5, 2 threads >> waiting for tasks. 2018-09-12 14:15:23,843+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f] Lock >> Acquired to object >> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]', >> sharedLocks=''}' 2018-09-12 14:15:23,849+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f] >> Running command: SyncNetworkProviderCommand internal: true. >> 2018-09-12 14:15:23,900+03 ERROR >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f] >> Command >> 'org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand' >> failed: EngineException: (Failed with error Bad Gateway and code >> 5050) 2018-09-12 14:15:23,901+03 INFO >> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] >> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f] Lock >> freed to object >> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]', >> sharedLocks=''}' >> >> >> [root@engine ~]# >> cat /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf # >> This file is automatically generated by engine-setup. Please do not >> edit manually [OVN REMOTE] ovn-remote=ssl:127.0.0.1:6641 >> [SSL] >> https-enabled=true >> ssl-cacert-file=/etc/pki/ovirt-engine/ca.pem >> ssl-cert-file=/etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer >> ssl-key-file=/etc/pki/ovirt-engine/keys/ovirt-provider-ovn.key.nopass >> [OVIRT] >> ovirt-sso-client-secret=Ms7Gw9qNT6IkXu7oA54tDmxaZDIukABV >> ovirt-host=https://engine.set.local:443 >> ovirt-sso-client-id=ovirt-provider-ovn >> ovirt-ca-file=/etc/pki/ovirt-engine/apache-ca.pem >> [PROVIDER] >> provider-host=engine.set.local >> >> >>> 12 сент. 2018 г., в 13:59, Dominik Holler <dholler(a)redhat.com> >>> написал(а): >>> >>> On Wed, 12 Sep 2018 13:04:53 +0300 >>> "Mail SET Inc. Group" <mail(a)set-pro.net> wrote: >>> >>>> Hello Dominik! >>>> I have a same issue with OVN provider and SSL >>>> https://www.mail-archive.com/users@ovirt.org/msg47020.html >>>> <https://www.mail-archive.com/users@ovirt.org/msg47020.html> But >>>> certificate changes not helps to resolve it. Maybe you can help me >>>> with this? >>> >>> Sure. Can you please share the relevant lines of >>> ovirt-provider-ovn.log and engine.log, and the information if you >>> are using the certificates generated by engine-setup with >>> users(a)ovirt.org ? Thanks, >>> Dominik >>> >> > >

1 year, 7 months

5
13
2 / 0

engine-config -s UserSessionTimeOutInterval=X problem

by marek

ovirt 4.5.4, standalone engine, centos 8 stream [root@ovirt ~]# engine-config -g UserSessionTimeOutInterval Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false UserSessionTimeOutInterval: 30 version: general [root@ovirt ~]# engine-config -s UserSessionTimeOutInterval=60 Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false Cannot set value 60 to key UserSessionTimeOutInterval. any ideas where is the problem? Marek

1 year, 9 months

5
6
0 / 0

Unable to upload or download iso via admin portal

by Igor Filipovic

Hi, I'm having a trouble on fresh 4.4.10.7 installation (on oracle linux), I'm not able to upload or download any file using storage domain upload image function. I've imported CA certificate and have tried on several browsers (firefow, chrome,edge), on different computers (and browsers are green - claiming that I'm securely connected), but I'm always getting error regarding CA certificate when I test connection, or when I try to upload ISO image. I've tried to upload ISO image via cli commands (upload_disk.py), and that scenario was successful, however this method It is not very convenient for my co-workers. I have 5 physical hosts, one is dedicated to run ovirt-engine, and other 4 are kvm hypervisors. When I try to upload ISO this is what engine.log logs: 2023-04-08 11:00:28,339+02 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-2) [f6b62add-0a0c-45ee-a985-a76171843382] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: 1eb97088-b805-4616-af55-0ac9d1d7dfbe Type: SystemAction group CREATE_DISK with role type USER 2023-04-08 11:00:28,340+02 INFO [org.ovirt.engine.core.bll.storage.disk.image.ImageTransferUpdater] (default task-2) [f6b62add-0a0c-45ee-a985-a76171843382] Updating image transfer a78b18c5-e395-4c29-aa5c-15ffff8a1cb6 (image 4f758325-ac11-4071-a9fa-d180425e8604) phase to Paused by System (message: 'Sent 0MB') 2023-04-08 11:00:28,363+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-2) [f6b62add-0a0c-45ee-a985-a76171843382] EVENT_ID: UPLOAD_IMAGE_NETWORK_ERROR(1,062), Unable to upload image to disk 4f758325-ac11-4071-a9fa-d180425e8604 due to a network error. Ensure ovirt-engine's CA certificate is registered as a trusted CA in the browser. The certificate can be fetched from https://engine-dr.somedomain/ovirt-engine/services/pki-resource?resource=... 2023-04-08 11:00:28,363+02 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-2) [f6b62add-0a0c-45ee-a985-a76171843382] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: 1eb97088-b805-4616-af55-0ac9d1d7dfbe Type: SystemAction group CREATE_DISK with role type USER Can you please point me in some direction to try to fix this? Thanks, and best regards Igor

1 year, 9 months

4
4
1 / 0

ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials

by cmicarelli＠fdmservices.it

Hi Guys, I'm tried to install ovirt 4.5 on centos 8 stream and everytime file with this error ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials Someone could help me? Regrards

1 year, 9 months

2
2
0 / 0

engine-setup failing on 4.3.2 -> 4.3.3 fails during Engine schema refresh fail

by Edward Berger

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

1 year, 10 months

4
6
0 / 0

Suggestion to switch to nightly

by Sandro Bonazzola

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

1 year, 10 months

5
9
1 / 0

Bcp vm

by Ali Gusainov

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

1 year, 11 months

2
5
1 / 0

Non responsive host (4.3.10)

by Maria Souvalioti

Hello everyone! Due to a recent major power outage in my area I now have an unresponsive self hosted host in an environment of 3 self hosted hosts. There's one vm stuck on there as well as some metadata I guess from when hosted engine was running there (before the power went down). I'm running 4.3.10 ovirt node with 3 nodes and GlusterFS, no arbiter, and I'm using it to provide services to our clients i.e. DNS, web sites, wikis, ticketing etc. and I cannot shut them down. The ovirt engine is up and running and I can manage all the other VMs that run on the other hosts through the web gui. The unresponsive host replies only to ICMP requests; in every other sense it's dead, no ssh, no gluster bricks, no console, nothing. I tried to place the faulty host in maintenance, using the option to stop glusterd, but wasn't able to as the engine won't let the host go into maintenance mode because it thinks the host has running VMs on it. The host won't go into maintenance even if I chose the "Ignore gluster quorum and self-heal validations" option. I spent last week creating a backup environment were I copied the VMs, to have somewhere to run them in case something goes terribly wrong with the systems or the gluster in the production system. I'm thinking of using the global maintenance mode and then shutting down the engine itself with *hosted-engine --vm-shutdown* and rebooting the affected host. Should I remove the host from the cluster and then re-add it or should I do something else? Thanks for any of your help!

1 year, 11 months

3
4
0 / 0

novnc console error: promise.js missing?

by karl.morgan＠gmail.com

Seeing the following on the engine when attempting to start a novnc console 2023-03-31 11:57:34,988-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (default task-29) [307c22a9] START, SetVmTicketVDSCommand(HostName = ov2node02-mn, SetVmTicketVDSCommandParameters:{hostId='19a92de3-c6e4-4f4e-be31-1d5533a2b6b6', vmId='4481b0e9-a96c-4ee7-8bd2-572558eb9fda', protocol='VNC', ticket='LMl903dd', validTime='120', userName='admin@ovirt', userId='9e88a363-34cb-466a-8ba9-25e46819423b', disconnectAction='LOCK_SCREEN', consoleDisconnectActionDelay='0'}), log id: 1d6520d5 2023-03-31 11:57:35,031-07 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (default task-29) [307c22a9] FINISH, SetVmTicketVDSCommand, return: , log id: 1d6520d5 2023-03-31 11:57:35,044-07 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-29) [307c22a9] EVENT_ID: VM_SET_TICKET(164), User admin@ovirt@internalkeycloak-authz initiated console session for VM first 2023-03-31 11:57:35,158-07 INFO [org.ovirt.engine.core.utils.servlet.ServletUtils] (default task-29) [] Can't read file '/usr/share/ovirt-engine/files/novnc/vendor/promise.js' for request '/ovirt-engine/services/files/novnc/vendor/promise.js' -- 404 Curious if this is obvious to anyone? How to resolve? ovirt-engine-webadmin-portal-4.5.4-1.el9.noarch ovirt-engine-4.5.4-1.el9.noarch

1 year, 12 months

2
1
0 / 0

OKD Installer Provisioned Infrastructure in oVirt > 4.3

by Fredrik Arneving

Hi, I've successfully installed OKD <= 4.8 in my ovirt 4.3 self-hosted engine setup. However, I have now found out that the imageio-proxy and/or imageio-deamon has changed it's API calls and ports to make the OKD install fail on self-hosted (all-in-one) setups on ovirt 4.4 and 4.5. Since I've upgraded to version 4.5 I can no longer install OKD with Installer Provisioned Infrastructure. I recently read throough a long thread in bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=1871348) on how to get image uploads working from the GUI but haven't found any solutions for making the OKD install work. The suggested solution, engine-config -s "EnableImageioProxy=false", didn't solve my problem. Would it be possible to tweak the setup so that the OKD installer can upload it's image through imageio? I don't use the imageio service for anything else since I (almost) only kickstart my new vm's from my foreman servers so if other use cases than the OKD install would fail I can live with that. I take it the problem only appears for a self-hosted setup. If it was possible to migrate the engine to a standalone host (not a powerful compute node but somewhere with 4vCPU and 16 GB RAM) would that make the solution easier? I would lose a lot of my current infrastructure if I had to reinstall but if I can't find a better solution I will have to. Any help would be appreciated.

1 year, 12 months

1
0
0 / 0

VM host deploy failed

by Latchezar Filtchev

Hi there, Centos Stream 8 fresh standalone install from nightly build of ovirt-engine. VM host Centos Stream 8 node nightly build repo enabled. Cannot add host to engine. The error message: Host n1 installation failed. Task Install ovirt-hosted-engine-setup package failed to execute. Please check logs for more details: /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20230530094214-n1............. Any hint will be appreciated. Thank you! Best, Latcho 2023-05-30 09:42:26 EEST - { "uuid" : "e905de36-7b04-4b52-96b8-71855d561446", "counter" : 99, "stdout" : "fatal: [n1.aubgin.local]: FAILED! => {\"changed\": false, \"failures\": [], \"msg\": \"Depsolve Error occurred: \\n Problem: conflicting requests\\n - nothing provides python3-importlib-resources needed by ovirt-hosted-engine-setup-2.7.1-0.0.master.20230414113600.git340e19b.el8.noarch\", \"rc\": 1, \"results\": []}", "start_line" : 87, "end_line" : 88, "runner_ident" : "c7d833e9-8de3-4d53-87a3-72c3d80177ce", "event" : "runner_on_failed", "pid" : 41043, "created" : "2023-05-30T06:42:25.111204", "parent_uuid" : "ac162d01-a065-3587-db9e-000000000228", "event_data" : { "playbook" : "ovirt-host-deploy.yml", "playbook_uuid" : "de0dd632-7d53-4e08-a06c-610334200c49", "play" : "all", "play_uuid" : "ac162d01-a065-3587-db9e-000000000006", "play_pattern" : "all", "task" : "Install ovirt-hosted-engine-setup package", "task_uuid" : "ac162d01-a065-3587-db9e-000000000228", "task_action" : "ansible.builtin.yum", "task_args" : "", "task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/packages.yml:6", "role" : "ovirt-host-deploy-vdsm", "host" : "n1.aubgin.local", "remote_addr" : "n1.aubgin.local", "res" : { "failures" : [ ], "results" : [ ], "rc" : 1, "msg" : "Depsolve Error occurred: \n Problem: conflicting requests\n - nothing provides python3-importlib-resources needed by ovirt-hosted-engine-setup-2.7.1-0.0.master.20230414113600.git340e19b.el8.noarch", "invocation" : { "module_args" : { "name" : [ "ovirt-hosted-engine-setup" ], "state" : "present", "allow_downgrade" : false, "autoremove" : false, "bugfix" : false, "cacheonly" : false, "disable_gpg_check" : false, "disable_plugin" : [ ], "disablerepo" : [ ], "download_only" : false, "enable_plugin" : [ ], "enablerepo" : [ ], "exclude" : [ ], "installroot" : "/", "install_repoquery" : true, "install_weak_deps" : true, "security" : false, "skip_broken" : false, "update_cache" : false, "update_only" : false, "validate_certs" : true, "sslverify" : true, "lock_timeout" : 30, "allowerasing" : false, "nobest" : false, "conf_file" : null, "disable_excludes" : null, "download_dir" : null, "list" : null, "releasever" : null } }, "_ansible_no_log" : null, "changed" : false }, "start" : "2023-05-30T06:42:23.217686", "end" : "2023-05-30T06:42:25.111007", "duration" : 1.893321, "ignore_errors" : null, "event_loop" : null, "uuid" : "e905de36-7b04-4b52-96b8-71855d561446" } } [root@e host-deploy]#

1 year, 12 months

1
0
0 / 0

NIC Ordering

by Alan G

Is there any way to enforce NIC ordering so the vNICs match the ordering in the Engine UI? I found this but not clear if it was ever implemented? https://www.ovirt.org/develop/release-management/features/network/predict...

2 years

3
6
0 / 0

ERROR HSMGetAllTasksStatusesVDS Cannot deactivate Logical Volume:

by parallax

Hello environment: oVirt 4.5.4-1 messages like this appear in the event log what do these errors mean? the volume 114f08c4-f864-44e1-a937-19405307e643 has 128m size ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-18) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM kvm3 command HSMGetAllTasksStatusesVDS failed: value=Cannot deactivate Logical Volume: 'error=General Storage Exception: ("5 [] [\' Logical volume 3526ebaa-31de-4c9f-b724-f0fbe5448a78/114f08c4-f864-44e1-a937-19405307e643 in use.\']\\n3526ebaa-31de-4c9f-b724-f0fbe5448a78/[\'114f08c4-f864-44e1-a937-19405307e643\']",), users={\'/dev/3526ebaa-31de-4c9f-b724-f0fbe5448a78/114f08c4-f864-44e1-a937-19405307e643\': [{\'pid\': 2227780, \'command\': \'systemd-udevd\', \'user\': \'root\', \'fd\': 7}]}' abortedcode=552

2 years

1
0
0 / 0

Extended ovirt image disk and now virtual size is < 1 GiB and actual size i +1TB

by arc＠b4restore.com

Hi, i extended 16 virtual image disks today by 1000GiB through the GUI and now we have a problem with some of them... 9 of them are shown if "edited" that they have a size of 0GiB and not 16360GiB as expected? 5 of them are not able to be extended either within the VM. we tried to power it off and then on again (not reboot, but actual power off / power on) any suggestions to get out of this weird mode? disks seems as if they have the "old" size within the VM but are shown in oVirt as if they are 0GiB.? They are relying on a posix compliant fs if that makes any difference, and they are thin-provisioned and discard-enabled. Thanks in advance.

2 years

2
3
0 / 0

VM causes CPU blocks and forces reboot of host

by dominik.drazyk＠blackrack.pl

Hello, I have recently migrated our customer's cluster to newer hardware (CentOS 8 Stream, 4 hypervisor nodes, 3 hosts with GlusterFS 5x 6TB SSD as JBOD with replica 3). After 1 month from the switch we encounter frequent vm locks that need host reboot in order to unlock the VM. Affected vms cannot be powered down from ovirt UI. Even if ovirt is successful in powering down affected vms, they cannot be booted again with information that OS disk is used. Once I reboot the host, vms can be turned on and everything works fine. In vdsm logs I can note the following error: 2023-05-11 19:33:12,339+0200 ERROR (qgapoller/1) [virt.periodic.Operation] <bound method QemuGuestAgentPoller._poller of <vdsm.virt.qemuguestagent.QemuGuestAgentPoller object at 0x7f553aa3e470>> operation failed (periodic:187) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/virt/periodic.py", line 185, in __call__ self._func() File "/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py", line 476, in _poller vm_id, self._qga_call_get_vcpus(vm_obj)) File "/usr/lib/python3.6/site-packages/vdsm/virt/qemuguestagent.py", line 797, in _qga_call_get_vcpus if 'online' in vcpus: TypeError: argument of type 'NoneType' is not iterable /var/log/messages reports: May 11 19:35:15 kernel: task:CPU 7/KVM state:D stack: 0 pid: 7065 ppid: 1 flags: 0x80000182 May 11 19:35:15 kernel: Call Trace: May 11 19:35:15 kernel: __schedule+0x2d1/0x870 May 11 19:35:15 kernel: schedule+0x55/0xf0 May 11 19:35:15 kernel: schedule_preempt_disabled+0xa/0x10 May 11 19:35:15 kernel: rwsem_down_read_slowpath+0x26e/0x3f0 May 11 19:35:15 kernel: down_read+0x95/0xa0 May 11 19:35:15 kernel: get_user_pages_unlocked+0x66/0x2a0 May 11 19:35:15 kernel: hva_to_pfn+0xf5/0x430 [kvm] May 11 19:35:15 kernel: kvm_faultin_pfn+0x95/0x2e0 [kvm] May 11 19:35:15 kernel: ? select_task_rq_fair+0x355/0x990 May 11 19:35:15 kernel: ? sched_clock+0x5/0x10 May 11 19:35:15 kernel: ? sched_clock_cpu+0xc/0xb0 May 11 19:35:15 kernel: direct_page_fault+0x3b4/0x860 [kvm] May 11 19:35:15 kernel: kvm_mmu_page_fault+0x114/0x680 [kvm] May 11 19:35:15 kernel: ? vmx_vmexit+0x9f/0x70d [kvm_intel] May 11 19:35:15 kernel: ? vmx_vmexit+0xae/0x70d [kvm_intel] May 11 19:35:15 kernel: ? gfn_to_pfn_cache_invalidate_start+0x190/0x190 [kvm] May 11 19:35:15 kernel: vmx_handle_exit+0x177/0x770 [kvm_intel] May 11 19:35:15 kernel: ? gfn_to_pfn_cache_invalidate_start+0x190/0x190 [kvm] May 11 19:35:15 kernel: vcpu_enter_guest+0xafd/0x18e0 [kvm] May 11 19:35:15 kernel: ? hrtimer_try_to_cancel+0x7b/0x100 May 11 19:35:15 kernel: kvm_arch_vcpu_ioctl_run+0x112/0x600 [kvm] May 11 19:35:15 kernel: kvm_vcpu_ioctl+0x2c9/0x640 [kvm] May 11 19:35:15 kernel: ? pollwake+0x74/0xa0 May 11 19:35:15 kernel: ? wake_up_q+0x70/0x70 May 11 19:35:15 kernel: ? __wake_up_common+0x7a/0x190 May 11 19:35:15 kernel: do_vfs_ioctl+0xa4/0x690 May 11 19:35:15 kernel: ksys_ioctl+0x64/0xa0 May 11 19:35:15 kernel: __x64_sys_ioctl+0x16/0x20 May 11 19:35:15 kernel: do_syscall_64+0x5b/0x1b0 May 11 19:35:15 kernel: entry_SYSCALL_64_after_hwframe+0x61/0xc6 May 11 19:35:15 kernel: RIP: 0033:0x7faf1a1387cb May 11 19:35:15 kernel: Code: Unable to access opcode bytes at RIP 0x7faf1a1387a1. May 11 19:35:15 kernel: RSP: 002b:00007fa6f5ffa6e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 May 11 19:35:15 kernel: RAX: ffffffffffffffda RBX: 000055be52e7bcf0 RCX: 00007faf1a1387cb May 11 19:35:15 kernel: RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000027 May 11 19:35:15 kernel: RBP: 0000000000000000 R08: 000055be5158c6a8 R09: 00000007d9e95a00 May 11 19:35:15 kernel: R10: 0000000000000002 R11: 0000000000000246 R12: 0000000000000000 May 11 19:35:15 kernel: R13: 000055be515bcfc0 R14: 00007fffec958800 R15: 00007faf1d6c6000 May 11 19:35:15 kernel: INFO: task worker:714626 blocked for more than 120 seconds. May 11 19:35:15 kernel: Not tainted 4.18.0-489.el8.x86_64 #1 May 11 19:35:15 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. May 11 19:35:15 kernel: task:worker state:D stack: 0 pid:714626 ppid: 1 flags:0x00000180 May 11 19:35:15 kernel: Call Trace: May 11 19:35:15 kernel: __schedule+0x2d1/0x870 May 11 19:35:15 kernel: schedule+0x55/0xf0 May 11 19:35:15 kernel: schedule_preempt_disabled+0xa/0x10 May 11 19:35:15 kernel: rwsem_down_read_slowpath+0x26e/0x3f0 May 11 19:35:15 kernel: down_read+0x95/0xa0 May 11 19:35:15 kernel: do_madvise.part.30+0x2c3/0xa40 May 11 19:35:15 kernel: ? syscall_trace_enter+0x1ff/0x2d0 May 11 19:35:15 kernel: ? __x64_sys_madvise+0x26/0x30 May 11 19:35:15 kernel: __x64_sys_madvise+0x26/0x30 May 11 19:35:15 kernel: do_syscall_64+0x5b/0x1b0 May 11 19:35:15 kernel: entry_SYSCALL_64_after_hwframe+0x61/0xc6 May 11 19:35:15 kernel: RIP: 0033:0x7faf1a138a4b May 11 19:35:15 kernel: Code: Unable to access opcode bytes at RIP 0x7faf1a138a21. May 11 19:35:15 kernel: RSP: 002b:00007faf151ea7f8 EFLAGS: 00000206 ORIG_RAX: 000000000000001c May 11 19:35:15 kernel: RAX: ffffffffffffffda RBX: 00007faf149eb000 RCX: 00007faf1a138a4b May 11 19:35:15 kernel: RDX: 0000000000000004 RSI: 00000000007fb000 RDI: 00007faf149eb000 May 11 19:35:15 kernel: RBP: 0000000000000000 R08: 00000007faf080ba R09: 00000000ffffffff May 11 19:35:15 kernel: R10: 00007faf151ea760 R11: 0000000000000206 R12: 00007faf15aec48e May 11 19:35:15 kernel: R13: 00007faf15aec48f R14: 00007faf151eb700 R15: 00007faf151ea8c0 May 11 19:35:15 kernel: INFO: task worker:714628 blocked for more than 120 seconds. May 11 19:35:15 kernel: Not tainted 4.18.0-489.el8.x86_64 #1 May 11 19:35:15 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Installed VDSM packages: vdsm-api-4.50.3.4-1.el8.noarch vdsm-network-4.50.3.4-1.el8.x86_64 vdsm-yajsonrpc-4.50.3.4-1.el8.noarch vdsm-http-4.50.3.4-1.el8.noarch vdsm-client-4.50.3.4-1.el8.noarch vdsm-4.50.3.4-1.el8.x86_64 vdsm-gluster-4.50.3.4-1.el8.x86_64 vdsm-python-4.50.3.4-1.el8.noarch vdsm-jsonrpc-4.50.3.4-1.el8.noarch vdsm-common-4.50.3.4-1.el8.noarch Libvirt: libvirt-client-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-nodedev-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-logical-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-network-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-qemu-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-scsi-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-core-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-config-network-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-iscsi-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-rbd-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-libs-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-config-nwfilter-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-secret-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-disk-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-mpath-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-gluster-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 python3-libvirt-8.0.0-2.module_el8.7.0+1218+f626c2ff.x86_64 libvirt-daemon-driver-nwfilter-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-lock-sanlock-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-interface-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-driver-storage-iscsi-direct-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 libvirt-daemon-kvm-8.0.0-14.module_el8.8.0+1257+0c3374ae.x86_64 During the issue with locked vms, they do not respond from network, I cannot use VNC console (or any other) to check what is happening from VM perspective. The host cannot list running processes. There are plenty of resources left and each host runs about 30-35 vms. First I thought that it might be related to glusterfs (I use gluster on other clusters and it usually works fine), so we migrated all vms back to old storage (NFS). The problem came back today on two hosts. I do not have such issues on other cluster which runs on Rocky 8.6 with hyperconverged glusterfs. Hence as a last resort I'll be migrating to Rocky 8 from CentOS 8-stream. Has anyone observed such issues with ovirt hosts on CentOS 8-stream? Any form of help is welcome, as I'm running out of ideas.

2 years

4
4
0 / 0

Patching issue on RHEL 8.7-8.8

by jamesroark＠gmail.com

After applying RHEL updates for the recent upgrade from 8.7 to 8.8, I started getting some package problems on my oVirt engine and hosts. Perhaps someone can help me figure out what is going on. Environment: oVirt 4.5.4-1.el8 Stand alone engine - Red Hat Enterprise Linux release 8.7 (Ootpa) RHEL hosts - Red Hat Enterprise Linux release 8.7 (Ootpa) # yum update Updating Subscription Management repositories. Last metadata expiration check: 3:01:05 ago on Fri 19 May 2023 09:43:55 AM EDT. Error: Problem: installed package centos-stream-release-8.6-1.el8.noarch obsoletes redhat-release < 9 provided by redhat-release-8.8-0.8.el8.x86_64 - cannot install the best update candidate for package redhat-release-8.7-0.3.el8.x86_64 - problem with installed package centos-stream-release-8.6-1.el8.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) # yum update --nobest Updating Subscription Management repositories. Last metadata expiration check: 3:01:25 ago on Fri 19 May 2023 09:43:55 AM EDT. Dependencies resolved. Problem: installed package centos-stream-release-8.6-1.el8.noarch obsoletes redhat-release < 9 provided by redhat-release-8.8-0.8.el8.x86_64 - cannot install the best update candidate for package redhat-release-8.7-0.3.el8.x86_64 - problem with installed package centos-stream-release-8.6-1.el8.noarch Nothing to do. Complete! I've applied the https://ovirt.org/download/install_on_rhel.html suggestions. When I try to "Install nightly oVirt master snapshot" as suggested, I also get an error: # dnf copr enable -y ovirt/ovirt-master-snapshot centos-stream-8 Updating Subscription Management repositories. Enabling a Copr repository. Please note that this repository is not part of the main distribution, and quality may vary. The Fedora Project does not exercise any power over the contents of this repository beyond the rules outlined in the Copr FAQ at <https://docs.pagure.org/copr.copr/user_documentation.html#what-i-can-buil...>, and packages are not held to any quality or security level. Please do not file bug reports about these packages in Fedora Bugzilla. In case of problems, contact the owner of this repository. Error: Failed to connect to https://copr.fedorainfracloud.org/coprs/ovirt/ovirt-master-snapshot/repo/...: Error

2 years

2
2
0 / 0

Ovirt 4.5.0 Support (End of Life Date)

by masood.ahmed＠digital.mod.uk

Hi, I am working on a project and we would like to utilise (oVirt 4.5.) as the platform for our enterprise infrastructure. We have arrived at this juncture because of a range of considerations related to hardware and software availability and compatibility. My question is if there is on-going vendor \ professional support for oVirt moving forward, as one of my colleagues spoke with Red Hat, who stated they are going to end their support for the product. we will not gain security accreditation for our project unless we have professional support available, community support only is not sufficient, Any ideas of firms available for a support contract for oVirt 4.5.0? thanks

2 years

2
1
0 / 0

constant error in enfine lof and Ovirt dashboard.

by eevans＠digitaldatatechs.com

My setup: CentOS 7 with Gluster 9.6 managed outside of engine, includes 3 servers plusdt the engine host. engine is a standalong but controls the 3 managed gluster volumes hosts. One of the hosts manages the gluster volume. I have used this setup for years and have never seen this on the engine host, but I have on the gluster volume servers. engine.log: 2023-05-22 15:58:33,020-04 INFO [org.ovirt.engine.core.vdsbroker.gluster.Gluste rServersListVDSCommand] (DefaultQuartzScheduler6) [235e97d6] FINISH, GlusterServ ersListVDSCommand, return: [192.168.254.252/24:CONNECTED, kvm04.digitaldatatechs .com:CONNECTED, kvm02.digitaldatatechs.com:CONNECTED], log id: 513632a0 2023-05-22 15:58:33,032-04 INFO [org.ovirt.engine.core.vdsbroker.gluster.AddGlu sterServerVDSCommand] (DefaultQuartzScheduler6) [235e97d6] START, AddGlusterServ erVDSCommand(HostName = kvm02, AddGlusterServerVDSParameters:{hostId='41b5df10-e d0a-4d6a-b375-c77ae9b681b6'}), log id: 6b6b5c97 2023-05-22 15:58:36,237-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghan dling.AuditLogDirector] (DefaultQuartzScheduler6) [235e97d6] EVENT_ID: GLUSTER_S ERVER_ADD_FAILED(4,436), Failed to add host kvm02 into Cluster ovirt_cluster. Ad d host failed: rc=107 out=() err=['Probe returned with Transport endpoint is not connected'] This shows up about eveny 90 seconds. No other issues and the host is up, volume is up. Triple checked firewalld and even disabled it as a test. SELinux is disabled. I'm not sure what I'm missing. Everything looks great in the cockpit. Any help is appreciated. Thanks in advance.

2 years

1
0
0 / 0

Ovirt 4.5 deploy failed

by Selçuk N

Hello, I'm trying to install Ovirt 4.5 and I got the following error. FAILED! => {"attempts": 50, "changed": false, "msg": "Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials."} The node and hosted-engine vm password is the same and does not have any problem. Here are detailed logs. What am I doing wrong? Thank you. Regards 2023-05-18 18:49:25,924+0000 DEBUG ansible on_any args localhost TASK: ovirt.ovirt.hosted_engine_setup : include_tasks kwargs 2023-05-18 18:49:26,601+0000 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': '', 'task_duration': 1} 2023-05-18 18:49:26,601+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa5580> kwargs 2023-05-18 18:49:26,644+0000 DEBUG ansible on_any args /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/auth_sso.yml (args={} vars={}): [localhost] kwargs 2023-05-18 18:49:27,317+0000 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml', 'ansible_task': 'ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials'} 2023-05-18 18:49:27,317+0000 DEBUG ansible on_any args TASK: ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials kwargs is_conditional:False 2023-05-18 18:49:27,318+0000 DEBUG ansible on_any args localhost TASK: ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials kwargs 2023-05-18 18:49:29,447+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f970781b430> kwargs 2023-05-18 18:49:40,175+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079b9190> kwargs 2023-05-18 18:49:50,869+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079cb460> kwargs 2023-05-18 18:50:01,565+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079b9190> kwargs 2023-05-18 18:50:12,258+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707864b50> kwargs 2023-05-18 18:50:22,932+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079b9b80> kwargs 2023-05-18 18:50:33,638+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9709cb0370> kwargs 2023-05-18 18:50:44,319+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079b9190> kwargs 2023-05-18 18:50:54,990+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9709cb0370> kwargs 2023-05-18 18:51:05,683+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079b9b80> kwargs 2023-05-18 18:51:16,375+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9709cb0370> kwargs 2023-05-18 18:51:27,062+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079b9190> kwargs 2023-05-18 18:51:37,766+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9709cb0a60> kwargs 2023-05-18 18:51:48,422+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97077c3670> kwargs 2023-05-18 18:51:59,125+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97078c2a30> kwargs 2023-05-18 18:52:09,821+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa5730> kwargs 2023-05-18 18:52:20,489+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707a41ac0> kwargs 2023-05-18 18:52:31,188+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f970781b700> kwargs 2023-05-18 18:52:41,873+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707894580> kwargs 2023-05-18 18:52:52,559+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707894760> kwargs 2023-05-18 18:53:03,260+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079f3d00> kwargs 2023-05-18 18:53:13,923+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa14f0> kwargs 2023-05-18 18:53:24,622+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707a01310> kwargs 2023-05-18 18:53:35,311+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97076b0700> kwargs 2023-05-18 18:53:45,964+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa14f0> kwargs 2023-05-18 18:53:56,661+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f970771afa0> kwargs 2023-05-18 18:54:07,346+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa15e0> kwargs 2023-05-18 18:54:18,018+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa5730> kwargs 2023-05-18 18:54:28,715+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa5c40> kwargs 2023-05-18 18:54:39,387+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97076f8cd0> kwargs 2023-05-18 18:54:50,067+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa17c0> kwargs 2023-05-18 18:55:00,773+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa5730> kwargs 2023-05-18 18:55:11,426+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707a36c40> kwargs 2023-05-18 18:55:22,121+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa5c40> kwargs 2023-05-18 18:55:32,809+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97077b5880> kwargs 2023-05-18 18:55:43,463+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97075dc0d0> kwargs 2023-05-18 18:55:54,157+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa14f0> kwargs 2023-05-18 18:56:04,841+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa5c40> kwargs 2023-05-18 18:56:15,500+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97079b9250> kwargs 2023-05-18 18:56:26,193+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97076b05e0> kwargs 2023-05-18 18:56:36,875+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f970787c790> kwargs 2023-05-18 18:56:47,557+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f970769ba00> kwargs 2023-05-18 18:56:58,257+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707aa14f0> kwargs 2023-05-18 18:57:08,912+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97076f8c10> kwargs 2023-05-18 18:57:19,612+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97076f8040> kwargs 2023-05-18 18:57:30,302+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97077b5160> kwargs 2023-05-18 18:57:40,969+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f970769b160> kwargs 2023-05-18 18:57:51,664+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9707516b80> kwargs 2023-05-18 18:58:02,347+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97073f1c40> kwargs 2023-05-18 18:58:13,021+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f970769bb20> kwargs 2023-05-18 18:58:24,784+0000 DEBUG var changed: host "localhost" var "ansible_failed_task" type "<class 'dict'>" value: "{ "action": "ovirt_auth", "any_errors_fatal": false, "args": { "_ansible_check_mode": false, "_ansible_debug": false, "_ansible_diff": false, "_ansible_keep_remote_files": false, "_ansible_module_name": "ovirt_auth", "_ansible_no_log": false, "_ansible_remote_tmp": "~/.ansible/tmp", "_ansible_selinux_special_fs": [ "fuse", "nfs", "vboxsf", "ramfs", "9p", "vfat" ], "_ansible_shell_executable": "/bin/sh", "_ansible_socket": null, "_ansible_string_conversion_action": "warn", "_ansible_syslog_facility": "LOG_USER", "_ansible_tmpdir": "/root/.ansible/tmp/ansible-tmp-1684436303.0466125-36573-187227954552032/", "_ansible_verbosity": 0, "_ansible_version": "2.13.5", "insecure": true }, "async": 0, "async_val": 0, "become": false, "become_exe": null, "become_flags": null, "become_method": "sudo", "become_user": null, "changed_when": [], "check_mode": false, "collections": [ "ovirt.ovirt", "ansible.builtin" ], "connection": "local", "debugger": null, "delay": 10, "delegate_facts": null, "delegate_to": null, "diff": false, "environment": [ { "OVIRT_PASSWORD": "**FILTERED**", "OVIRT_URL": "https://eng.xxxx.net/ovirt-engine/api", "OVIRT_USERNAME": "admin@internal" } ], "failed_when": [], "finalized": true, "ignore_errors": null, "ignore_unreachable": null, "loop": null, "loop_control": null, "loop_with": null, "module_defaults": [], "name": "Obtain SSO token using username/password credentials", "no_log": null, "notify": null, "poll": 15, "port": null, "register": "ovirt_sso_auth", "remote_user": null, "retries": 50, "run_once": null, "squashed": true, "tags": [ "never", "bootstrap_local_vm", "never" ], "throttle": 0, "timeout": 0, "until": [ "ovirt_sso_auth is succeeded" ], "uuid": "1866daab-9d24-cf71-0985-00000000181c", "vars": {}, "when": [] }" 2023-05-18 18:58:24,784+0000 DEBUG var changed: host "localhost" var "ansible_failed_result" type "<class 'dict'>" value: "{ "_ansible_no_log": null, "_ansible_parsed": true, "attempts": 50, "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_auth_payload_x_h__rn9/ansible_ovirt_auth_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_auth.py\", line 287, in main\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 382, in authenticate\n self._sso_token = self._get_access_token()\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 627, in _get_access_token\n sso_error[1]\novirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials.\n", "failed": true, "invocation": { "module_args": { "ca_file": null, "compress": true, "headers": null, "hostname": null, "insecure": true, "kerberos": false, "ovirt_auth": null, "password": null, "state": "present", "timeout": 0, "token": null, "url": null, "username": null } }, "msg": "Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials." }" 2023-05-18 18:58:24,784+0000 ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": null, "attempts": 50, "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_auth_payload_x_h__rn9/ansible_ovirt_auth_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_auth.py\", line 287, in main\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 382, in authenticate\n self._sso_token = self._get_access_token()\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 627, in _get_access_token\n sso_error[1]\novirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials.\n", "invocation": { "module_args": { "ca_file": null, "compress": true, "headers": null, "hostname": null, "insecure": true, "kerberos": false, "ovirt_auth": null, "password": null, "state": "present", "timeout": 0, "token": null, "url": null, "username": null } }, "msg": "Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials." }, "ansible_task": "Obtain SSO token using username/password credentials", "ansible_type": "task", "status": "FAILED", "task_duration": 538 } 2023-05-18 18:58:24,784+0000 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f97073f1520> kwargs ignore_errors:None 2023-05-18 18:58:25,487+0000 DEBUG var changed: host "localhost" var "ovirt_sso_auth" type "<class 'dict'>" value: "{ "attempts": 50, "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_auth_payload_x_h__rn9/ansible_ovirt_auth_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_auth.py\", line 287, in main\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 382, in authenticate\n self._sso_token = self._get_access_token()\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 627, in _get_access_token\n sso_error[1]\novirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials.\n", "failed": true, "msg": "Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials." }" 2023-05-18 18:58:25,487+0000 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml', 'ansible_task': 'ovirt.ovirt.hosted_engine_setup : Sync on engine machine'} 2023-05-18 18:58:25,487+0000 DEBUG ansible on_any args TASK: ovirt.ovirt.hosted_engine_setup : Sync on engine machine kwargs is_conditional:False

2 years

2
2
0 / 0

ovirt node

by skhurtsilava＠cellfie.ge

Hello Guys I installed oVirt Node 4.4 and I want to deploy Hosted Engine but i get this error [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Ensure the resolved address resolves only on the selected interface] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "hostname 'ovirt.bee.moitel.local' doesn't uniquely match the interface 'ens192' selected for the management bridge; it matches also interface with IP ['fe80::9a5b:2039:fe49:5252', '192.168.222.1', 'fd00:1234:5678:900::1']. Please make sure that the hostname got from the interface for the management network resolves only there.\n"} How can i fix this error?

2 years

2
1
0 / 0

oVirt and Oracle Linux Virtualization Manager

by Andrei Verovski

Hi, Does Oracle plan to continue active development of oVirt, since it is released as Oracle Linux Virtualization Manager ? with best regards Andrei

2 years

1
0
0 / 0

Re: Basic authentication to Rest api not working 4.5.4

by kishorekumar.goli＠gmail.com

Thanks Alexei for the response. I see httpd configuration is updated to use oauth. I see below configuration updated in /etc/httpd/conf.d/internalsso-openidc.conf <LocationMatch ^/ovirt-engine/api($|/)> AuthType oauth20 Require valid-user </LocationMatch> I dont see any release notes about removal of basic authentication in 4.5.x. So I wanted to know if this is mentioned anywhere in the documentation.

2 years

2
1
0 / 0

How to deploy a glusterFS on ovirt 4.5 cluster

by patrick.noel＠2IS.biz

Hi, I installed an ovirt 4.5 cluster with 3 nodes and a hosted engine. I would like to configure a GlusterFS cluster on the 3 nodes. I follow this procedure https://www.ovirt.org/dropped/gluster-hyperconverged/chap-Deploying_Hyper... but the package cockpit-ovirt-dashboard does not exist. What is the procedure to follow? Thank you.

2 years

1
0
0 / 0

Basic authentication to Rest api not working 4.5.4

by kishorekumar.goli＠gmail.com

We are facing issue while using basic authentication . We get 401 unauthorized error . It was working in previous versions. parameters used: curl -vvk -u "admin:admin" -H "Content-type: application/xml" -X GET https://<ovirt_gui>/ovirt-engine/api/hosts/ <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html> <head> <title>401 Unauthorized</title> </head> <body> <h1>Unauthorized</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> </body> </html>

2 years

2
1
0 / 0

Failed to read or parse '/etc/pki/ovirt-engine/keys/engine.p12'

by Frank Wall

Hi, I was trying to restore a oVirt Engine Backup into a new Hosted Engine appliance (as part of an upgrade), but this failed with the following error: --== PKI CONFIGURATION ==-- [WARNING] Failed to read or parse '/etc/pki/ovirt-engine/keys/engine.p12' Perhaps it was changed since last Setup. Error was: Error outputting keys and certificates 80EBCC44677F0000:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:crypto/evp/evp_fetch.c:373:Global default library context, Algorithm (RC2-40-CBC : 0) It looks like this is related to openssl requiring legacy mode to use the old Engine cert/key. Is there any way to workaround this? Or would it be possible to repackage the existing PCKS#12 file with new encryption (on the old Engine)? Regards - Frank

2 years

3
3
0 / 0

[ansible]attach vdisk to vm

by Pietro Pesce

Hello ever1 i create a playbook for create and attach vdisk (from direct lun) to vm, the firs block work. I want attach the created vdisk to second vm. how can do? --- # Add fiber chanel disk - name: Create disk ovirt.ovirt.ovirt_disk: auth: "{{ ovirt_auth }}" name: "{{ item.0 }}" host: "{{host}}" shareable: True interface: virtio_scsi vm_name: "{{hostname}}" scsi_passthrough: disabled logical_unit: id: "{{ item.1 }}" storage_type: fcp loop: "{{ disk_name | zip(lun) | list }}" ## Add disk second node #- name: Create disk # ovirt.ovirt.ovirt_disk: # auth: "{{ ovirt_auth }}" # vm_name: "{{hostname2}}" # name: "{{ item.0 }}" # host: "{{host}}" # interface: virtio_scsi # logical_unit: # id: "{{ item.1 }}" # storage_type: fcp # loop: "{{ disk_name | zip(lun) | list }}" thanks

2 years

1
0
0 / 0

engine setup fails: error: The system may not be provisioned according to the playbook results

by neeldey427＠gmail.com

I'm trying to setup the engine. But I am getting the same error. [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Remove temporary entry in /etc/hosts for the local VM] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Destroy local storage-pool localvm3a2r5z0y] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Undefine local storage-pool localvm3a2r5z0y] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Destroy local storage-pool 9ef860a6-ee88-4aa6-94ac-a429a90ebec8] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Undefine local storage-pool 9ef860a6-ee88-4aa6-94ac-a429a90ebec8] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} Please let me know if you need more information in this regard or contents from any of the log files. Any & all suggestions on how to fix/troubleshoot this are much appreciated.

2 years

1
0
0 / 0

engine setup fails: error creating bridge interface virbr0: File exists - ?

by lejeczek

Hi guys. I'm trying to setup the engine on the latest stable ovirt node(in a VM), so a clean, vanilla-default system. -> $ hosted-engine --deploy --4 ... [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Activate default libvirt network] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "cmd": ["virsh", "net-start", "default"], "delta": "0:00:00.042134", "end": "2023-05-11 11:08:59.248405", "msg": "non-zero return code", "rc": 1, "start": "2023-05-11 11:08:59.206271", "stderr": "error: Failed to start network default\nerror: error creating bridge interface virbr0: File exists", "stderr_lines": ["error: Failed to start network default", "error: error creating bridge interface virbr0: File exists"], "stdout": "", "stdout_lines": []} [ ERROR ] Failed to execute stage 'Closing up': Failed getting local_vm_dir ... Any & all suggestions on how to fix/troubleshoot this are much appreciated. many thanks, L.

2 years

2
3
0 / 0

Migration failed after upgrade engine from 4.3 to 4.4

by Emmanuel Ferrandi

Hi ! When I try to migrate a powered VM (regardless of OS) from one hypervisor to another, the VM is immediately shut down with this error message: /Migration failed: Admin shut down from the engine (VM: VM, Source: HP11)./ The oVirt engine has been upgraded from version 4.3 to version 4.4. Some nodes are in version 4.3 and others in version 4.4. Here are the oVirt versions for selected hypervisors: * HP11 : 4.4 * HP5 : 4.4 * HP6 : 4.3 Here are the migration attempts I tried with a powered VM : * From HP > to HP * HP6 > HP5 : OK * HP6 > HP11 : OK * HP5 > HP11 : OK * HP5 > HP6 : OK * HP11 > HP5 : *NOK* * HP11 > HP6 : OK As mentioned above the migration of a VM between two versions of ovirt is not a problem. The migration of the VM between two HPs with the same 4.4 version works only in one direction (HP5 to HP11) and doesn't work in the other way. I already tried to reinstall both HPs in version 4.4 but without success. Here are the logs on the HP5 concerning the VM: //var/log/vdsm/vdsm.log:2023-05-11 14:32:56,303+0200 INFO (jsonrpc/3) [api.virt] START destroy(gracefulAttempts=1) from=::ffff:172.20.3.250,37534, flow_id=43364065, vmId=d14f75cd-1cb1-440b-9780-6b6ee78149ac (api:48)// ///var/log/vdsm/vdsm.log:2023-05-11 14:32:56,303+0200 INFO (jsonrpc/3) [api] FINISH destroy error=Virtual machine does not exist: {'vmId': 'd14f75cd-1cb1-440b-9780-6b6ee78149ac'} (api:129)// ///var/log/vdsm/vdsm.log:2023-05-11 14:32:56,303+0200 INFO (jsonrpc/3) [api.virt] FINISH destroy return={'status': {'code': 1, 'message': "Virtual machine does not exist: {'vmId': 'd14f75cd-1cb1-440b-9780-6b6ee78149ac'}"}} from=::ffff:172.20.3.250,37534, flow_id=43364065, vmId=d14f75cd-1cb1-440b-9780-6b6ee78149ac (api:54)/ //var/log/libvirt/qemu/VM.log:2023-03-24 14:56:51.474+0000: initiating migration// ///var/log/libvirt/qemu/VM.log:2023-03-24 14:56:54.342+0000: shutting down, reason=migrated// ///var/log/libvirt/qemu/VM.log:2023-03-24T14:56:54.870528Z qemu-kvm: terminating on signal 15 from pid 4379 (<unknown process>)/ Here are the log on the engine concerning the VM: // //var/log/ovirt-engine/engine.log:2023-05-11 14:32:53,333+02 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-18197) [3f672d7f-f617-47a2-b0e9-c521656e8c01] START, MigrateVDSCommand( MigrateVDSCommandParameters:{hostId='6817e182-f163-4a44-9ad6-53156b8bb5a0', vmId='d14f75cd-1cb1-440b-9780-6b6ee78149ac', srcHost='HP11', dstVdsId='d2481de5-5ad2-4d06-9545-d5628cb87bcb', dstHost='HP5:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', migrateEncrypted='null', consoleAddress='null', maxBandwidth='256', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='192.168.1.1'}), log id: 6a3507d0// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:53,334+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-18197) [3f672d7f-f617-47a2-b0e9-c521656e8c01] START, MigrateBrokerVDSCommand(HostName = HP11, MigrateVDSCommandParameters:{hostId='6817e182-f163-4a44-9ad6-53156b8bb5a0', vmId='d14f75cd-1cb1-440b-9780-6b6ee78149ac', srcHost='HP11', dstVdsId='d2481de5-5ad2-4d06-9545-d5628cb87bcb', dstHost='HP5:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', migrateEncrypted='null', consoleAddress='null', maxBandwidth='256', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='192.168.1.1'}), log id: f254f72// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,246+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-9) [3f0e966d] VM 'd14f75cd-1cb1-440b-9780-6b6ee78149ac' was reported as Down on VDS '6817e182-f163-4a44-9ad6-53156b8bb5a0'(HP11)// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,296+02 INFO [org.ovirt.engine.core.bll.SaveVmExternalDataCommand] (ForkJoinPool-1-worker-9) [43364065] Running command: SaveVmExternalDataCommand internal: true. Entities affected : ID: d14f75cd-1cb1-440b-9780-6b6ee78149ac Type: VM// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,299+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-9) [43364065] START, DestroyVDSCommand(HostName = HP11, DestroyVmVDSCommandParameters:{hostId='6817e182-f163-4a44-9ad6-53156b8bb5a0', vmId='d14f75cd-1cb1-440b-9780-6b6ee78149ac', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 20bf3f27// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,303+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-9) [43364065] Failed to destroy VM 'd14f75cd-1cb1-440b-9780-6b6ee78149ac' because VM does not exist, ignoring// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,303+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-9) [43364065] VM 'd14f75cd-1cb1-440b-9780-6b6ee78149ac'(VM) moved from 'MigratingFrom' --> 'Down'// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,303+02 INFO [org.ovirt.engine.core.vdsbroker.DestroyVmVDSCommand] (ForkJoinPool-1-worker-9) [43364065] START, DestroyVmVDSCommand( DestroyVmVDSCommandParameters:{hostId='d2481de5-5ad2-4d06-9545-d5628cb87bcb', vmId='d14f75cd-1cb1-440b-9780-6b6ee78149ac', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 1734109b// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,303+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-9) [43364065] START, DestroyVDSCommand(HostName = HP5, DestroyVmVDSCommandParameters:{hostId='d2481de5-5ad2-4d06-9545-d5628cb87bcb', vmId='d14f75cd-1cb1-440b-9780-6b6ee78149ac', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 2679b538// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,307+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-9) [43364065] Failed to destroy VM 'd14f75cd-1cb1-440b-9780-6b6ee78149ac' because VM does not exist, ignoring// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,310+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-9) [43364065] Stopped migrating VM: 'd14f75cd-1cb1-440b-9780-6b6ee78149ac'(VM) on VDS: 'd2481de5-5ad2-4d06-9545-d5628cb87bcb'// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,329+02 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (ForkJoinPool-1-worker-9) [43364065] Lock freed to object 'EngineLock:{exclusiveLocks='[d14f75cd-1cb1-440b-9780-6b6ee78149ac=VM]', sharedLocks=''}'// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,333+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-9) [43364065] VM 'd14f75cd-1cb1-440b-9780-6b6ee78149ac' was reported as Down on VDS '6817e182-f163-4a44-9ad6-53156b8bb5a0'(HP11)// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,333+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-9) [43364065] VM 'd14f75cd-1cb1-440b-9780-6b6ee78149ac'(VM) was unexpectedly detected as 'Down' on VDS '6817e182-f163-4a44-9ad6-53156b8bb5a0'(HP11) (expected on 'null')// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,333+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-9) [43364065] START, DestroyVDSCommand(HostName = HP11, DestroyVmVDSCommandParameters:{hostId='6817e182-f163-4a44-9ad6-53156b8bb5a0', vmId='d14f75cd-1cb1-440b-9780-6b6ee78149ac', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 6a04ab1// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,358+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-9) [43364065] Failed to destroy VM 'd14f75cd-1cb1-440b-9780-6b6ee78149ac' because VM does not exist, ignoring// ///var/log/ovirt-engine/engine.log:2023-05-11 14:32:56,358+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-9) [43364065] VM 'd14f75cd-1cb1-440b-9780-6b6ee78149ac'(VM) was unexpectedly detected as 'Down' on VDS '6817e182-f163-4a44-9ad6-53156b8bb5a0'(HP11) (expected on 'null')/ Has anyone ever encountered this kind of problem following an oVirt cluster update? Thanks, -- Emmanuel

2 years

1
0
0 / 0

barely started - cannot import name 'Callable' from 'collections'

by lejeczek

Hi guys. I've barely started, trying to deploy my first oVirt and I get: ... Please indicate the gateway IP address [10.3.1.254]: [ INFO ] Checking available network interfaces: [ ERROR ] b'[WARNING]: Skipping plugin (/usr/share/ovirt-hosted-engine-\n' [ ERROR ] b'setup/he_ansible/callback_plugins/2_ovirt_logger.py), cannot load: cannot\n' [ ERROR ] b"import name 'Callable' from 'collections'\n" [ ERROR ] b'(/usr/lib64/python3.11/collections/__init__.py)\n' [ ERROR ] b"ERROR! Unexpected Exception, this is probably a bug: cannot import name 'Callable' from 'collections' (/usr/lib64/python3.11/collections/__init__.py)\n" [ ERROR ] Failed to execute stage 'Environment customization': Failed executing ansible-playbook [ INFO ] Stage: Clean up [ INFO ] Cleaning temporary resources [ ERROR ] b'[WARNING]: Skipping plugin (/usr/share/ovirt-hosted-engine-\n' [ ERROR ] b'setup/he_ansible/callback_plugins/2_ovirt_logger.py), cannot load: cannot\n' [ ERROR ] b"import name 'Callable' from 'collections'\n" [ ERROR ] b'(/usr/lib64/python3.11/collections/__init__.py)\n' [ ERROR ] b"ERROR! Unexpected Exception, this is probably a bug: cannot import name 'Callable' from 'collections' (/usr/lib64/python3.11/collections/__init__.py)\n" [ ERROR ] Failed to execute stage 'Clean up': Failed executing ansible-playbook [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20230509193552.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20230509193544-s72umf.log centos 9 stream with ovirt-engine-setup-base-4.5.3.1-1.el9.noarch Any & every suggestion on what is braking here and how to troubleshoot/fix it are much appreciated. thanks, L.

2 years

2
1
0 / 0

Please help connecting to serial console - <urlopen error [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:897)>

by morgan cox

Hi. I have an Ovirt 4.4.10 system - its a standalone setup (not hosted engine) - ovirt-vmconsole-proxy-sshd is running on the engine. Presently I just cannot connect via port 2222. I have never been able to connect via serial console and require help connecting, pretty sure its due to not using the right key/cert .. I have tried to follow something like this -> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/... i.e I created a serialconsole key - added to my user in Ovirt UI (as my user 'mcox') however if I try # ssh -t -i /home/mcox/.ssh/ -p 2222 ng2-ovirt-mgmt1 -l ovirt-vmconsole I get ovirt-vmconsole(a)10.168.69.200: Permission denied (publickey). I get in ovirt-vmconsole-proxy-sshd logs "May 10 15:54:37 ng2-ovirt-mgmt1 ovirt-vmconsole[301584]: 2023-05-10 15:54:37,221+0000 ovirt-vmconsole-list: ERROR main:265 Error: <urlopen error [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:897)> May 10 15:54:37 ng2-ovirt-mgmt1 ovirt-vmconsole-proxy-keys[301580]: ERROR Key list execution failed rc=1 May 10 15:54:37 ng2-ovirt-mgmt1 sshd[301578]: AuthorizedKeysCommand /usr/libexec/ovirt-vmconsole-proxy-keys ovirt-vmconsole failed, status 1 May 10 15:54:37 ng2-ovirt-mgmt1 ovirt-vmconsole[301589]: 2023-05-10 15:54:37,543+0000 ovirt-vmconsole-list: ERROR main:265 Error: <urlopen error [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:897)> May 10 15:54:37 ng2-ovirt-mgmt1 ovirt-vmconsole-proxy-keys[301585]: ERROR Key list execution failed rc=1 May 10 15:54:37 ng2-ovirt-mgmt1 sshd[301578]: AuthorizedKeysCommand /usr/libexec/ovirt-vmconsole-proxy-keys ovirt-vmconsole failed, status 1 May 10 15:54:37 ng2-ovirt-mgmt1 sshd[301578]: Connection closed by authenticating user ovirt-vmconsole 10.88.1.105 port 52858 [preauth]" Am I using the right key ? I have tried to troubleshoot this - if I use # /usr/libexec/ovirt-vmconsole-proxy-keys list ERROR: Internal error If it helps here is : /usr/share/ovirt-vmconsole/ovirt-vmconsole-proxy/ovirt-vmconsole-proxy-sshd/sshd_config ------------ AllowAgentForwarding no #AllowStreamLocalForwarding no AllowTcpForwarding no AllowUsers ovirt-vmconsole AuthorizedKeysCommand /usr/libexec/ovirt-vmconsole-proxy-keys AuthorizedKeysCommandUser ovirt-vmconsole ChallengeResponseAuthentication no ClientAliveCountMax 3 ClientAliveInterval 10 GSSAPIAuthentication no HostCertificate /etc/pki/ovirt-vmconsole/proxy-ssh_host_rsa-cert.pub HostKey /etc/pki/ovirt-vmconsole/proxy-ssh_host_rsa HostbasedAuthentication no KbdInteractiveAuthentication no KerberosAuthentication no PasswordAuthentication no #PermitUserRC no PidFile /dev/null Port 2222 Protocol 2 PubkeyAuthentication yes TrustedUserCAKeys /etc/pki/ovirt-vmconsole/ca.pub X11Forwarding no ------------

2 years

1
0
0 / 0

no snapshot function in VM portal

by Christoph Köhler

Hi! On a fresh Version 4.5.4-1.el8: in the vm portal are no snapshot operations possible - not for an user_vm_manager and not for a super_user. We have imported VMs from 4.3 with exisiting snapshots. These are listed for the users in the snapshot box but there is also no operation possible for them. Does anyone has a hint? Greetings! Chris

2 years

2
3
0 / 0

Ovirt node disk broken

by marcel d'heureuse

Hi all, On a single Server the node disk is broken and I have to replace it. The glusterfs configuration is also gone but the glusterfs directorys are existing on a separate available disk. Did I have a Chance to install the ovirt Node on a New disk and make the old glusterfs running and also the 7 vms included the hosted engine? I can also deploy a New hosted engine but can I than import the existing gluster disk from the old Installation? I have installed the node and also mount the gluster_bricks but to make the volumes available I have not found any command. It is an ovirt 4.3.10 Installation. Is there any chance to save some time. The data inside the vms are good to have. Br Marcel

2 years

2
1
0 / 0

hosted setup failed with error on 'Initialize lockspace volume'

by destfinal＠googlemail.com

Hi, I am trying to perform a self hosted ovirt cluster. All goes well and towards the end the setup fails at the task 'Initialize lockspace volume' with the following error message: { "attempts":5, "changed":true, "cmd":[ "hosted-engine", "--reinitialize-lockspace", "--force" ], "delta":"0:00:00.108243", "end":"2023-05-03 22:50:53.930482", "msg":"non-zero return code", "rc":1, "start":"2023-05-03 22:50:53.822239", "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/python3.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_storage()\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 return 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/py thon3.9/xmlrpc/client.py\", line 1166, in request\n return self.single_request(host, handler, request_body, verbose)\n File \"/usr/lib64/python3.9/xmlrpc/client.py\", line 1178, in single_request\n http_conn = self.send_request(host, handler, request_body, verbose)\n File \"/usr/lib64/python3.9/xmlrpc/client.py\", line 1291, in send_request\n self.send_content(connection, request_body)\n File \"/usr/lib64/python3.9/xmlrpc/client.py\", line 1321, in send_content\n connection.endheaders(request_body)\n File \"/usr/lib64/python3.9/http/client.py\", line 1280, in endheaders\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/client.py\", line 980, in send\n self.connect()\n File \"/usr/lib/python3.9/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py\", line 76, in connect\n self.sock.connect(base64.b16decode(self.host ))\nFileNotFoundError: [Errno 2] No such file or directory", "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_globals, None,", " File \"/usr/lib64/python3.9/runpy.py\", line 87, in _run_code", " exec(code, run_globals)", " File \"/usr/lib/python3.9/site-packages/ovirt_hosted_engine_setup/reinitialize_lockspace.py\", line 30, in <module>", " ha_cli.reset_lockspace(force)", " File \"/usr/lib/python3.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/python3.9/xmlrpc/client.py\", line 1166, in request", " return self.single_request(host, handler, request_body, verbose)", " File \"/usr/lib64/python3.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/python3.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.b16decode(self.host))", "FileNotFoundError: [Errno 2] No such file or directory" ], "stdout":"", "stdout_lines":[ ] } The underlying storage is NFS on top of Ceph (which is not listed in the ovirt documentation). Does this ring any bell to anybody? Please let me know if you need more information in this regard or contents from any of the log files. Thanks

2 years

2
2
0 / 0

Unable to change the admin passsword on oVirt 4.5.2.5

by Ayansh Rocks

Hi All, Any idea hot to change password of admin user on oVirt 4.5.2.5 ? Below is not working - [root@ovirt]# ovirt-aaa-jdbc-tool user password-reset admin Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false Password: Reenter password: updating user admin... user updated successfully [root@delhi-test-ovirtm-02 ~]# Above shows successful but password not changed. Thanks

2 years

5
7
0 / 0

Illegal Disk after Removing Snapshot

by Nur Imam Febrianto

Hi, Using ovirt 4.5.4 with all CentOS 8 Stream Host. Having an issue, whenever we tried to delete any snapshot of any vm, it will failed. Second try will get us succeed. But if the snapshot already deleted, and we shutdown the VM, we cannot turned it on again. It showing illegal disk error. Any idea about this issue ? Thanks. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

2 years

1
0
0 / 0

cannot update expired engine certificates?

by michael.d1.holt＠lmco.com

ovirt 4.4.10.x, using self signed certificates with a self hosted engine. apache certs expired, renewed manually via guides provided by RHEL and oVirt using the pki_enroll_pkcs12.sh script. Engine certs are also expired and cannot update certs via gui and no option to renew the certs when running using engine-setup --offline. The error I am getting is a VDSM certificate error on the hosted engine in the engine.log file. I have attempted to manually run the pki_enroll_pkcs12.sh script with "engine" in the name and the subject of the previous engine.cer file with no luck. I copied the p12, key and cert from that attempt into the engine.cer, engine.p12 and engine_id_rsa files, but when booting the hosted engine VM, the first error in the engine.log is "VDC cannot find the engine certificate". This also breaks my access to the web interface for oVirt administration. When the expired engine certs are restored, I have GUI access but still see the VDSM errors on the ovirt-engine. That I hav e web access with the expired engine certs indicate to me that the apache certificates are correct (but i could be wrong in that evaluation). Basically i am looking for a way to either force the enroll pki option in the engine-setup --offline script or manually generate and update the engine.cer, engine.p12 (and if needed, but i couldn't determine where it was used) the engine_id_rsa key.

2 years

2
1
0 / 0

Remove role AdminReadOnly from Everyone group that has made my admin readonly

by robert.r.bristow＠outlook.com

We accidently added AdminReadOnly to users and has now made admin read only. Please does some one know how we can remove that to get the system back in Ovirt engine. I found the following but with being new and links not working it does not help much. Regards Rob

2 years

1
0
0 / 0

Ovirt CSI driver

by Nathanaël Blanchet

Hello, According to https://docs.openshift.com/container-platform/4.11/storage/container_stor... Ovirt CSI driver doesn't support snapshots. This is annoying because we can't backup Persistent Volume. Is there a technical reason for that? Can we hope any development for this?

2 years

1
0
0 / 0

GlusterFS+Virt

by antony.parkin＠graidtech.com

Hi, Could somebody comment on storage options i.e Gluster or Ceph and when to use each one? Looking for an architecture which is fully redundant, both at the hypervisor level and at the storage level so needs to include data replication. thx

2 years

1
0
0 / 0

VDSM certs expired, manual renewal not working

by cen

Hi Our VDSM certs have expired, both hosts are unassigned and can't be put into maintenance from UI. vdsm-client is not working, times out even with --insecure flag. Does host and port need to be specified when run locally or should defaults work? Error in console events is: Get Host Capabilities Failed: PKIX path validation failed... I followed a RHV guide for this exact situation and generated new vdsm certificate using the ovirt-engine CA. The new cert seems identical to the old one, everything matches (algos, extensions, CA, CN, SAN etc) just new date. After restarting libvirtd and vdsmd on the host with new cert in place the host is still not reachable. However, error message is now slightly different: get Host Capabilities failed: Received fatal error: certificate_expired Cert was replaced in the following locations: /etc/pki/vdsm/certs/vdsmcert.pem /etc/pki/vdsm/libvirt-spice/server-cert.pem /etc/pki/libvirt/clientcert.pem Is there another location missing? What else can I try? All help appreciated in advance

2 years

3
6
0 / 0

ovirt 4.5.4 install failure

by Selçuk N

Hello all, I tried to install ovirt 4.5.4 on ovirt node install. *hosted-engine --deploy* After this step installation is stuck. *[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up]* I checked the log file and details below. Apr 20 22:10:18 ovirt3 ansible-async_wrapper.py[41856]: 41857 still running (85405) Apr 20 22:10:19 ovirt3 python3[51367]: ansible-ovirt_host_info Invoked with pattern=name=ovirt3.44c.net auth={'token': 'eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJOTXdyenhDY284eERxZVlLaFRhWG5xblVpV0lFNDVBM2VmRzhXdndTaDVBIn0.eyJleHAiOjE2ODIwMzQzNzgsImlhdCI6MTY4MjAxNzA5OCwianRpIjoiODdjNDAwZTItNDZiMS00NmY1LTk2MWMtMWJhMDA3MDAxOGQxIiwiaXNzIjoiaHR0cHM6Ly9lbmcuNDRjLm5ldC9vdmlydC1lbmdpbmUtYXV0aC9yZWFsbXMvb3ZpcnQtaW50ZXJuYWwiLCJhdWQiOiJhY2NvdW50Iiwic3ViIjoiZmFiMDNmM2UtODVmZS00YjQ5LWE5ZWItZTExODRjOTYzYzdjIiwidHlwIjoiQmVhcmVyIiwiYXpwIjoib3ZpcnQtZW5naW5lLWludGVybmFsIiwic2Vzc2lvbl9zdGF0ZSI6IjYwOWJiMmMxLTJkNTItNDc4Zi1hYzg2LWMyMjVlNTVmYTMwNyIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cHM6Ly9lbmcuNDRjLm5ldCJdLCJyZWFsbV9hY2Nlc3MiOnsicm9sZXMiOlsiZGVmYXVsdC1yb2xlcy1vdmlydC1pbnRlcm5hbCIsIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iXX0sInJlc291cmNlX2FjY2VzcyI6eyJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6Im92aXJ0LWFwcC1hcGkgZW1haWwgb3ZpcnQtZXh0PXRva2VuLWluZm86YXV0aHotc2VhcmNoIG92aXJ0LWV4dD10b2tlbi1pbmZvOnZhbGlkYXRlIG92aXJ0LWV4dD10b2tlbi1pbmZvOnB1YmxpYy1hdXRoei1zZWFyY2ggcHJvZmlsZSBvdmlydC1leHQ9dG9rZW46cGFzc3dvcmQtYWNjZXNzIiwic2lkIjoiNjA5YmIyYzEtMmQ1Mi00NzhmLWFjODYtYzIyNWU1NWZhMzA3IiwiZW1haWxfdmVyaWZpZWQiOmZhbHNlLCJncm91cHMiOlsiL292aXJ0LWFkbWluaXN0cmF0b3IiXSwicHJlZmVycmVkX3VzZXJuYW1lIjoiYWRtaW5Ab3ZpcnQiLCJlbWFpbCI6ImFkbWluQGxvY2FsaG9zdCJ9.e47PgAtt_Sj-_4IQ8OIQynAV_AvrOfzalhwi1VJapCQB_sdQqxd0jIH7JGVM1a4TGEJb6E5ffTXBocqQabe5pBPIv4kqsgU1iadyTjjDjZ1elECnahPf6lrze-8hEO92GKFOepGLQ-iu7gRilAknvaXhoc309G1hyQvnP4Q-syffw6Eoo4RmgnLnztnPzsxBtGgkZrzAwFfTNDtdS2uj5lvzzAEIfvDPRFTjJhYwKXSx2hC1lnhXnmv1XEtCfXZZ3qqarXw8GAvOQbe10xklm5UAtu--C8NX32DE6659QtEqk-5g52SdFWIic_OlZ5-obHn3jOllo8qnsb-6mfEn_w', 'url': 'https://eng.44c.net/ovirt-engine/api', 'ca_file': None, 'insecure': True, 'timeout': 0, 'compress': True, 'kerberos': False, 'headers': None, 'hostname': None, 'username': None, 'password': None} fetch_nested=False nested_attributes=[] follow=[] all_content=False cluster_version=None *Apr 20 22:10:22 ovirt3 journal[47971]: Invalid value '-1' for 'cpu.max': Invalid argument* Apr 20 22:10:23 ovirt3 sssd_kcm[50811]: Shutting down (status = 0) Apr 20 22:10:23 ovirt3 systemd[1]: sssd-kcm.service: Deactivated successfully. Apr 20 22:10:23 ovirt3 ansible-async_wrapper.py[41856]: 41857 still running (85400) Apr 20 22:10:28 ovirt3 ansible-async_wrapper.py[41856]: 41857 still running (85395) What did I did wrong? Thanks.

2 years

2
1
0 / 0

checking engine vm status during global maintenance

by Alexey Valkov

Hi all, I tried to check engine status (via hosted-engine --vm-status) during global maintenance in oVirt 4.5.1 and discovered that it showed me status as it was just before entering global maintenance. Is it by design? And HA agent doesn't monitor and therefore doesn't update Engine VM status? If I remember right in oVirt 4.2 hosted-engine --vm-status showed correct status of Engine VM regardless of Global maintenance. I shutted down the engine but the output of hosted-engine --vm-status was Engine status : {"vm": "up", "health": "good", "detail": "Up"} Notice !! Cluster is in GLOBAL MAINTENANCE mode !! existed in the output. Host timestamp and extra metadata was up to date. All rest info looked good. Thi is my second attempt to ask the question (first was at 24/04 and still is being moderated). -- Best regards Alexei

2 years

2
1
0 / 0

richiesta accesso Zanata

by Rosario Grasso

Buongiorno, la presente per richiedere l'accesso a Zanata in lingua inglese e se possibile anche in italiano. Saluti, RG

2 years

2
2
0 / 0

Disable SSL for ovirt-ha-broker?

by phil.gardnerjr＠gmail.com

I have a neglected oVirt 4.3 cluster that consists of two hosts with a hosted engine. Unfortunately, the host SSL certificates on both hosts are expired, and now the hosted engine is down from a power loss event. I don't see a way to get ovirt-ha-broker functioning again if the vdsm certificates are expired, since I can't get the hosted engine VM to start in order to generate new host certificates. My sledgehammer approach was to just disable SSL in the configuration for vdsm and libvirt, but I can't seem to figure out how to disable SSL for ovirt-ha-broker. Is this possible? I don't know what else to try. I figure if I can just get the hosted-engine back up, and I can maybe proceed with getting one of the hosts back up and functional in some way, and maybe getting the single VM that I am concerned about started up. If the hosted engine isn't recoverable, is it possible to get another VM up and running with just standard kvm/libvirt/virsh if I still have access to the storage?

2 years

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users May 2023