November 2020 - Users - oVirt List Archives

Restart oVirt-Engine
by Jeremey Wise 09 Jan '25

09 Jan '25

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

4 4

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

22 Nov '24

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

5 15

Changing disk QoS causes segfault with IO-Threads enabled (oVirt 4.3.0.4-1.el7)
by jloh＠squiz.net 23 Apr '24

23 Apr '24

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.

4 3

Deploy oVirt Engine fail behind proxy
by Matteo Bonardi 21 Mar '24

21 Mar '24

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=st… [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

7 20

Unable to install oVirt on RHEL7.5
by SS00514758＠techmahindra.com 05 Jan '24

05 Jan '24

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

6 8

Re: Failed to synchronize networks of Provider ovirt-provider-ovn
by Mail SET Inc. Group 27 Oct '23

27 Oct '23

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/ht… > > 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 >>> >> > >

5 13

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

17 Jul '23

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

4 6

oVirt host deploy: disable multipath
by femi adegoke 27 Mar '23

27 Mar '23

https://bugzilla.redhat.com/show_bug.cgi?id=1472356 There are 2 drives in my install that oVirt is claiming as multipath. I have tried blacklisting at /etc/multipath/ but that hasn't worked. Any better solutions? I need these 2 drives to be non-multipathed.

4 19

Out-of-sync networks can only be detached
by Sakhi Hadebe 26 Feb '23

26 Feb '23

Hi, I have a 3-node oVirt cluster. I have configured 2 logical networks: ovirtmgmt and public. Public logical network is attached in only 2 nodes and failing to attach on the 3rd node with the below error Invalid operation, out-of-sync network 'public' can only be detached. Please have been stuck on this for almost the whole day now. How do I fix this error? -- Regards, Sakhi Hadebe

3 5

Network Address Change
by Paul.LKW 28 Dec '22

28 Dec '22

Hi All: I just has a case, I need to change the oVirt host and engine IP address due to data center decommission I checked in the hosted-engine host there are some files I could change ; in ovirt-hosted-engine/hosted-engine.conf ca_subject="O=simple.com, CN=1.2.3.4" gateway=1.2.3.254 and of course I need to change the ovirtmgmt interface IP too, I think just change the above line could do the tick, but where could I change the other host IP in the cluster ? I think I have to be lost all the host as once changed the hosted-engine host IP as it is in diff. sub net. Does there any command line tools could do that or someone has such experience could share? Best Regards, Paul.LKW

4 6

looking for some ISV backup software which integrates the backup API
by Nathanaël Blanchet 08 Jun '22

08 Jun '22

Hello, We are about to change our backup provider, and I find it is a great chance to choose a full supported ovirt backup solution. I currently use this python script vm-backup-scheduler (https://github.com/wefixit-AT/oVirtBackup) but it is not the workflow officially suggested by the community (https://www.ovirt.org/develop/release-management/features/storage/backup-re…) I've been looking for a long time an ISV who supports such an API, but the only one I found is this one : Acronis Backup Advanced suggested here https://access.redhat.com/ecosystem/search/#/ecosystem/Red%20Hat%20Enterpri… I ran the trial version, but it doesn't seem to do better than the vm-backup-scheduler script, and it doesn't seem to use the backup API (attach a clone as a disk to an existing vm). Can you suggest me some other ISV solutions, if they ever exist... or share me your backup experience?

5 4

VM HostedEngine is down with error
by souvaliotimaria＠mail.com 26 May '22

26 May '22

Hello everyone, I have a replica 2 + arbiter installation and this morning the Hosted Engine gave the following error on the UI and resumed on a different node (node3) than the one it was originally running(node1). (The original node has more memory than the one it ended up, but it had a better memory usage percentage at the time). Also, the only way I discovered the migration had happened and there was an Error in Events, was because I logged in the web interface of ovirt for a routine inspection. Βesides that, everything was working properly and still is. The error that popped is the following: VM HostedEngine is down with error. Exit message: internal error: qemu unexpectedly closed the monitor: 2020-09-01T06:49:20.749126Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config, ability to start up with partial NUMA mappings is obsoleted and will be removed in future 2020-09-01T06:49:20.927274Z qemu-kvm: -device virtio-blk-pci,iothread=iothread1,scsi=off,bus=pci.0,addr=0x7,drive=drive-ua-d5de54b6-9f8e-4fba-819b-ebf6780757d2,id=ua-d5de54b6-9f8e-4fba-819b-ebf6780757d2,bootindex=1,write-cache=on: Failed to get "write" lock Is another process using the image?. Which from what I could gather concerns the following snippet from the HostedEngine.xml and it's the virtio disk of the Hosted Engine: <disk type='file' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='threads' iothread='1'/> <source file='/var/run/vdsm/storage/80f6e393-9718-4738-a14a-64cf43c3d8c2/d5de54b6-9f8e-4fba-819b-ebf6780757d2/a48555f4-be23-4467-8a54-400ae7baf9d7'> <seclabel model='dac' relabel='no'/> </source> <target dev='vda' bus='virtio'/> <serial>d5de54b6-9f8e-4fba-819b-ebf6780757d2</serial> <alias name='ua-d5de54b6-9f8e-4fba-819b-ebf6780757d2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> I've tried looking into the logs and the sar command but I couldn't find anything to relate with the above errors and determining the reason for it to happen. Is this a Gluster or a QEMU problem? The Hosted Engine was manually migrated five days before on node1. Is there a standard practice I could follow to determine what happened and secure my system? Thank you very much for your time, Maria Souvalioti

4 6

OVS switch type for hosted-engine
by Devin A. Bougie 06 May '22

06 May '22

Is it possible to setup a hosted engine using the OVS switch type instead of Legacy? If it's not possible to start out as OVS, instructions for switching from Legacy to OVS after the fact would be greatly appreciated. Many thanks, Devin

4 5

USB3 redirection
by Rik Theys 19 Apr '22

19 Apr '22

Hi, I'm trying to assign a USB3 controller to a CentOS 7.4 VM in oVirt 4.1 with USB redirection enabled. I've created the following file in /etc/ovirt-engine/osinfo.conf.d: 01-usb.properties with content os.other.devices.usb.controller.value = nec-xhci and have restarted ovirt-engine. If I disable USB-support in the web interface for the VM, the xhci controller is added to the VM (I can see it in the qemu-kvm commandline), but usb redirection is not available. If I enable USB-support in the UI, no xhci controller is added (only 4 uhci controllers). Is there a way to make the controllers for usb redirection xhci controllers? Regards, Rik -- Rik Theys System Engineer KU Leuven - Dept. Elektrotechniek (ESAT) Kasteelpark Arenberg 10 bus 2440 - B-3001 Leuven-Heverlee +32(0)16/32.11.07 ---------------------------------------------------------------- <<Any errors in spelling, tact or fact are transmission errors>>

3 5

OVN routing and firewalling in oVirt
by Gianluca Cecchi 19 Apr '22

19 Apr '22

Hello, how do we manage routing between different OVN networks in oVirt? And between OVN networks and physical ones? Based on architecture read here: http://openvswitch.org/support/dist-docs/ovn-architecture.7.html I see terms for logical routers and gateway routers respectively but how to apply to oVirt configuration? Do I have to choose between setting up a specialized VM or a physical one: is it applicable/advisable to put on oVirt host itself the gateway functionality? Is there any security policy (like security groups in Openstack) to implement? Thanks, Gianluca

4 6

Install hosted-engine - Task Get local VM IP failed
by florentl 10 Mar '22

10 Mar '22

Hi all, I try to install hosted-engine on node : ovirt-node-ng-4.2.3-0.20180518. Every times I get stuck on : [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": true, "cmd": "virsh -r net-dhcp-leases default | grep -i 00:16:3e:6c:5a:91 | awk '{ print $5 }' | cut -f1 -d'/'", "delta": "0:00:00.108872", "end": "2018-06-01 11:17:34.421769", "rc": 0, "start": "2018-06-01 11:17:34.312897", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} I tried with static IP Address and with DHCP but both failed. To be more specific, I installed three nodes, deployed glusterfs with the wizard. I'm in a nested virtualization environment for this lab (Vmware Esxi Hypervisor). My node IP is : 192.168.176.40 / and I want the hosted-engine vm has 192.168.176.43. Thanks, Florent

7 17

Host needs to be reinstalled after configuring power management
by Andrew DeMaria 02 Feb '22

02 Feb '22

Hi, I am running ovirt 4.3 and have found the following action item immediately after configuring power management for a host: Host needs to be reinstalled as important configuration changes were applied on it. The thing is - I've just freshly installed this host and it seems strange that I need to reinstall it. Is there a better way to install a host and configure power management without having to reinstall it after? Thanks, Andrew

4 3

Import an exported VM using Ansible
by paolo＠airaldi.it 25 Jan '22

25 Jan '22

Hello everybody! I'm trying to automate a copy of a VM from one Datacenter to another using an Ansible.playbook. I'm able to: - Create a snapshot of the source VM - create a clone from the snapshot - remove the snapshot - attach an Export Domain - export the clone to the Export Domain - remove the clone - detach the Export domain from the source Datacenter and attach to the destination. Unfortunately I cannot find a module to: - import the VM from the Export Domain - delete the VM image from the Export Domain. Any hint on how to do that? Thanks in advance. Cheers. Paolo PS: if someone is interested I can share the playbook.

4 3

did 4.3.9 reset bug https://bugzilla.redhat.com/show_bug.cgi?id=1590266
by kelley bryan 10 Jan '22

10 Jan '22

I am experiencing the error message in the ovirt-hosted-engine-setup-ansible-create_target_vm log {2020-05-06 14:15:30,024-0500 ERROR ansible failed {'status': 'FAILED', 'ansible_type': 'task', 'ansible_task': u"Fail if Engine IP is different from engine's he_fqdn resolved IP", 'ansible_result': u'type: <type \'dict\'>\nstr: {\'msg\': u"Engine VM IP address is while the engine\'s he_fqdn ovirt1-engine.kelleykars.org resolves to 192.168.122.2. If you are using DHCP, check your DHCP reservation configuration", \'changed\': False, \'_ansible_no_log\': False}', 'task_duration': 1, 'ansible_host': u'localhost', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml'}}:Q! The bug 1590266 says it should report the engine VM IP address xxx.xxx.xxx.xxx while the Engines he_fqdn is xxxxxxxxx I need to see what it thins is wrong as both dig fqdn engine name and dig -x ip return the correct information. Now this bug looks like it may play but I don't see the failed rediness check in the this log https://access.redhat.com/solutions/4462431 or is it because the vm fails or dies or ???

3 7

Lots of storage.MailBox.SpmMailMonitor
by Fabrice Bacchella 06 Jan '22

06 Jan '22

My vdsm log files are huge: -rw-r--r-- 1 vdsm kvm 1.8G Nov 22 11:32 vdsm.log And this is juste half an hour of logs: $ head -1 vdsm.log 2018-11-22 11:01:12,132+0100 ERROR (mailbox-spm) [storage.MailBox.SpmMailMonitor] mailbox 2 checksum failed, not clearing mailbox, clearing new mail (data='...lots of data', expected='\xa4\x06\x08\x00') (mailbox:612) I just upgraded vdsm: $ rpm -qi vdsm Name : vdsm Version : 4.20.43

3 5

Snapshot and disk size allocation
by jorgevisentini＠gmail.com 28 Oct '21

28 Oct '21

Hello everyone. I would like to know how disk size and snapshot allocation works, because every time I create a new snapshot, it increases 1 GB in the VM's disk size, and when I remove the snap, that space is not returned to Domain Storage. I'm using the oVirt 4.3.10 How do I reprovision the VM disk? Thank you all.

5 7

How to renew an Ovirt host certificate (vdsmcert.pem) ?
by noua.toukourou＠uni.lu 19 Sep '21

19 Sep '21

Hi, I have an Ovirt host that the vdsmcert.pem expired. The problem is that host contains the self-hosted engine. How to renew the certificate without breaking the self-hosted engine ? Thanks,

3 3

oVirt 4.3 DWH with Grafana
by Vrgotic, Marko 14 Sep '21

14 Sep '21

Dear oVirt, We are currently running oVirt 4.3 and upgrade/migration to 4.4 won’t be possible for few more months. I am looking into guidelines, how to, for setting up Grafana using DataWarehouse as data source. Did anyone already did this, and would be willing to share the steps? Kindly awaiting your reply. ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message.

8 11

Template for Ubuntu 18.04 Server Issues
by jeremy_tourville＠hotmail.com 02 Sep '21

02 Sep '21

I have built a system as a template on oVirt. Specifically, Ubuntu 18.04 server. I am noticing an issue when creating new vms from that template. I used the check box for "seal template" when creating the template. When I create a new Ubuntu VM I am getting duplicate IP addresses for all the machines created from the template. It seems like the checkbox doesn't fully function as intended. I would need to do further manual steps to clear up this issue. Has anyone else noticed this behavior? Is this expected or have I missed something? Thanks for your input!

6 7

Libgfapi considerations
by Jayme 01 Jul '21

01 Jul '21

Are there currently any known issues with using libgfapi in the latest stable version of ovirt in hci deployments? I have recently enabled it and have noticed a significant (over 4x) increase in io performance on my vms. I’m concerned however since it does not seem to be an ovirt default setting. Is libgfapi considered safe and stable to use in ovirt 4.3 hci?

9 16

Re: Parent checkpoint ID does not match the actual leaf checkpoint
by Nir Soffer 27 May '21

27 May '21

On Sun, Jul 19, 2020 at 5:38 PM Łukasz Kołaciński <l.kolacinski(a)storware.eu> wrote: > Hello, > Thanks to previous answers, I was able to make backups. Unfortunately, we > had some infrastructure issues and after the host reboots new problems > appeared. I am not able to do any backup using the commands that worked > yesterday. I looked through the logs and there is something like this: > > 2020-07-17 15:06:30,644+02 ERROR > [org.ovirt.engine.core.bll.StartVmBackupCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-54) > [944a1447-4ea5-4a1c-b971-0bc612b6e45e] Failed to execute VM backup > operation 'StartVmBackup': {}: > org.ovirt.engine.core.common.errors.EngineException: EngineException: > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: > VDSGenericException: VDSErrorException: Failed to StartVmBackupVDS, error = > Checkpoint Error: {'parent_checkpoint_id': None, 'leaf_checkpoint_id': > 'cd078706-84c0-4370-a6ec-654ccd6a21aa', 'vm_id': > '116aa6eb-31a1-43db-9b1e-ad6e32fb9260', 'reason': '*Parent checkpoint ID > does not match the actual leaf checkpoint*'}, code = 1610 (Failed with > error unexpected and code 16) > > It looks like engine sent: parent_checkpoint_id: None This issue was fix in engine few weeks ago. Which engine and vdsm versions are you testing? > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:114) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.runVdsCommand(VDSBrokerFrontendImpl.java:33) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.runVdsCommand(CommandBase.java:2114) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.StartVmBackupCommand.performVmBackupOperation(StartVmBackupCommand.java:368) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.StartVmBackupCommand.runVmBackup(StartVmBackupCommand.java:225) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.StartVmBackupCommand.performNextOperation(StartVmBackupCommand.java:199) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback.childCommandsExecutionEnded(SerialChildCommandsExecutionCallback.java:32) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.ChildCommandsCallbackBase.doPolling(ChildCommandsCallbackBase.java:80) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:175) > at > deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:109) > at > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > at > java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) > at > org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383) > at > org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534) > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > at > org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) > > > And the last error is: > > 2020-07-17 15:13:45,835+02 ERROR > [org.ovirt.engine.core.bll.StartVmBackupCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-14) > [f553c1f2-1c99-4118-9365-ba6b862da936] Failed to execute VM backup > operation 'GetVmBackupInfo': {}: > org.ovirt.engine.core.common.errors.EngineException: EngineException: > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: > VDSGenericException: VDSErrorException: Failed to GetVmBackupInfoVDS, error > = No such backup Error: {'vm_id': '116aa6eb-31a1-43db-9b1e-ad6e32fb9260', > 'backup_id': 'bf1c26f7-c3e5-437c-bb5a-255b8c1b3b73', 'reason': '*VM > backup not exists: Domain backup job id not found: no domain backup job > present'*}, code = 1601 (Failed with error unexpected and code 16) > > This is likely a result of the first error. If starting backup failed the backup entity is deleted. > (these errors are from full backup) > > Like I said this is very strange because everything was working correctly. > > > Regards > > Łukasz Kołaciński > > Junior Java Developer > > e-mail: l.kolacinski(a)storware.eu > <m.helbert(a)storware.eu> > > > > > *[image: STORWARE]* <http://www.storware.eu/> > > > > *ul. Leszno 8/44 01-192 Warszawa www.storware.eu > <https://www.storware.eu/>* > > *[image: facebook]* <https://www.facebook.com/storware> > > *[image: twitter]* <https://twitter.com/storware> > > *[image: linkedin]* <https://www.linkedin.com/company/storware> > > *[image: Storware_Stopka_09]* > <https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw> > > > > *Storware Spółka z o.o. nr wpisu do ewidencji KRS dla M.St. Warszawa > 000510131* *, NIP 5213672602.** Wiadomość ta jest przeznaczona jedynie > dla osoby lub podmiotu, który jest jej adresatem i może zawierać poufne > i/lub uprzywilejowane informacje. Zakazane jest jakiekolwiek przeglądanie, > przesyłanie, rozpowszechnianie lub inne wykorzystanie tych informacji lub > podjęcie jakichkolwiek działań odnośnie tych informacji przez osoby lub > podmioty inne niż zamierzony adresat. Jeżeli Państwo otrzymali przez > pomyłkę tę informację prosimy o poinformowanie o tym nadawcy i usunięcie > tej wiadomości z wszelkich komputerów. **This message is intended only > for the person or entity to which it is addressed and may contain > confidential and/or privileged material. Any review, retransmission, > dissemination or other use of, or taking of any action in reliance upon, > this information by persons or entities other than the intended recipient > is prohibited. If you have received this message in error, please contact > the sender and remove the material from all of your computer systems.* > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/S3PLYPOZGT6TL… >

3 4

poweroff and reboot with ovirt_vm ansible module
by Nathanaël Blanchet 18 May '21

18 May '21

Hello, is there a way to poweroff or reboot (without stopped and running state) a vm with the ovirt_vm ansible module? -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

7 11

supervdsm failing during network_caps
by Alan G 24 Mar '21

24 Mar '21

Hi, I have issues with one host where supervdsm is failing in network_caps. I see the following trace in the log. MainProcess|jsonrpc/1::ERROR::2020-01-06 03:01:05,558::supervdsm_server::100::SuperVdsm.ServerCallback::(wrapper) Error in network_caps Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_server.py", line 98, in wrapper res = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 56, in network_caps return netswitch.configurator.netcaps(compatibility=30600) File "/usr/lib/python2.7/site-packages/vdsm/network/netswitch/configurator.py", line 317, in netcaps net_caps = netinfo(compatibility=compatibility) File "/usr/lib/python2.7/site-packages/vdsm/network/netswitch/configurator.py", line 325, in netinfo _netinfo = netinfo_get(vdsmnets, compatibility) File "/usr/lib/python2.7/site-packages/vdsm/network/netinfo/cache.py", line 150, in get return _stringify_mtus(_get(vdsmnets)) File "/usr/lib/python2.7/site-packages/vdsm/network/netinfo/cache.py", line 59, in _get ipaddrs = getIpAddrs() File "/usr/lib/python2.7/site-packages/vdsm/network/netinfo/addresses.py", line 72, in getIpAddrs for addr in nl_addr.iter_addrs(): File "/usr/lib/python2.7/site-packages/vdsm/network/netlink/addr.py", line 33, in iter_addrs with _nl_addr_cache(sock) as addr_cache: File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ return self.gen.next() File "/usr/lib/python2.7/site-packages/vdsm/network/netlink/__init__.py", line 92, in _cache_manager cache = cache_allocator(sock) File "/usr/lib/python2.7/site-packages/vdsm/network/netlink/libnl.py", line 469, in rtnl_addr_alloc_cache raise IOError(-err, nl_geterror(err)) IOError: [Errno 16] Message sequence number mismatch A restart of supervdsm will resolve the issue for a period, maybe 24 hours, then it will occur again. So I'm thinking it's resource exhaustion or a leak of some kind? Running 4.2.8.2 with VDSM at 4.20.46. I've had a look through the bugzilla and can't find an exact match, closest was this one https://bugzilla.redhat.com/show_bug.cgi?id=1666123 which seems to be a RHV only fix. Thanks, Alan

2 3

Gluster volume slower then raid1 zpool speed
by Harry O 28 Jan '21

28 Jan '21

Hi, Can anyone help me with the performance on my 3 node gluster on zfs (it is setup with one arbiter) The performance on the single vm I have on it (with engine) is 50% worse then a single bare metal disk, on the writes. I have enabled "Optimize for virt store" I run 1Gbps 1500MTU network, could this be the write performance killer? Is this to be expected from a 2xHDD zfs raid one on each node, with 3xNode arbiter setup? Maybe I should move to raid 5 or 6? Maybe I should add SSD cache to raid1 zfs zpools? What are your thoughts? What to do for optimize this setup? I would like to run zfs with gluster and I can deal with a little performance loss, but not that much.

5 13

OVN and change of mgmt network
by Gianluca Cecchi 26 Jan '21

26 Jan '21

Hello, I previously had OVN running on engine (as OVN provider with northd and northbound and southbound DBs) and hosts (with OVN controller). After changing mgmt ip of hosts (engine has retained instead the same ip), I executed again on them the command: vdsm-tool ovn-config <ip_of_engine> <nel_local_ip_of_host> Now I think I have to clean up some things, eg: 1) On engine where I get these lines below systemctl status ovn-northd.service -l . . . Sep 29 14:41:42 ovmgr1 ovsdb-server[940]: ovs|00005|reconnect|ERR|tcp: 10.4.167.40:37272: no response to inactivity probe after 5 seconds, disconnecting Oct 03 11:52:00 ovmgr1 ovsdb-server[940]: ovs|00006|reconnect|ERR|tcp: 10.4.167.41:52078: no response to inactivity probe after 5 seconds, disconnecting The two IPs are the old ones of two hosts It seems that a restart of the services has fixed... Can anyone confirm if I have to do anything else? 2) On hosts (there are 3 hosts with OVN on ip 10.4.192.32/33/34) where I currently have this output [root@ov301 ~]# ovs-vsctl show 3a38c5bb-0abf-493d-a2e6-345af8aedfe3 Bridge br-int fail_mode: secure Port "ovn-1dce5b-0" Interface "ovn-1dce5b-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.192.32"} Port "ovn-ddecf0-0" Interface "ovn-ddecf0-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.192.33"} Port "ovn-fd413b-0" Interface "ovn-fd413b-0" type: geneve options: {csum="true", key=flow, remote_ip="10.4.168.74"} Port br-int Interface br-int type: internal ovs_version: "2.7.2" [root@ov301 ~]# The IPs of kind 10.4.192.x are ok. But there is a left-over of an old host I initially used for tests, corresponding to 10.4.168.74, that now doesn't exist anymore How can I clean records for 1) and 2)? Thanks, Gianluca

3 4

CentOS Stream support
by Michal Skrivanek 25 Jan '21

25 Jan '21

Hi all, we would like to ask about interest in community about oVirt moving to CentOS Stream. There were some requests before but it’s hard to see how many people would really like to see that. With CentOS releases lagging behind RHEL for months it’s interesting to consider moving to CentOS Stream as it is much more up to date and allows us to fix bugs faster, with less workarounds and overhead for maintaining old code. E.g. our current integration tests do not really pass on CentOS 8.1 and we can’t really do much about that other than wait for more up to date packages. It would also bring us closer to make oVirt run smoothly on RHEL as that is also much closer to Stream than it is to outdated CentOS. So..would you like us to support CentOS Stream? We don’t really have capacity to run 3 different platforms, would you still want oVirt to support CentOS Stream if it means “less support” for regular CentOS? There are some concerns about Stream being a bit less stable, do you share those concerns? Thank you for your comments, michal

5 8

encrypted GENEVE traffic
by Pavel Nakonechnyi 18 Jan '21

18 Jan '21

Dear oVirt Community, From my understanding oVirt does not support Open vSwitch IPSEC tunneling for GENEVE traffic (which is described on pages http://docs.openvswitch.org/en/latest/howto/ipsec/ and http://docs.openvswitch.org/en/latest/tutorials/ipsec/) Are there plans to introduce such support? (or explicitly not to..) Is it possible to somehow manually configure such tunneling for existing virtual networks? (even in a limited way) Alternatively, is it possible to deploy oVirt on top of the tunneled (i.e. via VXLAN, IPSec) interfaces? This will allow to encrypt all management traffic. Such requirement arises when using oVirt deployment on third-party premises with untrusted network. Thank in advance for any clarifications. :) -- WBR, Pavel +32478910884

2 7

Re: Constantly XFS in memory corruption inside VMs
by Strahil Nikolov 14 Jan '21

14 Jan '21

Damn... You are using EFI boot. Does this happen only to EFI machines ? Did you notice if only EL 8 is affected ? Best Regards, Strahil Nikolov В неделя, 29 ноември 2020 г., 19:36:09 Гринуич+2, Vinícius Ferrão <ferrao(a)versatushpc.com.br> написа: Yes! I have a live VM right now that will de dead on a reboot: [root@kontainerscomk ~]# cat /etc/*release NAME="Red Hat Enterprise Linux" VERSION="8.3 (Ootpa)" ID="rhel" ID_LIKE="fedora" VERSION_ID="8.3" PLATFORM_ID="platform:el8" PRETTY_NAME="Red Hat Enterprise Linux 8.3 (Ootpa)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:redhat:enterprise_linux:8.3:GA" HOME_URL="https://www.redhat.com/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8" REDHAT_BUGZILLA_PRODUCT_VERSION=8.3 REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux" REDHAT_SUPPORT_PRODUCT_VERSION="8.3" Red Hat Enterprise Linux release 8.3 (Ootpa) Red Hat Enterprise Linux release 8.3 (Ootpa) [root@kontainerscomk ~]# sysctl -a | grep dirty vm.dirty_background_bytes = 0 vm.dirty_background_ratio = 10 vm.dirty_bytes = 0 vm.dirty_expire_centisecs = 3000 vm.dirty_ratio = 30 vm.dirty_writeback_centisecs = 500 vm.dirtytime_expire_seconds = 43200 [root@kontainerscomk ~]# xfs_db -r /dev/dm-0 xfs_db: /dev/dm-0 is not a valid XFS filesystem (unexpected SB magic number 0xa82a0000) Use -F to force a read attempt. [root@kontainerscomk ~]# xfs_db -r /dev/dm-0 -F xfs_db: /dev/dm-0 is not a valid XFS filesystem (unexpected SB magic number 0xa82a0000) xfs_db: size check failed xfs_db: V1 inodes unsupported. Please try an older xfsprogs. [root@kontainerscomk ~]# cat /etc/fstab # # /etc/fstab # Created by anaconda on Thu Nov 19 22:40:39 2020 # # Accessible filesystems, by reference, are maintained under '/dev/disk/'. # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info. # # After editing this file, run 'systemctl daemon-reload' to update systemd # units generated from this file. # /dev/mapper/rhel-root / xfs defaults 0 0 UUID=ad84d1ea-c9cc-4b22-8338-d1a6b2c7d27e /boot xfs defaults 0 0 UUID=4642-2FF6 /boot/efi vfat umask=0077,shortname=winnt 0 2 /dev/mapper/rhel-swap none swap defaults 0 0 Thanks, -----Original Message----- From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Sunday, November 29, 2020 2:33 PM To: Vinícius Ferrão <ferrao(a)versatushpc.com.br> Cc: users <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Constantly XFS in memory corruption inside VMs Can you check the output on the VM that was affected: # cat /etc/*release # sysctl -a | grep dirty Best Regards, Strahil Nikolov В неделя, 29 ноември 2020 г., 19:07:48 Гринуич+2, Vinícius Ferrão via Users <users(a)ovirt.org> написа: Hi Strahil. I’m not using barrier options on mount. It’s the default settings from CentOS install. I have some additional findings, there’s a big number of discarded packages on the switch on the hypervisor interfaces. Discards are OK as far as I know, I hope TCP handles this and do the proper retransmissions, but I ask if this may be related or not. Our storage is over NFS. My general expertise is with iSCSI and I’ve never seen this kind of issue with iSCSI, not that I’m aware of. In other clusters, I’ve seen a high number of discards with iSCSI on XenServer 7.2 but there’s no corruption on the VMs there... Thanks, Sent from my iPhone > On 29 Nov 2020, at 04:00, Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > > Are you using "nobarrier" mount options in the VM ? > > If yes, can you try to remove the "nobarrrier" option. > > > Best Regards, > Strahil Nikolov > > > > > > > В събота, 28 ноември 2020 г., 19:25:48 Гринуич+2, Vinícius Ferrão <ferrao(a)versatushpc.com.br> написа: > > > > > > Hi Strahil, > > I moved a running VM to other host, rebooted and no corruption was found. If there's any corruption it may be silent corruption... I've cases where the VM was new, just installed, run dnf -y update to get the updated packages, rebooted, and boom XFS corruption. So perhaps the motion process isn't the one to blame. > > But, in fact, I remember when moving a VM that it went down during the process and when I rebooted it was corrupted. But this may not seems related. It perhaps was already in a inconsistent state. > > Anyway, here's the mount options: > > Host1: > 192.168.10.14:/mnt/pool0/ovirt/vm on > /rhev/data-center/mnt/192.168.10.14:_mnt_pool0_ovirt_vm type nfs4 > (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,noshar > ecache,proto=tcp,timeo=100,retrans=3,sec=sys,clientaddr=192.168.10.1,l > ocal_lock=none,addr=192.168.10.14) > > Host2: > 192.168.10.14:/mnt/pool0/ovirt/vm on > /rhev/data-center/mnt/192.168.10.14:_mnt_pool0_ovirt_vm type nfs4 > (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,noshar > ecache,proto=tcp,timeo=100,retrans=3,sec=sys,clientaddr=192.168.10.1,l > ocal_lock=none,addr=192.168.10.14) > > The options are the default ones. I haven't changed anything when configuring this cluster. > > Thanks. > > > > -----Original Message----- > From: Strahil Nikolov <hunter86_bg(a)yahoo.com> > Sent: Saturday, November 28, 2020 1:54 PM > To: users <users(a)ovirt.org>; Vinícius Ferrão > <ferrao(a)versatushpc.com.br> > Subject: Re: [ovirt-users] Constantly XFS in memory corruption inside > VMs > > Can you try with a test vm, if this happens after a Virtual Machine migration ? > > What are your mount options for the storage domain ? > > Best Regards, > Strahil Nikolov > > > > > > > В събота, 28 ноември 2020 г., 18:25:15 Гринуич+2, Vinícius Ferrão via Users <users(a)ovirt.org> написа: > > > > > > > > > Hello, > > > > I’m trying to discover why an oVirt 4.4.3 Cluster with two hosts and NFS shared storage on TrueNAS 12.0 is constantly getting XFS corruption inside the VMs. > > > > For random reasons VM’s gets corrupted, sometimes halting it or just being silent corrupted and after a reboot the system is unable to boot due to “corruption of in-memory data detected”. Sometimes the corrupted data are “all zeroes”, sometimes there’s data there. In extreme cases the XFS superblock 0 get’s corrupted and the system cannot even detect a XFS partition anymore since the magic XFS key is corrupted on the first blocks of the virtual disk. > > > > This is happening for a month now. We had to rollback some backups, and I don’t trust anymore on the state of the VMs. > > > > Using xfs_db I can see that some VM’s have corrupted superblocks but the VM is up. One in specific, was with sb0 corrupted, so I knew when a reboot kicks in the machine will be gone, and that’s exactly what happened. > > > > Another day I was just installing a new CentOS 8 VM for random reasons, and after running dnf -y update and a reboot the VM was corrupted needing XFS repair. That was an extreme case. > > > > So, I’ve looked on the TrueNAS logs, and there’s apparently nothing wrong on the system. No errors logged on dmesg, nothing on /var/log/messages and no errors on the “zpools”, not even after scrub operations. On the switch, a Catalyst 2960X, we’ve been monitoring it and all it’s interfaces. There are no “up and down” and zero errors on all interfaces (we have a 4x Port LACP on the TrueNAS side and 2x Port LACP on each hosts), everything seems to be fine. The only metric that I was unable to get is “dropped packages”, but I’m don’t know if this can be an issue or not. > > > > Finally, on oVirt, I can’t find anything either. I looked on /var/log/messages and /var/log/sanlock.log but there’s nothing that I found suspicious. > > > > Is there’s anyone out there experiencing this? Our VM’s are mainly CentOS 7/8 with XFS, there’s 3 Windows VM’s that does not seems to be affected, everything else is affected. > > > > Thanks all. > > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org Privacy > Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLYSE7HC > FNWTWFZZTL2EJHV36OENHUGB/ _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/CZ5E55LJMA7Y5…

3 8

Unable to live migrate a VM from 4.4.2 to 4.4.3 CentOS Linux host
by Gianluca Cecchi 23 Dec '20

23 Dec '20

Hello, I was able to update an external CentOS Linux 8.2 standalone engine from 4.4.2 to 4.4.3 (see dedicated thread). Then I was able to put into maintenance one 4.4.2 host (CentOS Linux 8.2 based, not ovirt node ng) and run: [root@ov301 ~]# dnf update Last metadata expiration check: 0:27:11 ago on Wed 11 Nov 2020 08:48:04 PM CET. Dependencies resolved. ====================================================================================================================== Package Arch Version Repository Size ====================================================================================================================== Installing: kernel x86_64 4.18.0-193.28.1.el8_2 BaseOS 2.8 M kernel-core x86_64 4.18.0-193.28.1.el8_2 BaseOS 28 M kernel-modules x86_64 4.18.0-193.28.1.el8_2 BaseOS 23 M ovirt-ansible-collection noarch 1.2.1-1.el8 ovirt-4.4 276 k replacing ovirt-ansible-engine-setup.noarch 1.2.4-1.el8 replacing ovirt-ansible-hosted-engine-setup.noarch 1.1.8-1.el8 Upgrading: ansible noarch 2.9.15-2.el8 ovirt-4.4-centos-ovirt44 17 M bpftool x86_64 4.18.0-193.28.1.el8_2 BaseOS 3.4 M cockpit-ovirt-dashboard noarch 0.14.13-1.el8 ovirt-4.4 3.5 M ioprocess x86_64 1.4.2-1.el8 ovirt-4.4 37 k kernel-tools x86_64 4.18.0-193.28.1.el8_2 BaseOS 3.0 M kernel-tools-libs x86_64 4.18.0-193.28.1.el8_2 BaseOS 2.8 M libiscsi x86_64 1.18.0-8.module_el8.2.0+524+f765f7e0 AppStream 89 k nftables x86_64 1:0.9.3-12.el8_2.1 BaseOS 311 k ovirt-hosted-engine-ha noarch 2.4.5-1.el8 ovirt-4.4 325 k ovirt-hosted-engine-setup noarch 2.4.8-1.el8 ovirt-4.4 227 k ovirt-imageio-client x86_64 2.1.1-1.el8 ovirt-4.4 21 k ovirt-imageio-common x86_64 2.1.1-1.el8 ovirt-4.4 155 k ovirt-imageio-daemon x86_64 2.1.1-1.el8 ovirt-4.4 15 k ovirt-provider-ovn-driver noarch 1.2.32-1.el8 ovirt-4.4 27 k ovirt-release44 noarch 4.4.3-1.el8 ovirt-4.4 17 k python3-ioprocess x86_64 1.4.2-1.el8 ovirt-4.4 33 k python3-nftables x86_64 1:0.9.3-12.el8_2.1 BaseOS 25 k python3-ovirt-engine-sdk4 x86_64 4.4.6-1.el8 ovirt-4.4 560 k python3-perf x86_64 4.18.0-193.28.1.el8_2 BaseOS 2.9 M python3-pyasn1 noarch 0.4.6-3.el8 ovirt-4.4-centos-opstools 140 k python3-pyasn1-modules noarch 0.4.6-3.el8 ovirt-4.4-centos-opstools 151 k qemu-img x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 1.0 M qemu-kvm x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 118 k qemu-kvm-block-curl x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 129 k qemu-kvm-block-gluster x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 131 k qemu-kvm-block-iscsi x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 136 k qemu-kvm-block-rbd x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 130 k qemu-kvm-block-ssh x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 131 k qemu-kvm-common x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 1.2 M qemu-kvm-core x86_64 15:4.2.0-29.el8.6 ovirt-4.4-advanced-virtualization 3.4 M selinux-policy noarch 3.14.3-41.el8_2.8 BaseOS 615 k selinux-policy-targeted noarch 3.14.3-41.el8_2.8 BaseOS 15 M spice-server x86_64 0.14.2-1.el8_2.1 AppStream 404 k tzdata noarch 2020d-1.el8 BaseOS 471 k vdsm x86_64 4.40.35.1-1.el8 ovirt-4.4 1.4 M vdsm-api noarch 4.40.35.1-1.el8 ovirt-4.4 106 k vdsm-client noarch 4.40.35.1-1.el8 ovirt-4.4 24 k vdsm-common noarch 4.40.35.1-1.el8 ovirt-4.4 136 k vdsm-hook-ethtool-options noarch 4.40.35.1-1.el8 ovirt-4.4 9.8 k vdsm-hook-fcoe noarch 4.40.35.1-1.el8 ovirt-4.4 10 k vdsm-hook-openstacknet noarch 4.40.35.1-1.el8 ovirt-4.4 18 k vdsm-hook-vhostmd noarch 4.40.35.1-1.el8 ovirt-4.4 17 k vdsm-hook-vmfex-dev noarch 4.40.35.1-1.el8 ovirt-4.4 11 k vdsm-http noarch 4.40.35.1-1.el8 ovirt-4.4 15 k vdsm-jsonrpc noarch 4.40.35.1-1.el8 ovirt-4.4 31 k vdsm-network x86_64 4.40.35.1-1.el8 ovirt-4.4 331 k vdsm-python noarch 4.40.35.1-1.el8 ovirt-4.4 1.3 M vdsm-yajsonrpc noarch 4.40.35.1-1.el8 ovirt-4.4 40 k Installing dependencies: NetworkManager-ovs x86_64 1:1.22.14-1.el8 ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.22 144 k Transaction Summary ====================================================================================================================== Install 5 Packages Upgrade 48 Packages Total download size: 116 M After reboot I can activate the host (strange that I see many pop up messages about "finished activating host") and the host is shown as OS Version: RHEL - 8.2 - 2.2004.0.2.el8 OS Description: CentOS Linux 8 (Core) Kernel Version: 4.18.0 - 193.28.1.el8_2.x86_64 KVM Version: 4.2.0 - 29.el8.6 LIBVIRT Version: libvirt-6.0.0-25.2.el8 VDSM Version: vdsm-4.40.35.1-1.el8 SPICE Version: 0.14.2 - 1.el8_2.1 GlusterFS Version: [N/A] CEPH Version: librbd1-12.2.7-9.el8 Open vSwitch Version: [N/A] Nmstate Version: nmstate-0.2.10-1.el8 Kernel Features: MDS: (Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable), L1TF: (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable), SRBDS: (Not affected), MELTDOWN: (Mitigation: PTI), SPECTRE_V1: (Mitigation: usercopy/swapgs barriers and __user pointer sanitization), SPECTRE_V2: (Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling), ITLB_MULTIHIT: (KVM: Mitigation: Split huge pages), TSX_ASYNC_ABORT: (Not affected), SPEC_STORE_BYPASS: (Mitigation: Speculative Store Bypass disabled via prctl and seccomp) VNC Encryption: Disabled FIPS mode enabled: Disabled while another host still in 4.4.2: OS Version: RHEL - 8.2 - 2.2004.0.2.el8 OS Description: CentOS Linux 8 (Core) Kernel Version: 4.18.0 - 193.19.1.el8_2.x86_64 KVM Version: 4.2.0 - 29.el8.3 LIBVIRT Version: libvirt-6.0.0-25.2.el8 VDSM Version: vdsm-4.40.26.3-1.el8 SPICE Version: 0.14.2 - 1.el8 GlusterFS Version: [N/A] CEPH Version: librbd1-12.2.7-9.el8 Open vSwitch Version: [N/A] Nmstate Version: nmstate-0.2.10-1.el8 Kernel Features: MDS: (Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable), L1TF: (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable), SRBDS: (Not affected), MELTDOWN: (Mitigation: PTI), SPECTRE_V1: (Mitigation: usercopy/swapgs barriers and __user pointer sanitization), SPECTRE_V2: (Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling), ITLB_MULTIHIT: (KVM: Mitigation: Split huge pages), TSX_ASYNC_ABORT: (Not affected), SPEC_STORE_BYPASS: (Mitigation: Speculative Store Bypass disabled via prctl and seccomp) VNC Encryption: Disabled FIPS mode enabled: Disabled But if I try to move away VMs from the 4.4.2 host to the 4.4.3 one I get error: Failed to migrate VM c8client to Host ov301 . Trying to migrate to another Host. (btw: there is no other active host; there is a ov300 host that is in maintenance) No available host was found to migrate VM c8client to. It seems the root error in engine.log is: 2020-11-11 21:44:42,487+01 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-11) [] Migration of VM 'c8client' to host 'ov301' failed: VM destroyed during the startup. On target host in /var/log/libvirt/qemu/c8clinet.log I see: 2020-11-11 20:44:40.981+0000: shutting down, reason=failed In target vdsm.log 2020-11-11 21:44:39,958+0100 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call VM.migrationCreate took more than 1.00 seconds to succeed: 1.97 (__init__:316) 2020-11-11 21:44:40,230+0100 INFO (periodic/3) [vdsm.api] START repoStats(domains=()) from=internal, task_id=cb51fd4a-09d3-4d77-821b-391da2467487 (api:48) 2020-11-11 21:44:40,231+0100 INFO (periodic/3) [vdsm.api] FINISH repoStats return={'fa33df49-b09d-4f86-9719-ede649542c21': {'code': 0, 'lastCheck': '4.1', 'delay': '0.000836715', 'valid': True, 'version': 4, 'acquired': True, 'actual': True}} from=internal, task_id=cb51fd4a-09d3-4d77-821b-391da2467487 (api:54) 2020-11-11 21:44:41,929+0100 INFO (jsonrpc/5) [api.virt] START destroy(gracefulAttempts=1) from=::ffff:10.4.192.32,52266, vmId=c95da734-7ed1-4caa-bacb-3fa24f4efb56 (api:48) 2020-11-11 21:44:41,930+0100 INFO (jsonrpc/5) [virt.vm] (vmId='c95da734-7ed1-4caa-bacb-3fa24f4efb56') Release VM resources (vm:4666) 2020-11-11 21:44:41,930+0100 INFO (jsonrpc/5) [virt.vm] (vmId='c95da734-7ed1-4caa-bacb-3fa24f4efb56') Stopping connection (guestagent:444) 2020-11-11 21:44:41,930+0100 INFO (jsonrpc/5) [vdsm.api] START teardownImage(sdUUID='fa33df49-b09d-4f86-9719-ede649542c21', spUUID='ef17cad6-7724-4cd8-96e3-9af6e529db51', imgUUID='ff10a405-cc61-4d00-a83f-3ee04b19f381', volUUID=None) from=::ffff:10.4.192.32,52266, task_id=177461c0-83d6-4c90-9c5c-3cc8ee9150c7 (api:48) It seems that during the host update the OVN configuration has not been maintained. Right now all my active VMs are with at least a vnic on OVN so I cannot test the scenario of migrating a VM without OVN based vnic. In fact on engine I see only the currently active host in 4.4.2 (ov200) and another host that is in maintenance (it is still in 4.3.10; I wanted to update to 4.4.2 but I realized that 4.4.3 has been out...): [root@ovmgr1 ovirt-engine]# ovn-sbctl show Chassis "6a46b802-5a50-4df5-b1af-e73f58a57164" hostname: "ov200.mydomain" Encap geneve ip: "10.4.192.32" options: {csum="true"} Port_Binding "2ae7391b-4297-4247-a315-99312f6392e6" Port_Binding "c1ec60a4-b4f3-4cb5-8985-43c086156e83" Port_Binding "174b69f8-00ed-4e25-96fc-7db11ea8a8b9" Port_Binding "66359e79-56c4-47e0-8196-2241706329f6" Port_Binding "ccbd6188-78eb-437b-9df9-9929e272974b" Chassis "ddecf0da-4708-4f93-958b-6af365a5eeca" hostname: "ov300.mydomain" Encap geneve ip: "10.4.192.33" options: {csum="true"} [root@ovmgr1 ovirt-engine]# Any hint about the reason of losing OVN config for ov301 and the correct procedure to get it again and persiste future updates? NOTE: this was a cluster in 4.3.10 and I updated it to 4.4.2 and I noticed that the OVN config was not retained and I had to run on hosts: [root@ov200 ~]# vdsm-tool ovn-config engine_ip ov200_ip_on_mgmt Using default PKI files Created symlink /etc/systemd/system/multi-user.target.wants/openvswitch.service → /usr/lib/systemd/system/openvswitch.service. Created symlink /etc/systemd/system/multi-user.target.wants/ovn-controller.service → /usr/lib/systemd/system/ovn-controller.service. [root@ov200 ~]# Now it seems the problem persists... Why do I have to run each time? Gianluca

1 3

oVirt 4.4: Self-hosted engine deployment fails with backup restore from 4.3 engine
by Oliver Leinfelder 11 Dec '20

11 Dec '20

Hi there, I'm a bit puzzled about an possible upgrade paths from a 4.3 cluster to version 4.4 in a self-hosted engine environment. My idea was: Set up a new host with a clean ovirt node 4.4 installation, then deploy the hosted engine on this with a restored backup from the production cluster and go from there. This however fails with the following error: 2020-05-27 00:17:08,886+0200 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 {'msg': 'non-zero return code', 'cmd': ['engine-setup', '--accept-defaults', '--config-append=/root/ovirt-engine-answers'], 'stdout': "[ INFO ] Stage: Initializing\n[ INFO ] Stage: Environment setup\n C onfiguration files: /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, /etc/ovirt-engine-setup.conf.d/10-packaging.conf, /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf, /root/ovirt-engine-answers\n Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20200527001657-fyeueu.log\n Version: otop i-1.9.1 (otopi-1.9.1-1.el8)\n[ INFO ] DNF Downloading 1 files, 0.00KB\n[ INFO ] DNF Downloaded CentOS-8 - AppStream\n[ INFO ] DNF Downloading 1 files, 0.00KB\n[ INFO ] DNF Downloaded CentOS-8 - Base\n[ INFO ] DNF Downloading 1 files, 0.00KB\n [...] ... anwsers from backup config follow .... [...] 2020-05-27 00:17:12,396+0200 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 403, in _closeup r = ah.run() File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 229, in run raise RuntimeError(_('Failed executing ansible-playbook')) Is this approach (restoring from 4.3) generally supposed to work? If not, what is the appropriate upgrade path? Thank you! Regards Oli

3 7

Can't import some VMs after storage domain detach and reattach to new datacenter.
by m black 09 Dec '20

09 Dec '20

7 14

ovirt 4.3 - locked image vm - unable to remove a failed deploy of a guest dom
by 3c.monitor＠gruppofilippetti.it 09 Dec '20

09 Dec '20

Hi all. I've deployed a VM from a corrupted template (it's disk is missing, but I've checked it later...). My Software Version is:4.3 Now, I have an unmanaged VM in inventory and unable to remove it too. It's reference is "locked image". I've restarted ovirt-engine many times on self-hosted engine and hosts too, but no benefits. So, what's now? I've also consulted: https://access.redhat.com/solutions/396753 but still no results. No tasks or items results to be "locked"... Any other ideas? Thanks a lot.

3 17

How to install win-virtio Drivers (aka guest tools) silently
by t.hofmann＠klett-it.net 09 Dec '20

09 Dec '20

Hi, i am currently trying to automate an upgrade process from the "old" oVirt 4.3 Guest Tools new one which should using starting with oVirt 4.4 To achieve this I have to install the win-virtio tools quietly. This works even if I use the parameters /install /passive /norestart. But then the oVirt Guest Agent is not installed. Is there a parameter or another way to install it during a silent installation? Thanks in advance. - Tim

3 2

BUG: after upgrading 4.4.2 to 4.4.3 ISO Domain show empty list
by Tarun Kushwaha 08 Dec '20

08 Dec '20

I have upgraded 4.4.2 to 4.4.3 afterthat ISO Domain is not showing any ISO files .its show empty list i think this is bug in 4.4.3

4 6

Cannot SSH into the self hosted host (going through tutorial)
by jenia.ivlev＠gmail.com 03 Dec '20

03 Dec '20

Hello. I want to install oVirt on my PC and for this purpose I'm following the tutorial which instructed me to make a VM and install there the oVirt self hosted host: https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engin… I cannot SSH to this new oVirt install - I get the error "Connection refused" (Even though I see something listening on port 22 by running `netstat -an`). So I tried stopping `sshd`and I got the same error. Tried to do all of this with `telnet 192.168.122.1 22`, I get the same error "Connection refused". Also, Yum returns "could not resolve host: https://mirrors.fedoraproject.org" I can ping the machine though from my PC. I turned off `firewalld`. `iproute -S` returns `ACCEPT` for everything. My PC is running archlinux and I installed the new VM using "Virtual Machine Manager". Normally, I can easily SSH to any VM I create. Maybe someone know what I'm doing wrong? Thanks kindly Jenia P.S. Running `nodectl check` returns "ok" for all.

2 3

Unable to move or copy disks
by suporte＠logicworks.pt 02 Dec '20

02 Dec '20

Hi, I was trying to move a disk between glusters domain storage without success. # gluster --version glusterfs 6.10 Now have a VM with this message: The VM has snapshot(s) with disk(s) in illegal status. Please don't shutdown the VM before successfully retrying the snapshot delete oVirt verison is Version 4.3.10.4-1.el7 I cannot delete the snapshot. What should I do? hanks -- Jose Ferradeira http://www.logicworks.pt

2 18

Can't install Ovirt from cockpit - ERROR: cannot retrieve iSCSI luns
by Patrick Lomakin 02 Dec '20

02 Dec '20

Latest version of Ovirt - 4.4.3 Hi everyboby. I have tryed to install hosted engine from ovirt cockpit, but when select iSCSI target I give the same error - Error: Cannot retrieve iSCSI LUNs. After that I have installed hosted engine from console with command - "hosted-engine --deploy" and than installed successfully. From console was able to retrieve iSCSI luns and select one there. Who can try to deploy ovirt from cockpit?

2 3

Guest OS Memory Free/Cached/Buffered: Not Configured
by Stefan Seifried 30 Nov '20

30 Nov '20

Hi, I'm quite new to oVirt, so my apologizies if I'm asking something dead obvious: I noticed that there is an item in the 'General Tab' of each VM, which says 'Guest OS Memory Free/Cached/Buffered' and on all my VM's it says 'Not Configured'. Right now I'm trying to figure out how to enable this feature. I assume that this gives me the equivalent output of executing 'free' on the shell on a Linux guest. Googling and digging around the VMM guide did not give me any pointers so far. Thanks in advance, Stefan PS: A little background info: I have one 'client' which keeps nagging me to increase the RAM on his VM because it's constantly operating at 95% memory load (as shown on the VM dashboard). After a quick investigation with 'free' I could see that Linux has built up the disk cache to 12G (from 16G total, no swapping occured). My intention is to make the real memory load visible to him, as he has already access to the VM portal for shutdown/restart/etc.

3 4

Re: Constantly XFS in memory corruption inside VMs
by Strahil Nikolov 29 Nov '20

29 Nov '20

Are you using "nobarrier" mount options in the VM ? If yes, can you try to remove the "nobarrrier" option. Best Regards, Strahil Nikolov В събота, 28 ноември 2020 г., 19:25:48 Гринуич+2, Vinícius Ferrão <ferrao(a)versatushpc.com.br> написа: Hi Strahil, I moved a running VM to other host, rebooted and no corruption was found. If there's any corruption it may be silent corruption... I've cases where the VM was new, just installed, run dnf -y update to get the updated packages, rebooted, and boom XFS corruption. So perhaps the motion process isn't the one to blame. But, in fact, I remember when moving a VM that it went down during the process and when I rebooted it was corrupted. But this may not seems related. It perhaps was already in a inconsistent state. Anyway, here's the mount options: Host1: 192.168.10.14:/mnt/pool0/ovirt/vm on /rhev/data-center/mnt/192.168.10.14:_mnt_pool0_ovirt_vm type nfs4 (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,nosharecache,proto=tcp,timeo=100,retrans=3,sec=sys,clientaddr=192.168.10.1,local_lock=none,addr=192.168.10.14) Host2: 192.168.10.14:/mnt/pool0/ovirt/vm on /rhev/data-center/mnt/192.168.10.14:_mnt_pool0_ovirt_vm type nfs4 (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,soft,nosharecache,proto=tcp,timeo=100,retrans=3,sec=sys,clientaddr=192.168.10.1,local_lock=none,addr=192.168.10.14) The options are the default ones. I haven't changed anything when configuring this cluster. Thanks. -----Original Message----- From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Saturday, November 28, 2020 1:54 PM To: users <users(a)ovirt.org>; Vinícius Ferrão <ferrao(a)versatushpc.com.br> Subject: Re: [ovirt-users] Constantly XFS in memory corruption inside VMs Can you try with a test vm, if this happens after a Virtual Machine migration ? What are your mount options for the storage domain ? Best Regards, Strahil Nikolov В събота, 28 ноември 2020 г., 18:25:15 Гринуич+2, Vinícius Ferrão via Users <users(a)ovirt.org> написа: Hello, I’m trying to discover why an oVirt 4.4.3 Cluster with two hosts and NFS shared storage on TrueNAS 12.0 is constantly getting XFS corruption inside the VMs. For random reasons VM’s gets corrupted, sometimes halting it or just being silent corrupted and after a reboot the system is unable to boot due to “corruption of in-memory data detected”. Sometimes the corrupted data are “all zeroes”, sometimes there’s data there. In extreme cases the XFS superblock 0 get’s corrupted and the system cannot even detect a XFS partition anymore since the magic XFS key is corrupted on the first blocks of the virtual disk. This is happening for a month now. We had to rollback some backups, and I don’t trust anymore on the state of the VMs. Using xfs_db I can see that some VM’s have corrupted superblocks but the VM is up. One in specific, was with sb0 corrupted, so I knew when a reboot kicks in the machine will be gone, and that’s exactly what happened. Another day I was just installing a new CentOS 8 VM for random reasons, and after running dnf -y update and a reboot the VM was corrupted needing XFS repair. That was an extreme case. So, I’ve looked on the TrueNAS logs, and there’s apparently nothing wrong on the system. No errors logged on dmesg, nothing on /var/log/messages and no errors on the “zpools”, not even after scrub operations. On the switch, a Catalyst 2960X, we’ve been monitoring it and all it’s interfaces. There are no “up and down” and zero errors on all interfaces (we have a 4x Port LACP on the TrueNAS side and 2x Port LACP on each hosts), everything seems to be fine. The only metric that I was unable to get is “dropped packages”, but I’m don’t know if this can be an issue or not. Finally, on oVirt, I can’t find anything either. I looked on /var/log/messages and /var/log/sanlock.log but there’s nothing that I found suspicious. Is there’s anyone out there experiencing this? Our VM’s are mainly CentOS 7/8 with XFS, there’s 3 Windows VM’s that does not seems to be affected, everything else is affected. Thanks all. _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLYSE7HCFNWTW…

2 4

Re: Constantly XFS in memory corruption inside VMs
by Strahil Nikolov 28 Nov '20

28 Nov '20

Can you try with a test vm, if this happens after a Virtual Machine migration ? What are your mount options for the storage domain ? Best Regards, Strahil Nikolov В събота, 28 ноември 2020 г., 18:25:15 Гринуич+2, Vinícius Ferrão via Users <users(a)ovirt.org> написа: Hello, I’m trying to discover why an oVirt 4.4.3 Cluster with two hosts and NFS shared storage on TrueNAS 12.0 is constantly getting XFS corruption inside the VMs. For random reasons VM’s gets corrupted, sometimes halting it or just being silent corrupted and after a reboot the system is unable to boot due to “corruption of in-memory data detected”. Sometimes the corrupted data are “all zeroes”, sometimes there’s data there. In extreme cases the XFS superblock 0 get’s corrupted and the system cannot even detect a XFS partition anymore since the magic XFS key is corrupted on the first blocks of the virtual disk. This is happening for a month now. We had to rollback some backups, and I don’t trust anymore on the state of the VMs. Using xfs_db I can see that some VM’s have corrupted superblocks but the VM is up. One in specific, was with sb0 corrupted, so I knew when a reboot kicks in the machine will be gone, and that’s exactly what happened. Another day I was just installing a new CentOS 8 VM for random reasons, and after running dnf -y update and a reboot the VM was corrupted needing XFS repair. That was an extreme case. So, I’ve looked on the TrueNAS logs, and there’s apparently nothing wrong on the system. No errors logged on dmesg, nothing on /var/log/messages and no errors on the “zpools”, not even after scrub operations. On the switch, a Catalyst 2960X, we’ve been monitoring it and all it’s interfaces. There are no “up and down” and zero errors on all interfaces (we have a 4x Port LACP on the TrueNAS side and 2x Port LACP on each hosts), everything seems to be fine. The only metric that I was unable to get is “dropped packages”, but I’m don’t know if this can be an issue or not. Finally, on oVirt, I can’t find anything either. I looked on /var/log/messages and /var/log/sanlock.log but there’s nothing that I found suspicious. Is there’s anyone out there experiencing this? Our VM’s are mainly CentOS 7/8 with XFS, there’s 3 Windows VM’s that does not seems to be affected, everything else is affected. Thanks all. _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLYSE7HCFNWTW…

2 1

Constantly XFS in memory corruption inside VMs
by Vinícius Ferrão 28 Nov '20

28 Nov '20

Hello, I'm trying to discover why an oVirt 4.4.3 Cluster with two hosts and NFS shared storage on TrueNAS 12.0 is constantly getting XFS corruption inside the VMs. For random reasons VM's gets corrupted, sometimes halting it or just being silent corrupted and after a reboot the system is unable to boot due to "corruption of in-memory data detected". Sometimes the corrupted data are "all zeroes", sometimes there's data there. In extreme cases the XFS superblock 0 get's corrupted and the system cannot even detect a XFS partition anymore since the magic XFS key is corrupted on the first blocks of the virtual disk. This is happening for a month now. We had to rollback some backups, and I don't trust anymore on the state of the VMs. Using xfs_db I can see that some VM's have corrupted superblocks but the VM is up. One in specific, was with sb0 corrupted, so I knew when a reboot kicks in the machine will be gone, and that's exactly what happened. Another day I was just installing a new CentOS 8 VM for random reasons, and after running dnf -y update and a reboot the VM was corrupted needing XFS repair. That was an extreme case. So, I've looked on the TrueNAS logs, and there's apparently nothing wrong on the system. No errors logged on dmesg, nothing on /var/log/messages and no errors on the "zpools", not even after scrub operations. On the switch, a Catalyst 2960X, we've been monitoring it and all it's interfaces. There are no "up and down" and zero errors on all interfaces (we have a 4x Port LACP on the TrueNAS side and 2x Port LACP on each hosts), everything seems to be fine. The only metric that I was unable to get is "dropped packages", but I'm don't know if this can be an issue or not. Finally, on oVirt, I can't find anything either. I looked on /var/log/messages and /var/log/sanlock.log but there's nothing that I found suspicious. Is there's anyone out there experiencing this? Our VM's are mainly CentOS 7/8 with XFS, there's 3 Windows VM's that does not seems to be affected, everything else is affected. Thanks all.

1 0

Ovirt 4.4.3 - Unable to start hosted engine
by Marco Marino 28 Nov '20

28 Nov '20

Hi, I have an ovirt 4.4.3 with 2 clusters, hosted engine and iscsi storage. First cluster, composed of 2 servers (host1 and host2), is dedicated to the hosted engine, the second cluster is for vms. Furthermore, there is a SAN with 3 luns: one for hosted engine storage, one for vms and one unused. My SAN is built on top of a pacemaker/drbd cluster with 2 nodes with a virtual ip used as iscsi Portal IP. Starting from today, after a failover of the iscsi cluster, I'm unable to start the hosted engine. It seems that there is some problem with storage. Actually I have only one node (host1) running in the cluster. It seems there is some lock on lvs, but I'm not sure of this. Here are some details about the problem: 1. iscsiadm -m session iSCSI Transport Class version 2.0-870 version 6.2.0.878-2 Target: iqn.2003-01.org.linux-iscsi.s1-node1.x8664:sn.2a734f67d5b1 (non-flash) Current Portal: 10.3.8.8:3260,1 Persistent Portal: 10.3.8.8:3260,1 ********** Interface: ********** Iface Name: default Iface Transport: tcp Iface Initiatorname: iqn.1994-05.com.redhat:4b668221d9a9 Iface IPaddress: 10.3.8.10 Iface HWaddress: default Iface Netdev: default SID: 1 iSCSI Connection State: LOGGED IN iSCSI Session State: LOGGED_IN Internal iscsid Session State: NO CHANGE ********* Timeouts: ********* Recovery Timeout: 5 Target Reset Timeout: 30 LUN Reset Timeout: 30 Abort Timeout: 15 ***** CHAP: ***** username: <empty> password: ******** username_in: <empty> password_in: ******** ************************ Negotiated iSCSI params: ************************ HeaderDigest: None DataDigest: None MaxRecvDataSegmentLength: 262144 MaxXmitDataSegmentLength: 262144 FirstBurstLength: 65536 MaxBurstLength: 262144 ImmediateData: Yes InitialR2T: Yes MaxOutstandingR2T: 1 ************************ Attached SCSI devices: ************************ Host Number: 7 State: running scsi7 Channel 00 Id 0 Lun: 0 Attached scsi disk sdb State: running scsi7 Channel 00 Id 0 Lun: 1 Attached scsi disk sdc State: running 2. vdsm.log errors: 2020-11-27 18:37:16,786+0100 INFO (jsonrpc/0) [api] FINISH getStats error=Virtual machine does not exist: {'vmId': 'f3a1194d-0632-43c6-8e12-7f22518cff87'} (api:129) ..... 2020-11-27 18:37:52,864+0100 INFO (jsonrpc/4) [vdsm.api] FINISH getVolumeInfo error=(-223, 'Sanlock resource read failure', 'Lease does not exist on storage') from=::1,60880, task_id=138a3615-d537-4e5f-a39c-335269ad0917 (api:52) 2020-11-27 18:37:52,864+0100 ERROR (jsonrpc/4) [storage.TaskManager.Task] (Task='138a3615-d537-4e5f-a39c-335269ad0917') Unexpected error (task:880) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 887, in _run return fn(*args, **kargs) File "<decorator-gen-159>", line 2, in getVolumeInfo File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 3142, in getVolumeInfo info = self._produce_volume(sdUUID, imgUUID, volUUID).getInfo() File "/usr/lib/python3.6/site-packages/vdsm/storage/volume.py", line 258, in getInfo leasestatus = self.getLeaseStatus() File "/usr/lib/python3.6/site-packages/vdsm/storage/volume.py", line 203, in getLeaseStatus self.volUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 549, in inquireVolumeLease return self._domainLock.inquire(lease) File "/usr/lib/python3.6/site-packages/vdsm/storage/clusterlock.py", line 464, in inquire sector=self._block_size) sanlock.SanlockException: (-223, 'Sanlock resource read failure', 'Lease does not exist on storage') 2020-11-27 18:37:52,865+0100 INFO (jsonrpc/4) [storage.TaskManager.Task] (Task='138a3615-d537-4e5f-a39c-335269ad0917') aborting: Task is aborted: "value=(-223, 'Sanlock resource read failure', 'Lease does not exist on storage') abortedcode=100" (task:1190) 3. supervdsm.log MainProcess|monitor/de4645f::DEBUG::2020-11-27 18:41:25,286::commands::153::common.commands::(start) /usr/bin/taskset --cpu-list 0-11 /usr/sbin/dmsetup remove de4645fc--f379--4837--916b--a0c2b89927d9-dfa4e933--2b9c--4057--a4c5--aa4485b070e9 (cwd None) MainProcess|monitor/de4645f::DEBUG::2020-11-27 18:41:25,293::commands::98::common.commands::(run) FAILED: <err> = b'device-mapper: remove ioctl on de4645fc--f379--4837--916b--a0c2b89927d9-dfa4e933--2b9c--4057--a4c5--aa4485b070e9 failed: Device or resource busy\nCommand failed.\n'; <rc> = 1 MainProcess|monitor/de4645f::ERROR::2020-11-27 18:41:25,294::supervdsm_server::97::SuperVdsm.ServerCallback::(wrapper) Error in devicemapper_removeMapping Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/devicemapper.py", line 141, in removeMapping commands.run(cmd) File "/usr/lib/python3.6/site-packages/vdsm/common/commands.py", line 101, in run raise cmdutils.Error(args, p.returncode, out, err) vdsm.common.cmdutils.Error: Command ['/usr/sbin/dmsetup', 'remove', 'de4645fc--f379--4837--916b--a0c2b89927d9-dfa4e933--2b9c--4057--a4c5--aa4485b070e9'] failed with rc=1 out=b'' err=b'device-mapper: remove ioctl on de4645fc--f379--4837--916b--a0c2b89927d9-dfa4e933--2b9c--4057--a4c5--aa4485b070e9 failed: Device or resource busy\nCommand failed.\n' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/supervdsm_server.py", line 95, in wrapper res = func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/supervdsm_api/devicemapper.py", line 29, in devicemapper_removeMapping return devicemapper.removeMapping(deviceName) File "/usr/lib/python3.6/site-packages/vdsm/storage/devicemapper.py", line 143, in removeMapping raise Error("Could not remove mapping: {}".format(e)) vdsm.storage.devicemapper.Error: Could not remove mapping: Command ['/usr/sbin/dmsetup', 'remove', 'de4645fc--f379--4837--916b--a0c2b89927d9-dfa4e933--2b9c--4057--a4c5--aa4485b070e9'] failed with rc=1 out=b'' err=b'device-mapper: remove ioctl on de4645fc--f379--4837--916b--a0c2b89927d9-dfa4e933--2b9c--4057--a4c5--aa4485b070e9 failed: Device or resource busy\nCommand failed.\n' 4. /var/log/messages: ... Nov 27 18:43:46 host1 journal[20573]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine ERROR Failed to start necessary monitors Nov 27 18:43:46 host1 journal[20573]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 85, in start_monitor#012 response = self._proxy.start_monitor(type, options)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in __call__#012 return self.__send(self.__name, args)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request#012 verbose=self.__verbose#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1154, in request#012 return self.single_request(host, handler, request_body, verbose)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1166, in single_request#012 http_conn = self.send_request(host, handler, request_body, verbose)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1279, in send_request#012 self.send_content(connection, request_body)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1309, in send_content#012 connection.endheaders(request_body)#012 File "/usr/lib64/python3.6/http/client.py", line 1249, in endheaders#012 self._send_output(message_body, encode_chunked=encode_chunked)#012 File "/usr/lib64/python3.6/http/client.py", line 1036, in _send_output#012 self.send(msg)#012 File "/usr/lib64/python3.6/http/client.py", line 974, in send#012 self.connect()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py", line 74, in connect#012 self.sock.connect(base64.b16decode(self.host))#012FileNotFoundError: [Errno 2] No such file or directory#012#012During handling of the above exception, another exception occurred:#012#012Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 131, in _run_agent#012 return action(he)#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 55, in action_proper#012 return he.start_monitoring()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 437, in start_monitoring#012 self._initialize_broker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 561, in _initialize_broker#012 m.get('options', {}))#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 91, in start_monitor#012 ).format(t=type, o=options, e=e)#012ovirt_hosted_engine_ha.lib.exceptions.RequestError: brokerlink - failed to start monitor via ovirt-ha-broker: [Errno 2] No such file or directory, [monitor: 'network', options: {'addr': '10.3.7.1', 'network_test': 'dns', 'tcp_t_address': '', 'tcp_t_port': ''}] Nov 27 18:43:46 host1 journal[20573]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Trying to restart agent Nov 27 18:43:46 host1 systemd[1]: ovirt-ha-agent.service: Main process exited, code=exited, status=157/n/a Nov 27 18:43:46 host1 systemd[1]: ovirt-ha-agent.service: Failed with result 'exit-code'. .... Please, let me know if other logs are needed. Thank you -- Ai sensi dell'articolo 13 del Regolamento UE, n. 2016/679 (GDPR) si informa che Titolare del trattamento dei Suoi dati personali, anche particolari, compreso l'indirizzo di posta elettronica, è la EXTRAORDY S.r.l.. E' possibile revocare il consenso in qualsiasi momento senza pregiudicare la liceità del trattamento basata sul consenso prestato prima della revoca, nonché proporre reclamo all'Autorità di controllo. Agli interessati sono riconosciuti i diritti di cui agli artt. 15 ss. del Regolamento UE, n. 2016/679 e in particolare di chiedere al titolare del trattamento l'accesso ai dati personali e la rettifica o la cancellazione degli stessi o la limitazione del trattamento o la portabilità dei dati che lo riguardano o di opporsi al loro trattamento rivolgendo le richieste inviando un messaggio al seguente indirizzo e-mail privacy(a)extraordy.com.

1 2

Can not connect to gluster storage
by Stefan Wolf 27 Nov '20

27 Nov '20

Hello, I ve a host that can not connet to gluster storage. It has worked since I ve set up the environment, and today it stoped working this are the error messages in the webui The error message for connection kvm380.durchhalten.intern:/data returned by VDSM was: Failed to fetch Gluster Volume List Failed to connect Host kvm380.durchhalten.intern to the Storage Domains data. Failed to connect Host kvm380.durchhalten.intern to the Storage Domains hosted_storage. and here the vdsm.log StorageDomainDoesNotExist: Storage domain does not exist: (u'36663740-576a-4498-b28e-0a402628c6a7',) 2020-11-27 12:59:07,665+0000 INFO (jsonrpc/2) [storage.TaskManager.Task] (Task='8bed48b8-0696-4d3f-966a-119219f3b013') aborting: Task is aborted: "Storage domain does not exist: (u'36663740-576a-4498-b28e-0a402628c6a7',)" - code 358 (task:1181) 2020-11-27 12:59:07,665+0000 ERROR (jsonrpc/2) [storage.Dispatcher] FINISH getStorageDomainInfo error=Storage domain does not exist: (u'36663740-576a-4498-b28e-0a402628c6a7',) (dispatcher:83) 2020-11-27 12:59:07,666+0000 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call StorageDomain.getInfo failed (error 358) in 0.38 seconds (__init__:312) 2020-11-27 12:59:07,698+0000 INFO (jsonrpc/7) [vdsm.api] START connectStorageServer(domType=7, spUUID=u'00000000-0000-0000-0000-000000000000', conList=[{u'id': u'e29cf818-5ee5-46e1-85c1-8aeefa33e95d', u'vfs_type': u'glusterfs', u'connection': u'kvm380.durchhalten.intern:/engine', u'user': u'kvm'}], options=None) from=::1,40964, task_id=3a3eeb80-50ef-4710-a4f4-9d35da2ff281 (api:48) 2020-11-27 12:59:07,871+0000 ERROR (jsonrpc/7) [storage.HSM] Could not connect to storageServer (hsm:2420) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2417, in connectStorageServer conObj.connect() File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 167, in connect self.validate() File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 297, in validate if not self.volinfo: File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 284, in volinfo self._volinfo = self._get_gluster_volinfo() File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 329, in _get_gluster_volinfo self._volfileserver) File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ return callMethod() File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda> **kwargs) File "<string>", line 2, in glusterVolumeInfo File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod raise convert_to_error(kind, result) GlusterVolumesListFailedException: Volume list failed: rc=30806 out=() err=['Volume does not exist'] 2020-11-27 12:59:07,871+0000 INFO (jsonrpc/7) [vdsm.api] FINISH connectStorageServer return={'statuslist': [{'status': 4149, 'id': u'e29cf818-5ee5-46e1-85c1-8aeefa33e95d'}]} from=::1,40964, task_id=3a3eeb80-50ef-4710-a4f4-9d35da2ff281 (api:54) 2020-11-27 12:59:07,871+0000 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call StoragePool.connectStorageServer succeeded in 0.18 seconds (__init__:312) 2020-11-27 12:59:08,474+0000 INFO (Reactor thread) [ProtocolDetector.AcceptorImpl] Accepted connection from ::1:40966 (protocoldetector:61) 2020-11-27 12:59:08,484+0000 INFO (Reactor thread) [ProtocolDetector.Detector] Detected protocol stomp from ::1:40966 (protocoldetector:125) 2020-11-27 12:59:08,484+0000 INFO (Reactor thread) [Broker.StompAdapter] Processing CONNECT request (stompserver:95) 2020-11-27 12:59:08,485+0000 INFO (JsonRpc (StompReactor)) [Broker.StompAdapter] Subscribe command received (stompserver:124) 2020-11-27 12:59:08,525+0000 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312) 2020-11-27 12:59:08,529+0000 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312) 2020-11-27 12:59:08,533+0000 INFO (jsonrpc/6) [vdsm.api] START getStorageDomainInfo(sdUUID=u'36663740-576a-4498-b28e-0a402628c6a7', options=None) from=::1,40966, task_id=ee3ac98e-6a93-4cb2-a626-5533c8fb78ad (api:48) 2020-11-27 12:59:08,909+0000 INFO (jsonrpc/6) [vdsm.api] FINISH getStorageDomainInfo error=Storage domain does not exist: (u'36663740-576a-4498-b28e-0a402628c6a7',) from=::1,40966, task_id=ee3ac98e-6a93-4cb2-a626-5533c8fb78ad (api:52) 2020-11-27 12:59:08,910+0000 ERROR (jsonrpc/6) [storage.TaskManager.Task] (Task='ee3ac98e-6a93-4cb2-a626-5533c8fb78ad') Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in getStorageDomainInfo File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2753, in getStorageDomainInfo dom = self.validateSdUUID(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 305, in validateSdUUID sdDom = sdCache.produce(sdUUID=sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 110, in produce domain.getRealDomain() File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 51, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 134, in _realProduce domain = self._findDomain(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 151, in _findDomain return findMethod(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 176, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) StorageDomainDoesNotExist: Storage domain does not exist: (u'36663740-576a-4498-b28e-0a402628c6a7',) can somebody tell me where the problem is and how can it solved

2 1

[ANN] oVirt 4.4.4 Third Release Candidate is now available for testing
by Sandro Bonazzola 27 Nov '20

27 Nov '20

oVirt 4.4.4 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.4 Third Release Candidate for testing, as of November 26th, 2020. This update is the fourth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.4 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.4 (redeploy in case of already being on 4.4.4). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.4 release highlights: http://www.ovirt.org/release/4.4.4/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.4/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV 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 0

"gluster-ansible-roles is not installed on Host" error on Cockpit
by Hesham Ahmed 26 Nov '20

26 Nov '20

On a new 4.3.1 oVirt Node installation, when trying to deploy HCI (also when trying adding a new gluster volume to existing clusters) using Cockpit, an error is displayed "gluster-ansible-roles is not installed on Host. To continue deployment, please install gluster-ansible-roles on Host and try again". There is no package named gluster-ansible-roles in the repositories: [root@localhost ~]# yum install gluster-ansible-roles Loaded plugins: enabled_repos_upload, fastestmirror, imgbased-persist, package_upload, product-id, search-disabled-repos, subscription-manager, vdsmupgrade This system is not registered with an entitlement server. You can use subscription-manager to register. Loading mirror speeds from cached hostfile * ovirt-4.3-epel: mirror.horizon.vn No package gluster-ansible-roles available. Error: Nothing to do Uploading Enabled Repositories Report Cannot upload enabled repos report, is this client registered? This is due to check introduced here: https://gerrit.ovirt.org/#/c/98023/1/dashboard/src/helpers/AnsibleUtil.js Changing the line from: [ "rpm", "-qa", "gluster-ansible-roles" ], { "superuser":"require" } to [ "rpm", "-qa", "gluster-ansible" ], { "superuser":"require" } resolves the issue. The above code snippet is installed at /usr/share/cockpit/ovirt-dashboard/app.js on oVirt node and can be patched by running "sed -i 's/gluster-ansible-roles/gluster-ansible/g' /usr/share/cockpit/ovirt-dashboard/app.js && systemctl restart cockpit"

2 1

VM memory decrease
by Erez Zarum 26 Nov '20

26 Nov '20

I have an 8 node cluster running oVirt 4.4.2, i have noticed lately that some VMs started to have their memory decrease. For example a VM that was configured to have 32GB memory without any notice were had their memory decrease to about 4GB, if i restart the VM the VM comes up with the correct memory but shortly after it decreases again. The VM configuration has: Memory Size: 32768 MB Maximum Memory: 131072 MB Physical Memory Guaranteed: 1024 MB It's worth mentioning that those are Linux VMs which are provisioned through Foreman, Windows VMs are not provisioned from Foreman and their "Memory Size" is identical to "Physical Memory Guaranteed", so far i have not observed a Windows VM with this behaviour, though there might be some that i haven't caught. Is there a possibility the cause for this issue is by having "Physical Memory Guaranteed" set to this low?

2 2

Check multipath status using API
by Paulo Silva 26 Nov '20

26 Nov '20

Hi, Is it possible to check the multipath status using the current REST API on ovirt? There is an old page that hints at this but I'm not sure if this has been implemented: https://www.ovirt.org/develop/release-management/features/storage/multipath… Thanks -- Paulo Silva <paulojjs(a)gmail.com>

2 1

Re: EPYC CPU not being detected correctly on cluster
by Lucia Jelinkova 26 Nov '20

26 Nov '20

Hi Vinícius, I am glad you've managed to solve it and thanks for sharing your findings. Lucia On Wed, Nov 25, 2020 at 9:07 PM Vinícius Ferrão <ferrao(a)versatushpc.com.br> wrote: > Lucia, I ended figuring out. > > > > The culprit is that I was pinned with the wrong virt module; after running > this commands I was able to have the CPU properly detected: > > > > # dnf module reset virt > > # dnf module enable virt:8.3 > > # dnf upgrade –nobest > > > > I think virt was in 8.2. > > > > Thank you! > > > > *From:* Lucia Jelinkova <ljelinko(a)redhat.com> > *Sent:* Monday, November 23, 2020 6:25 AM > *To:* Vinícius Ferrão <ferrao(a)versatushpc.com.br> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] EPYC CPU not being detected correctly on > cluster > > > > Hi Vinícius, > > > > Thank you for the libvirt output - libvirt marked the EPYC CPU as not > usable. Let's query qemu why that is. You do not need an oVirt VM to do > that, just any VM running on qemu, e.g. created by Virtual Machines Manager > or you can follow the command from the answer here: > > > > > https://unix.stackexchange.com/questions/309788/how-to-create-a-vm-from-scr… > > > > Then you can use the following commands: > > sudo virsh list --all > > sudo virsh qemu-monitor-command [your-vm's-name] --pretty > '{"execute":"query-cpu-definitions"}' > > > > I do not know if this could be related to UEFI Firmware, lets check the > qemu output first. > > > > Regards, > > > > Lucia > > > > > > On Fri, Nov 20, 2020 at 4:07 PM Vinícius Ferrão <ferrao(a)versatushpc.com.br> > wrote: > > Hi Lucia, > > > > I had to create an user for virsh: > > # saslpasswd2 -a libvirt test > > Password: > > Again (for verification): > > > > With that in mind, here’s the outputs: > > > > <domainCapabilities> > > <path>/usr/libexec/qemu-kvm</path> > > <domain>kvm</domain> > > <machine>pc-i440fx-rhel7.6.0</machine> > > <arch>x86_64</arch> > > <vcpu max='240'/> > > <iothreads supported='yes'/> > > <os supported='yes'> > > <enum name='firmware'/> > > <loader supported='yes'> > > <value>/usr/share/OVMF/OVMF_CODE.secboot.fd</value> > > <enum name='type'> > > <value>rom</value> > > <value>pflash</value> > > </enum> > > <enum name='readonly'> > > <value>yes</value> > > <value>no</value> > > </enum> > > <enum name='secure'> > > <value>no</value> > > </enum> > > </loader> > > </os> > > <cpu> > > <mode name='host-passthrough' supported='yes'/> > > <mode name='host-model' supported='yes'> > > <model fallback='forbid'>EPYC-IBPB</model> > > <vendor>AMD</vendor> > > <feature policy='require' name='x2apic'/> > > <feature policy='require' name='tsc-deadline'/> > > <feature policy='require' name='hypervisor'/> > > <feature policy='require' name='tsc_adjust'/> > > <feature policy='require' name='clwb'/> > > <feature policy='require' name='umip'/> > > <feature policy='require' name='spec-ctrl'/> > > <feature policy='require' name='stibp'/> > > <feature policy='require' name='arch-capabilities'/> > > <feature policy='require' name='ssbd'/> > > <feature policy='require' name='xsaves'/> > > <feature policy='require' name='cmp_legacy'/> > > <feature policy='require' name='perfctr_core'/> > > <feature policy='require' name='invtsc'/> > > <feature policy='require' name='clzero'/> > > <feature policy='require' name='wbnoinvd'/> > > <feature policy='require' name='amd-ssbd'/> > > <feature policy='require' name='virt-ssbd'/> > > <feature policy='require' name='rdctl-no'/> > > <feature policy='require' name='skip-l1dfl-vmentry'/> > > <feature policy='require' name='mds-no'/> > > <feature policy='require' name='pschange-mc-no'/> > > <feature policy='disable' name='monitor'/> > > <feature policy='disable' name='svm'/> > > </mode> > > <mode name='custom' supported='yes'> > > <model usable='yes'>qemu64</model> > > <model usable='yes'>qemu32</model> > > <model usable='no'>phenom</model> > > <model usable='yes'>pentium3</model> > > <model usable='yes'>pentium2</model> > > <model usable='yes'>pentium</model> > > <model usable='no'>n270</model> > > <model usable='yes'>kvm64</model> > > <model usable='yes'>kvm32</model> > > <model usable='no'>coreduo</model> > > <model usable='no'>core2duo</model> > > <model usable='no'>athlon</model> > > <model usable='yes'>Westmere-IBRS</model> > > <model usable='yes'>Westmere</model> > > <model usable='no'>Skylake-Server-noTSX-IBRS</model> > > <model usable='no'>Skylake-Server-IBRS</model> > > <model usable='no'>Skylake-Server</model> > > <model usable='no'>Skylake-Client-noTSX-IBRS</model> > > <model usable='no'>Skylake-Client-IBRS</model> > > <model usable='no'>Skylake-Client</model> > > <model usable='yes'>SandyBridge-IBRS</model> > > <model usable='yes'>SandyBridge</model> > > <model usable='yes'>Penryn</model> > > <model usable='no'>Opteron_G5</model> > > <model usable='no'>Opteron_G4</model> > > <model usable='yes'>Opteron_G3</model> > > <model usable='yes'>Opteron_G2</model> > > <model usable='yes'>Opteron_G1</model> > > <model usable='yes'>Nehalem-IBRS</model> > > <model usable='yes'>Nehalem</model> > > <model usable='no'>IvyBridge-IBRS</model> > > <model usable='no'>IvyBridge</model> > > <model usable='no'>Icelake-Server-noTSX</model> > > <model usable='no'>Icelake-Server</model> > > <model usable='no'>Icelake-Client-noTSX</model> > > <model usable='no'>Icelake-Client</model> > > <model usable='no'>Haswell-noTSX-IBRS</model> > > <model usable='no'>Haswell-noTSX</model> > > <model usable='no'>Haswell-IBRS</model> > > <model usable='no'>Haswell</model> > > <model usable='no'>EPYC-IBPB</model> > > <model usable='no'>EPYC</model> > > <model usable='no'>Dhyana</model> > > <model usable='no'>Cooperlake</model> > > <model usable='yes'>Conroe</model> > > <model usable='no'>Cascadelake-Server-noTSX</model> > > <model usable='no'>Cascadelake-Server</model> > > <model usable='no'>Broadwell-noTSX-IBRS</model> > > <model usable='no'>Broadwell-noTSX</model> > > <model usable='no'>Broadwell-IBRS</model> > > <model usable='no'>Broadwell</model> > > <model usable='yes'>486</model> > > </mode> > > </cpu> > > <devices> > > <disk supported='yes'> > > <enum name='diskDevice'> > > <value>disk</value> > > <value>cdrom</value> > > <value>floppy</value> > > <value>lun</value> > > </enum> > > <enum name='bus'> > > <value>ide</value> > > <value>fdc</value> > > <value>scsi</value> > > <value>virtio</value> > > <value>usb</value> > > <value>sata</value> > > </enum> > > <enum name='model'> > > <value>virtio</value> > > <value>virtio-transitional</value> > > <value>virtio-non-transitional</value> > > </enum> > > </disk> > > <graphics supported='yes'> > > <enum name='type'> > > <value>sdl</value> > > <value>vnc</value> > > <value>spice</value> > > </enum> > > </graphics> > > <video supported='yes'> > > <enum name='modelType'> > > <value>vga</value> > > <value>cirrus</value> > > <value>qxl</value> > > <value>virtio</value> > > <value>none</value> > > <value>bochs</value> > > <value>ramfb</value> > > </enum> > > </video> > > <hostdev supported='yes'> > > <enum name='mode'> > > <value>subsystem</value> > > </enum> > > <enum name='startupPolicy'> > > <value>default</value> > > <value>mandatory</value> > > <value>requisite</value> > > <value>optional</value> > > </enum> > > <enum name='subsysType'> > > <value>usb</value> > > <value>pci</value> > > <value>scsi</value> > > </enum> > > <enum name='capsType'/> > > <enum name='pciBackend'> > > <value>default</value> > > <value>vfio</value> > > </enum> > > </hostdev> > > <rng supported='yes'> > > <enum name='model'> > > <value>virtio</value> > > <value>virtio-transitional</value> > > <value>virtio-non-transitional</value> > > </enum> > > <enum name='backendModel'> > > <value>random</value> > > <value>egd</value> > > </enum> > > </rng> > > </devices> > > <features> > > <gic supported='no'/> > > <vmcoreinfo supported='yes'/> > > <genid supported='yes'/> > > <backingStoreInput supported='yes'/> > > <backup supported='no'/> > > <sev supported='yes'> > > <cbitpos>47</cbitpos> > > <reducedPhysBits>1</reducedPhysBits> > > </sev> > > </features> > > </domainCapabilities> > > > > Regarding the last two commands, I don’t have any VM running, since I > cannot start anything on the engine. > > > > I’m starting to suspect that this may be something in the UEFI Firmware. > > > > Any thoughts? > > > > Thanks, > > > > *From:* Lucia Jelinkova <ljelinko(a)redhat.com> > *Sent:* Friday, November 20, 2020 5:30 AM > *To:* Vinícius Ferrão <ferrao(a)versatushpc.com.br> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] EPYC CPU not being detected correctly on > cluster > > > > Hi, > > > > oVirt CPU detection depends on libvirt (and that depends on qemu) CPU > models. Could you please run the following command to see what libvirt > reports? > > > > virsh domcapabilities > > > > That should give you the list of CPUs known to libvirt with a usability > flag for each CPU. > > > > If you find out that the CPU is not usable by libvirt, you might want to > dig deeper by querying quemu directly. > > > > Locate any VM running on the system by > > sudo virsh list --all > > > > Use the name of a VM in the following command: > > sudo virsh qemu-monitor-command [your-vm's-name] --pretty > '{"execute":"query-cpu-definitions"}' > > > > That would give you the list of all CPUs supported by qemu and it will > list all cpu's features that are not available on your system. > > > > Regards, > > > > Lucia > > > > On Thu, Nov 19, 2020 at 9:38 PM Vinícius Ferrão via Users <users(a)ovirt.org> > wrote: > > Hi > > > > I’ve an strange issue with two hosts (not using the hypervisor image) with > EPYC CPUs, on the engine I got this message: > > > > The host CPU does not match the Cluster CPU Type and is running in a > degraded mode. It is missing the following CPU flags: model_EPYC. Please > update the host CPU microcode or change the Cluster CPU Type. > > > > But it is an EPYC CPU, the firmware is updated to the latest versions, but > for some reason oVirt does not like it. > > > > Here’s the relevant output from VDSM: > > "cpuCores": "128", > > "cpuFlags": > "ibs,vme,abm,sep,ssse3,perfctr_core,sse4_2,skip-l1dfl-vmentry,cx16,pae,misalignsse,avx2,smap,movbe,vgif,rdctl-no,extapic,clflushopt,de,sse4_1,xsaveerptr,perfctr_llc,fma,mca,sse,rdtscp,monitor,umip,mwaitx,cr8_legacy,mtrr,stibp,bmi2,pclmulqdq,amd-ssbd,lbrv,pdpe1gb,constant_tsc,vmmcall,f16c,ibrs,fsgsbase,invtsc,nopl,lm,3dnowprefetch,smca,ht,tsc_adjust,popcnt,cpb,bmi1,mmx,arat,aperfmperf,bpext,cqm_occup_llc,virt-ssbd,tce,pse,xsave,xgetbv1,topoext,sha_ni,amd_ppin,rdrand,cpuid,tsc_scale,extd_apicid,cqm,rep_good,tsc,sse4a,flushbyasid,pschange-mc-no,mds-no,ibpb,smep,clflush,tsc-deadline,fxsr,pat,avx,pfthreshold,v_vmsave_vmload,osvw,xsavec,cdp_l3,clzero,svm_lock,nonstop_tsc,adx,hw_pstate,spec-ctrl,arch-capabilities,xsaveopt,skinit,rdt_a,svm,rdpid,lahf_lm,fpu,rdseed,fxsr_opt,sse2,nrip_save,vmcb_clean,sme,cat_l3,cqm_mbm_local,irperf,overflow_recov,avic,mce,mmxext,msr,cx8,hypervisor,wdt,mba,nx,decodeassists,cmp_legacy,x2apic,perfctr_nb,succor,pni,xsaves,clwb,cqm_llc,syscall,apic,pge,npt,pse36,cmov,ssbd,pausefilter,sev,aes,wbnoinvd,cqm_mbm_total,spec_ctrl,model_qemu32,model_Opteron_G3,model_Nehalem-IBRS,model_qemu64,model_Conroe,model_kvm64,model_Penryn,model_SandyBridge,model_pentium,model_pentium2,model_kvm32,model_Nehalem,model_Opteron_G2,model_pentium3,model_Opteron_G1,model_SandyBridge-IBRS,model_486,model_Westmere-IBRS,model_Westmere", > > "cpuModel": "AMD EPYC 7H12 64-Core Processor", > > "cpuSockets": "2", > > "cpuSpeed": "3293.405", > > "cpuThreads": "256", > > > > Any ideia on why ou what to do to fix it? > > > > Thanks, > > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/WP6XL6ODTLJVB… > >

1 0

Connecting OVN network to physical network
by Alex K 26 Nov '20

26 Nov '20

Hi all, I have created some logical switches at the OVN network provider (the default provider that is configured during engine-setup). This is working fine. I would like though to be able to connect a logical OVN switch to a physical network at which the hosts have access, so as to give access to guest VMs to this network. When connecting such switch to a physical network the guest VMs do not have access to the physical network: [image: image.png] It seems that this should be supported from ovirt. Am I missing something? P.S. I know I can provide such connectivity through standard networking, though was wondering if this can be done with OVN. Many thanx, Alex

2 2

Re: EPYC CPU not being detected correctly on cluster
by Lucia Jelinkova 25 Nov '20

25 Nov '20

Hi Vinícius, Thank you for the libvirt output - libvirt marked the EPYC CPU as not usable. Let's query qemu why that is. You do not need an oVirt VM to do that, just any VM running on qemu, e.g. created by Virtual Machines Manager or you can follow the command from the answer here: https://unix.stackexchange.com/questions/309788/how-to-create-a-vm-from-scr… Then you can use the following commands: sudo virsh list --all sudo virsh qemu-monitor-command [your-vm's-name] --pretty '{"execute":"query-cpu-definitions"}' I do not know if this could be related to UEFI Firmware, lets check the qemu output first. Regards, Lucia On Fri, Nov 20, 2020 at 4:07 PM Vinícius Ferrão <ferrao(a)versatushpc.com.br> wrote: > Hi Lucia, > > > > I had to create an user for virsh: > > # saslpasswd2 -a libvirt test > > Password: > > Again (for verification): > > > > With that in mind, here’s the outputs: > > > > <domainCapabilities> > > <path>/usr/libexec/qemu-kvm</path> > > <domain>kvm</domain> > > <machine>pc-i440fx-rhel7.6.0</machine> > > <arch>x86_64</arch> > > <vcpu max='240'/> > > <iothreads supported='yes'/> > > <os supported='yes'> > > <enum name='firmware'/> > > <loader supported='yes'> > > <value>/usr/share/OVMF/OVMF_CODE.secboot.fd</value> > > <enum name='type'> > > <value>rom</value> > > <value>pflash</value> > > </enum> > > <enum name='readonly'> > > <value>yes</value> > > <value>no</value> > > </enum> > > <enum name='secure'> > > <value>no</value> > > </enum> > > </loader> > > </os> > > <cpu> > > <mode name='host-passthrough' supported='yes'/> > > <mode name='host-model' supported='yes'> > > <model fallback='forbid'>EPYC-IBPB</model> > > <vendor>AMD</vendor> > > <feature policy='require' name='x2apic'/> > > <feature policy='require' name='tsc-deadline'/> > > <feature policy='require' name='hypervisor'/> > > <feature policy='require' name='tsc_adjust'/> > > <feature policy='require' name='clwb'/> > > <feature policy='require' name='umip'/> > > <feature policy='require' name='spec-ctrl'/> > > <feature policy='require' name='stibp'/> > > <feature policy='require' name='arch-capabilities'/> > > <feature policy='require' name='ssbd'/> > > <feature policy='require' name='xsaves'/> > > <feature policy='require' name='cmp_legacy'/> > > <feature policy='require' name='perfctr_core'/> > > <feature policy='require' name='invtsc'/> > > <feature policy='require' name='clzero'/> > > <feature policy='require' name='wbnoinvd'/> > > <feature policy='require' name='amd-ssbd'/> > > <feature policy='require' name='virt-ssbd'/> > > <feature policy='require' name='rdctl-no'/> > > <feature policy='require' name='skip-l1dfl-vmentry'/> > > <feature policy='require' name='mds-no'/> > > <feature policy='require' name='pschange-mc-no'/> > > <feature policy='disable' name='monitor'/> > > <feature policy='disable' name='svm'/> > > </mode> > > <mode name='custom' supported='yes'> > > <model usable='yes'>qemu64</model> > > <model usable='yes'>qemu32</model> > > <model usable='no'>phenom</model> > > <model usable='yes'>pentium3</model> > > <model usable='yes'>pentium2</model> > > <model usable='yes'>pentium</model> > > <model usable='no'>n270</model> > > <model usable='yes'>kvm64</model> > > <model usable='yes'>kvm32</model> > > <model usable='no'>coreduo</model> > > <model usable='no'>core2duo</model> > > <model usable='no'>athlon</model> > > <model usable='yes'>Westmere-IBRS</model> > > <model usable='yes'>Westmere</model> > > <model usable='no'>Skylake-Server-noTSX-IBRS</model> > > <model usable='no'>Skylake-Server-IBRS</model> > > <model usable='no'>Skylake-Server</model> > > <model usable='no'>Skylake-Client-noTSX-IBRS</model> > > <model usable='no'>Skylake-Client-IBRS</model> > > <model usable='no'>Skylake-Client</model> > > <model usable='yes'>SandyBridge-IBRS</model> > > <model usable='yes'>SandyBridge</model> > > <model usable='yes'>Penryn</model> > > <model usable='no'>Opteron_G5</model> > > <model usable='no'>Opteron_G4</model> > > <model usable='yes'>Opteron_G3</model> > > <model usable='yes'>Opteron_G2</model> > > <model usable='yes'>Opteron_G1</model> > > <model usable='yes'>Nehalem-IBRS</model> > > <model usable='yes'>Nehalem</model> > > <model usable='no'>IvyBridge-IBRS</model> > > <model usable='no'>IvyBridge</model> > > <model usable='no'>Icelake-Server-noTSX</model> > > <model usable='no'>Icelake-Server</model> > > <model usable='no'>Icelake-Client-noTSX</model> > > <model usable='no'>Icelake-Client</model> > > <model usable='no'>Haswell-noTSX-IBRS</model> > > <model usable='no'>Haswell-noTSX</model> > > <model usable='no'>Haswell-IBRS</model> > > <model usable='no'>Haswell</model> > > <model usable='no'>EPYC-IBPB</model> > > <model usable='no'>EPYC</model> > > <model usable='no'>Dhyana</model> > > <model usable='no'>Cooperlake</model> > > <model usable='yes'>Conroe</model> > > <model usable='no'>Cascadelake-Server-noTSX</model> > > <model usable='no'>Cascadelake-Server</model> > > <model usable='no'>Broadwell-noTSX-IBRS</model> > > <model usable='no'>Broadwell-noTSX</model> > > <model usable='no'>Broadwell-IBRS</model> > > <model usable='no'>Broadwell</model> > > <model usable='yes'>486</model> > > </mode> > > </cpu> > > <devices> > > <disk supported='yes'> > > <enum name='diskDevice'> > > <value>disk</value> > > <value>cdrom</value> > > <value>floppy</value> > > <value>lun</value> > > </enum> > > <enum name='bus'> > > <value>ide</value> > > <value>fdc</value> > > <value>scsi</value> > > <value>virtio</value> > > <value>usb</value> > > <value>sata</value> > > </enum> > > <enum name='model'> > > <value>virtio</value> > > <value>virtio-transitional</value> > > <value>virtio-non-transitional</value> > > </enum> > > </disk> > > <graphics supported='yes'> > > <enum name='type'> > > <value>sdl</value> > > <value>vnc</value> > > <value>spice</value> > > </enum> > > </graphics> > > <video supported='yes'> > > <enum name='modelType'> > > <value>vga</value> > > <value>cirrus</value> > > <value>qxl</value> > > <value>virtio</value> > > <value>none</value> > > <value>bochs</value> > > <value>ramfb</value> > > </enum> > > </video> > > <hostdev supported='yes'> > > <enum name='mode'> > > <value>subsystem</value> > > </enum> > > <enum name='startupPolicy'> > > <value>default</value> > > <value>mandatory</value> > > <value>requisite</value> > > <value>optional</value> > > </enum> > > <enum name='subsysType'> > > <value>usb</value> > > <value>pci</value> > > <value>scsi</value> > > </enum> > > <enum name='capsType'/> > > <enum name='pciBackend'> > > <value>default</value> > > <value>vfio</value> > > </enum> > > </hostdev> > > <rng supported='yes'> > > <enum name='model'> > > <value>virtio</value> > > <value>virtio-transitional</value> > > <value>virtio-non-transitional</value> > > </enum> > > <enum name='backendModel'> > > <value>random</value> > > <value>egd</value> > > </enum> > > </rng> > > </devices> > > <features> > > <gic supported='no'/> > > <vmcoreinfo supported='yes'/> > > <genid supported='yes'/> > > <backingStoreInput supported='yes'/> > > <backup supported='no'/> > > <sev supported='yes'> > > <cbitpos>47</cbitpos> > > <reducedPhysBits>1</reducedPhysBits> > > </sev> > > </features> > > </domainCapabilities> > > > > Regarding the last two commands, I don’t have any VM running, since I > cannot start anything on the engine. > > > > I’m starting to suspect that this may be something in the UEFI Firmware. > > > > Any thoughts? > > > > Thanks, > > > > *From:* Lucia Jelinkova <ljelinko(a)redhat.com> > *Sent:* Friday, November 20, 2020 5:30 AM > *To:* Vinícius Ferrão <ferrao(a)versatushpc.com.br> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] EPYC CPU not being detected correctly on > cluster > > > > Hi, > > > > oVirt CPU detection depends on libvirt (and that depends on qemu) CPU > models. Could you please run the following command to see what libvirt > reports? > > > > virsh domcapabilities > > > > That should give you the list of CPUs known to libvirt with a usability > flag for each CPU. > > > > If you find out that the CPU is not usable by libvirt, you might want to > dig deeper by querying quemu directly. > > > > Locate any VM running on the system by > > sudo virsh list --all > > > > Use the name of a VM in the following command: > > sudo virsh qemu-monitor-command [your-vm's-name] --pretty > '{"execute":"query-cpu-definitions"}' > > > > That would give you the list of all CPUs supported by qemu and it will > list all cpu's features that are not available on your system. > > > > Regards, > > > > Lucia > > > > On Thu, Nov 19, 2020 at 9:38 PM Vinícius Ferrão via Users <users(a)ovirt.org> > wrote: > > Hi > > > > I’ve an strange issue with two hosts (not using the hypervisor image) with > EPYC CPUs, on the engine I got this message: > > > > The host CPU does not match the Cluster CPU Type and is running in a > degraded mode. It is missing the following CPU flags: model_EPYC. Please > update the host CPU microcode or change the Cluster CPU Type. > > > > But it is an EPYC CPU, the firmware is updated to the latest versions, but > for some reason oVirt does not like it. > > > > Here’s the relevant output from VDSM: > > "cpuCores": "128", > > "cpuFlags": > "ibs,vme,abm,sep,ssse3,perfctr_core,sse4_2,skip-l1dfl-vmentry,cx16,pae,misalignsse,avx2,smap,movbe,vgif,rdctl-no,extapic,clflushopt,de,sse4_1,xsaveerptr,perfctr_llc,fma,mca,sse,rdtscp,monitor,umip,mwaitx,cr8_legacy,mtrr,stibp,bmi2,pclmulqdq,amd-ssbd,lbrv,pdpe1gb,constant_tsc,vmmcall,f16c,ibrs,fsgsbase,invtsc,nopl,lm,3dnowprefetch,smca,ht,tsc_adjust,popcnt,cpb,bmi1,mmx,arat,aperfmperf,bpext,cqm_occup_llc,virt-ssbd,tce,pse,xsave,xgetbv1,topoext,sha_ni,amd_ppin,rdrand,cpuid,tsc_scale,extd_apicid,cqm,rep_good,tsc,sse4a,flushbyasid,pschange-mc-no,mds-no,ibpb,smep,clflush,tsc-deadline,fxsr,pat,avx,pfthreshold,v_vmsave_vmload,osvw,xsavec,cdp_l3,clzero,svm_lock,nonstop_tsc,adx,hw_pstate,spec-ctrl,arch-capabilities,xsaveopt,skinit,rdt_a,svm,rdpid,lahf_lm,fpu,rdseed,fxsr_opt,sse2,nrip_save,vmcb_clean,sme,cat_l3,cqm_mbm_local,irperf,overflow_recov,avic,mce,mmxext,msr,cx8,hypervisor,wdt,mba,nx,decodeassists,cmp_legacy,x2apic,perfctr_nb,succor,pni,xsaves,clwb,cqm_llc,syscall,apic,pge,npt,pse36,cmov,ssbd,pausefilter,sev,aes,wbnoinvd,cqm_mbm_total,spec_ctrl,model_qemu32,model_Opteron_G3,model_Nehalem-IBRS,model_qemu64,model_Conroe,model_kvm64,model_Penryn,model_SandyBridge,model_pentium,model_pentium2,model_kvm32,model_Nehalem,model_Opteron_G2,model_pentium3,model_Opteron_G1,model_SandyBridge-IBRS,model_486,model_Westmere-IBRS,model_Westmere", > > "cpuModel": "AMD EPYC 7H12 64-Core Processor", > > "cpuSockets": "2", > > "cpuSpeed": "3293.405", > > "cpuThreads": "256", > > > > Any ideia on why ou what to do to fix it? > > > > Thanks, > > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/WP6XL6ODTLJVB… > >

2 1

OVS - interface in a weir (broken) state after each system reboot.
by lejeczek 25 Nov '20

25 Nov '20

2 2

Re: Ovirt 4 2 NIC's
by Dominik Holler 24 Nov '20

24 Nov '20

https://www.ovirt.org/documentation/administration_guide/#Designate_a_Speci… documents how to use a display network. A possible flow could be like this: 1. Create a new logical network, use a VLAN if you do not have a free NIC on every host 2. Attach the new logical network and attach it in Compute > Hosts > hostname > Network Interfaces > Setup Host Networks to a free NIC (or an already used one if the network has a VLAN) for every host. This new network attachment should have an IP address. 3. Ensure that your network infrastructure allows the communication of your users into the display network. 4. Assign the role "Display Network" in Compute > Clusters > ClusterName > Logical Networks > Manage Networks to the new network. > El vie, 20 de nov. de 2020 a la(s) 06:01, Dominik Holler ( > dholler(a)redhat.com) escribió: > >> >> >> On Wed, Nov 18, 2020 at 7:30 PM Facundo Badaracco <varekoarfa(a)gmail.com> >> wrote: >> >>> Hi everyone! >>> >>> Hope someone can help me with this.. >>> >>> I have 3 servers with centos 8 and ovirt 4 installed. Each server has 2 >>> nic. >>> Server A = HE (HA) >>> Nic1= 192.169.2.24 Nic2=no ip >>> Server B = HE (HA) >>> Nic1= 192.169.2.25 Nic2=no ip >>> Server C = simply host. >>> Nic1= 192.169.2.26 Nic2=no ip >>> >>> How can i configure the second NIC in each server in order to use it for >>> clients connect to the vms?. I want one nic for management, the other for >>> connections. >>> >> >> >> If the clients want to access network services provided by the VMs, >> you could create an additional logical network in oVirt, and attach it in >> Compute > Hosts > hostname > Network Interfaces > Setup Host Networks >> to Nic2 for every host. This new network attachment should have no IP >> address. >> After that, you could reference this new logical network in your VMs >> virtual NICs. >> If possible, I would recommend using a VLAN to provide isolation to the >> management network. >> >> If the clients connect via SPICE or VNC, you would require a >> dedicated display network. >> >> >> >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/PL7WFXC4UZBUZ… >>> >>

1 0

Ovirt 4.4.3 Hyper-converged Deployment with GlusterFS
by rcpoling＠gmail.com 24 Nov '20

24 Nov '20

Trying to deploy a 3 Node Hyperconverged Ovirt Cluster with Gluster as the backend storage. I have tried this against the three nodes that I have as well as with just a single node to get a working base line. The failure that I keep getting stuck on is: TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** task path: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vg_create.yml:59 failed: [ovirt01-storage.poling.local] (item={'key': 'gluster_vg_sdb', 'value': [{'vgname': 'gluster_vg_sdb', 'pvname': '/dev/sdb'}]}) => {"ansible_loop_var": "item", "changed": false, "err": " Device /dev/sdb excluded by a filter.\n", "item": {"key": "gluster_vg_sdb", "value": [{"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}]}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5} I have verified my dns records and have reverse dns set up. The Front End Network and Storage Networks are physical separated and are 10GB connections. In the reading i have done this seems to point to possibly being a multipath issue, but i do see multipath configs being set in the Gluster Wizard and when I check after the wizard fails out - it does look like the mpath is set correctly. [root@ovirt01 ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 446.1G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 445.1G 0 part ├─onn-pool00_tmeta 253:0 0 1G 0 lvm │ └─onn-pool00-tpool 253:2 0 351.7G 0 lvm │ ├─onn-ovirt--node--ng--4.4.3--0.20201110.0+1 253:3 0 314.7G 0 lvm / │ ├─onn-pool00 253:5 0 351.7G 1 lvm │ ├─onn-var_log_audit 253:6 0 2G 0 lvm /var/log/audit │ ├─onn-var_log 253:7 0 8G 0 lvm /var/log │ ├─onn-var_crash 253:8 0 10G 0 lvm /var/crash │ ├─onn-var 253:9 0 15G 0 lvm /var │ ├─onn-tmp 253:10 0 1G 0 lvm /tmp │ ├─onn-home 253:11 0 1G 0 lvm /home │ └─onn-ovirt--node--ng--4.4.2--0.20200918.0+1 253:12 0 314.7G 0 lvm ├─onn-pool00_tdata 253:1 0 351.7G 0 lvm │ └─onn-pool00-tpool 253:2 0 351.7G 0 lvm │ ├─onn-ovirt--node--ng--4.4.3--0.20201110.0+1 253:3 0 314.7G 0 lvm / │ ├─onn-pool00 253:5 0 351.7G 1 lvm │ ├─onn-var_log_audit 253:6 0 2G 0 lvm /var/log/audit │ ├─onn-var_log 253:7 0 8G 0 lvm /var/log │ ├─onn-var_crash 253:8 0 10G 0 lvm /var/crash │ ├─onn-var 253:9 0 15G 0 lvm /var │ ├─onn-tmp 253:10 0 1G 0 lvm /tmp │ ├─onn-home 253:11 0 1G 0 lvm /home │ └─onn-ovirt--node--ng--4.4.2--0.20200918.0+1 253:12 0 314.7G 0 lvm └─onn-swap 253:4 0 4G 0 lvm [SWAP] sdb 8:16 0 5.5T 0 disk └─sdb1 8:17 0 5.5T 0 part /sdb Looking for any pointers on what else I should be looking at to get gluster to deploy successfully. Thanks ~ R

3 4

bond or different networks for frontend and backend
by jb 24 Nov '20

24 Nov '20

Hello, here in the description (https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Single_node…) it says that we should have at least 2 interfaces to separate frontend and backend traffic. How is this when I have 4 nics and I make with all one bond interface, is this not better in terms of performance? What is your recommendation with 4 x 1Gbit nics? Best regards Jonathan

3 4

Replacing ovirt certificates issue
by Alex K 24 Nov '20

24 Nov '20

Hi all, I am trying to replace the ovirt certificate at ovirt 4.3 following this: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht… I am doing the following: I have engine FQDN: manager.lab.local 1. Create root CA private key: openssl genrsa -des3 -out root.key 2048 2. Generate root certificate: (enter passphrase of root key) openssl req -x509 -new -nodes -key root.key -sha256 -days 3650 -out root.pem cp root.pem /tmp 3. Create key and CSR for engine: openssl genrsa -out manager.lab.local.key 2048 openssl req -new -out manager.lab.local.csr -key manager.lab.local.key 4. Generate a certificate for engine and sign with the root CA key: openssl x509 -req -in manager.lab.local.csr \ -CA root.pem \ -CAkey root.key \ -CAcreateserial \ -out manager.lab.local.crt \ -days 3650 \ -sha256 \ -extensions v3_req 5. Verify the trust chain and check the certificate details: openssl verify -CAfile root.pem manager.lab.local.crt openssl x509 -text -noout -in manager.lab.local.crt | head -15 6. Generate a P12 container: (with empty password) openssl pkcs12 -export -out /tmp/apache.p12 \ -inkey manager.lab.local.key \ -in manager.lab.local.crt 8. Export key and cert: openssl pkcs12 -in apache.p12 -nocerts -nodes > /tmp/apache.key openssl pkcs12 -in apache.p12 -nokeys > /tmp/apache.cer From the above steps we should have the following: /tmp/root.pem /tmp/apache.p12 /tmp/apache.key /tmp/apache.cer 9. Place the certificates: hosted-engine --set-maintenance --mode=global cp -p /etc/pki/ovirt-engine/keys/apache.p12 /tmp/apache.p12.bck cp /tmp/apache.p12 /etc/pki/ovirt-engine/keys/apache.p12 cp /tmp/root.pem /etc/pki/ca-trust/source/anchors update-ca-trust rm /etc/pki/ovirt-engine/apache-ca.pem cp /tmp/root.pem /etc/pki/ovirt-engine/apache-ca.pem Backup existing key and cert: cp /etc/pki/ovirt-engine/keys/apache.key.nopass /etc/pki/ovirt-engine/keys/apache.key.nopass.bck cp /etc/pki/ovirt-engine/certs/apache.cer /etc/pki/ovirt-engine/certs/apache.cer.bck cp /tmp/apache.key /etc/pki/ovirt-engine/keys/apache.key.nopass cp /tmp/apache.cer /etc/pki/ovirt-engine/certs/apache.cer chown root:ovirt /etc/pki/ovirt-engine/keys/apache.key.nopass chmod 640 /etc/pki/ovirt-engine/keys/apache.key.nopass systemctl restart httpd.service 10. Create a new trust store configuration file: vi /etc/ovirt-engine/engine.conf.d/99-custom-truststore.conf ENGINE_HTTPS_PKI_TRUST_STORE="/etc/pki/java/cacerts" ENGINE_HTTPS_PKI_TRUST_STORE_PASSWORD="" 11. Edit /etc/ovirt-engine/ovirt-websocket-proxy.conf.d/10-setup.conf : vi /etc/ovirt-engine/ovirt-websocket-proxy.conf.d/10-setup.conf SSL_CERTIFICATE=/etc/pki/ovirt-engine/certs/apache.cer SSL_KEY=/etc/pki/ovirt-engine/keys/apache.key.nopass 12. Edit /etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf: vi /etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf # Key file for SSL connections ssl_key_file = /etc/pki/ovirt-engine/keys/apache.key.nopass # Certificate file for SSL connections ssl_cert_file = /etc/pki/ovirt-engine/certs/apache.cer 13. Import the certificate at system-wide java trust store update-ca-trust extract keytool -list -alias ovirt -keystore /etc/pki/java/cacerts 14. Restart services: systemctl restart httpd.service systemctl restart ovirt-provider-ovn.service systemctl restart ovirt-imageio-proxy systemctl restart ovirt-websocket-proxy systemctl restart ovirt-engine.service Following the above I get at engine GUI: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target I have tried also to run engine-setup in case it could fix anything (it renewed the cert due to missing subjectAltName), and the above error still persists. I have tried several other suggestions from similar issues reported at this list without any luck. I have run out of ideas. Am I missing anything? Thanx for any suggestions. Alex

3 10

ovirt 4.3 cannot upload ISO to data domain
by Facundo Badaracco 24 Nov '20

24 Nov '20

Hi everyone. Im trying to upload a ISO to my data domain, the GUI gives me this error "Connection to ovirt-imageio service has failed. Ensure that ovirt-engine certificate <https://192.168.2.27/ovirt-engine/services/pki-resource?resource=ca-certifi…> is registered as a valid CA in the browser.". the image fails whne trying to upload. i have added the certificate in chrome, but inst working. Some help? any other way to upload?

3 2

Re: Fix corrupt self-hosted engine
by Alex K 24 Nov '20

24 Nov '20

On Sun, Nov 22, 2020 at 8:57 AM Yedidyah Bar David <didi(a)redhat.com> wrote: > On Thu, Nov 19, 2020 at 9:43 PM Alex K <rightkicktech(a)gmail.com> wrote: > >> >> >> On Thu, Nov 19, 2020 at 5:31 PM Alex K <rightkicktech(a)gmail.com> wrote: >> >>> Hi Didi, >>> >>> On Thu, Nov 19, 2020 at 5:13 PM Yedidyah Bar David <didi(a)redhat.com> >>> wrote: >>> >>>> On Thu, Nov 19, 2020 at 4:37 PM Alex K <rightkicktech(a)gmail.com> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I have a corrupt self-hosted engine (with several file system errors, >>>>> postgres not able to start) and thus it does not give access to the web UI. >>>>> This happened following an unlucky split brain resolution (I am running 2 >>>>> nodes). The two hosts are running VMs also which I would like to keep >>>>> running as they are needed. >>>>> >>>>> When trying to boot into rescue mode (using >>>>> systemd.unit=emergency.target boot parameter) I get a cursor and nothing >>>>> else. >>>>> >>>> >>>> This means that more than just the DB is corrupt... >>>> >>>> >>>>> >>>>> I have backups of engine files with scope all (using the engine-backup >>>>> tool). >>>>> What is the best approach to try and fix the engine or redeploy. >>>>> >>>> >>>> If you are careful, and know what you are doing, you can try something >>>> like the following. I am not giving many details, hopefully you can find on >>>> the net tutorials about how to use the things I suggest: >>>> >>>> 1. Move to global maintenance >>>> >>>> 2. Stop the current dead vm (if needed) >>>> >>>> 3. Find current vm conf, edit it to boot from a rescue iso image of >>>> your preference or from net/PXE etc., and start the vm with '--vm-conf' >>>> pointing to your edited file. >>>> >>>> 4. Connect a console (hosted-engine --console, or 'virsh console', or >>>> use '--add-console-password' and remote viewer, if needed) >>>> >>>> 5. Clean the disk and install the OS, oVirt, etc. >>>> >>>> 6. Copy your backup into the vm and restore with engine-backup >>>> >>>> 7. Then cleanly stop the machine, exit global maint, and let HA start >>>> it (or start it yourself with --vm-start). >>>> >>>> At the time, we had a bug [1] to document this. The result is [2]. It >>>> does not detail how to boot/reinstall os/etc., only restore (if e.g. db is >>>> dead but fs is ok). >>>> For something somewhat similar to what you want, see also [3], which >>>> uses guestfish. Might be useful, depending on how badly your disk is >>>> corrupted. >>>> >>> I went with the guestfish approach. It has fixed some fs issues and now >>> the yum etc seem fine apart from postgres. >>> I had tried previously to uninstall/install packages so I ended >>> installing them again with yum install ovirt\*setup\*. >>> Now I think I have to run engine-setup but I get the error: >>> >>> Failed to execute stage 'Environment setup': Cannot connect to Engine >>> database using existing credentials: engine@localhost:5432 >>> >> Seems that I need to have psql running to be able to run engine-backup >> --mode=restore. Are there any steps how one could manually prepare pgsql >> for ovirt so as to attempt restoration? >> > > Replying again, also to conclude this part of your episode: Generally > speaking, that's not needed. restore --provision-all-databases should do > that for you. > Seems that when pgsql is down nothing can be done. You need at least pgsql up and running (e clean state will do) so as to be able to proceed with restoration. > > I replied to all your interim emails in private, since you replied in > private. > Did not notice I was replying in private :) > > Thanks for the final message to the list. > > It would be nice if you send another summary of the main obstacles you ran > into, what worked and didn't work, and especially what ideas you can think > of to improve the code/doc for the next time something similar happens > (also to you :-) ). > > If you feel like that, and have time, it sounds like a nice opportunity > for a blog post :-) (I know I (almost?) never wrote any myself, sorry, but > I like reading them - and they are much more approachable and useful, over > the long run, compared to just posting to the list). > Noted. Will check to put this in a blog. Generally the missing part from the docs was that one cannot proceed with the restoration if pgsql is not able to start. So I had to clean re-install pgsql and initialize its data store before proceeding with the restoration. > > Best regards, > > >> >>> So I guess I need to follow [2]. What do you think? >>> >>> >>>> How did you run into a split brain? There is a lock on the shared >>>> storage that should prevent this. >>>> >>>> Good luck and best regards, >>>> >>>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1482710 >>>> [2] >>>> https://www.ovirt.org/documentation/administration_guide/#Overwriting_a_Sel… >>>> [3] https://bugzilla.redhat.com/show_bug.cgi?id=1569827#c4 >>>> -- >>>> Didi >>>> >>> > > -- > Didi >

2 3

Re: ovirt 4.3 cannot upload ISO to data domain
by Alex K 24 Nov '20

24 Nov '20

On Tue, Nov 24, 2020 at 12:44 PM Facundo Badaracco <varekoarfa(a)gmail.com> wrote: > hi alex! > > imageio-proxy isnt installed. Only ovirt-imageio service is running. > (ovirt 4.4 now, i made the update) > If I run the following I get: [root@engine ~]# systemctl | grep image ovirt-imageio-proxy.service Then checking the status of the service I confirm it is up: systemctl status ovirt-imageio-proxy.service If the service is up and ok then you need to check the certificate issue. I had noticed some times that importing the cert form GUI had not resolved the issue. You may try to manually get the CA cert from engine (/etc/pki/ovirt-engine/ca.pem) and import it at your browser. Clean cache at browser and try again. The browser should indicate the connection is trusted and secure. Also, you might need to remove the already imported cert from your browser. > when i connecto to the web UI, it say the certificate is not valid. with a > red warning. but, i have already added the certificate to chrome > > El mar, 24 de nov. de 2020 a la(s) 07:22, Alex K (rightkicktech(a)gmail.com) > escribió: > >> >> >> On Mon, Nov 23, 2020 at 4:43 PM Facundo Badaracco <varekoarfa(a)gmail.com> >> wrote: >> >>> Hi everyone. >>> >>> Im trying to upload a ISO to my data domain, the GUI gives me this error >>> "Connection to ovirt-imageio service has failed. Ensure that ovirt-engine >>> certificate >>> <https://192.168.2.27/ovirt-engine/services/pki-resource?resource=ca-certifi…> is >>> registered as a valid CA in the browser.". >>> >> is the imageio service running ok? At engine: systemctl status >> ovirt-imageio-proxy >> Also, when connecting at the engine web UI, is the browser happy with the >> certificate of the UI? >> >>> >>> the image fails whne trying to upload. >>> >>> i have added the certificate in chrome, but inst working. >>> >>> Some help? any other way to upload? >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/47YYPUF3NA2SH… >>> >>

1 0

oVirt 4.4 and Active directory
by Latchezar Filtchev 24 Nov '20

24 Nov '20

Hello All, Fresh standalone installation of oVirt 4.3 (CentOS 7) . Execution of ovirt-engine-extension-aaa-ldap-setup completes normally and DC is connected to AD (Domain functional level: Windows Server 2008 ). On the same hardware fresh standalone installation of oVirt 4.4. Installation of engine completed with warning: 2020-11-23 14:50:46,159+0200 WARNING otopi.plugins.ovirt_engine_common.base.network.hostname hostname._validateFQDNresolvability:308 Failed to resolve 44-8.mb118.local using DNS, it can be resolved only locally Despite warning engine portal is resolvable after installation. Execution of ovirt-engine-extension-aaa-ldap-setup ends with: [ INFO ] Stage: Environment customization Welcome to LDAP extension configuration program Available LDAP implementations: 1 - 389ds 2 - 389ds RFC-2307 Schema 3 - Active Directory 4 - IBM Security Directory Server 5 - IBM Security Directory Server RFC-2307 Schema 6 - IPA 7 - Novell eDirectory RFC-2307 Schema 8 - OpenLDAP RFC-2307 Schema 9 - OpenLDAP Standard Schema 10 - Oracle Unified Directory RFC-2307 Schema 11 - RFC-2307 Schema (Generic) 12 - RHDS 13 - RHDS RFC-2307 Schema 14 - iPlanet Please select: 3 Please enter Active Directory Forest name: mb118.local [ INFO ] Resolving Global Catalog SRV record for mb118.local [WARNING] Cannot resolve Global Catalog SRV record for mb118.local. Please check you have entered correct Active Directory forest name and check that forest is resolvable by your system DNS servers [ ERROR ] Failed to execute stage 'Environment customization': Active Directory forest is not resolvable, please make sure you've entered correct forest name. If for some reason you can't use forest and you need some special configuration instead, please refer to examples directory provided by ovirt-engine-extension-aaa-ldap package. [ INFO ] Stage: Clean up Log file is available at /tmp/ovirt-engine-extension-aaa-ldap-setup-20201123113909-bj749k.log: [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination Can someone advise on this? Thank you! Best, Latcho

1 0

error for gluster-ansible-roles is not installed on Host. To continue deployment, please install gluster-ansible-roles on Host and try again.
by garcialiang.anne＠gmail.com 23 Nov '20

23 Nov '20

Hello, Why have I this message : gluster-ansible-roles is not installed on Host. To continue deployment, please install gluster-ansible-roles on Host and try again. When I try create glusterfs with Hyperconverged - Configure Gluster storage and oVirt hosted engine ? Could you help me ? Best regards! Anne Garcia

2 1

Intel Cascade Lake Family supported
by Ramon Sierra 23 Nov '20

23 Nov '20

Hi, We are planning to upgrade our cluster hardware. We would like to know if Intel Cascade Lake CPUs are supported on ovirt 4.4.3. Any recommendation is very welcome. Regards, Ramon

3 2

oVirt Engine LDAP aaa - rfc2307bis issues
by Jake R 23 Nov '20

23 Nov '20

Hi, I have LDAP with rfc2307bis schema - I have posixGroup, with members defined as FDNs under the member attribute. Currently, if I login to oVirt via the AAA extension. then my groups are not enumerated. The LDAP searches (recorded on the LDAP server) are: slapd[1503]: conn=7876 op=2 SRCH base="dc=example,dc=com" scope=2 deref=0 filter="(&(objectClass=posixGroup)(memberUid=jreynolds))" slapd[1503]: conn=7876 op=2 SRCH attr=entryUUID cn description slapd[1503]: conn=7871 op=2 SRCH base="dc=example,dc=com" scope=2 deref=0 filter="(&(|(objectClass=groupOfUniqueNames)(objectClass=posixGroup))(uniqueMember:uniqueMemberMatch:=cn=jreynolds,ou=users,dc=example,dc=com))" slapd[1503]: conn=7871 op=2 SRCH attr=entryUUID cn description This returns no results, as the search needs to search for 'member' attribute, with an FDN. The issue looks to be inherited from the simple.properties file (regardless of if I use rfc2307, rfc2307-openldap profile), with the line: search.simple-resolve-groups-member.search-request.filter = &${seq:simple_filterGroupObject}(${seq:simple_attrGroupMemberDN}=${seq:_simple_dn_encoded}) I can fix the issue by replacing "${seq:simple_attrGroupMemberDN}=" with "member=", but this feels pretty hacky. I cannot find where this variable is defined, nor how to change it. Is the correct way to do this to create a new profile that overwrites the filter value? Or am I doing something wrong? I don't think my LDAP schema is particularly unusual, as far as I'm aware it complies with rfc2307bis spec. Thanks, Jake

2 1

Can't find storage server connection
by francesco＠shellrent.com 23 Nov '20

23 Nov '20

Hi all, I'm using oVirt SDK python for retrieving info about storage domain, in several hosts (centos7/ovirt4.3 and centos8/ovirt4.4), but the script exits with the following error in some of them: Traceback (most recent call last): File "get_uuid.py", line 70, in <module> storage_domain = sds_service.list(search='name=data-foo')[0] File "/root/.local/lib/python2.7/site-packages/ovirtsdk4/services.py", line 26296, in list return self._internal_get(headers, query, wait) File "/root/.local/lib/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get return future.wait() if wait else future File "/root/.local/lib/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/root/.local/lib/python2.7/site-packages/ovirtsdk4/service.py", line 208, in callback self._check_fault(response) File "/root/.local/lib/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/root/.local/lib/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "Can't find storage server connection for id '92444a95-0be7-4589-ac46-1ed6dfe7ed4c'.". HTTP response code is 500. The portion of the script that search for the storage domain is the following: sds_service = connection.system_service().storage_domains_service() storage_domain = sds_service.list(search='name={}'.format(storage_domain_name))[0] Now: I have no real clue on which ID "92444a95-0be7-4589-ac46-1ed6dfe7ed4c'" but digging in the engine logs it refers to StorageServerConnections ID: [root@ovirt-engine ovirt-engine]# zgrep 92444a95-0be7-4589-ac46-1ed6dfe7ed4c *.gz engine.log-20201108.gz:2020-11-07 06:05:54,352+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) [3ffb810c] START, ConnectStorageServerVDSCommand(HostName = another-server.foo.com, StorageServerConnectionManagementVDSParameters:{hostId='7d202bc7-002b-4426-8446-99b6b346874e', storagePoolId='82d0b3de-0334-451c-8321-c3533de9a894', storageType='LOCALFS', connectionList='[StorageServerConnections:{id='92444a95-0be7-4589-ac46-1ed6dfe7ed4c', connection='/data', iqn='null', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}]', sendNetworkEventOnFailure='true'}), log id: 1509fe17 As I said, I tried to execute the script from several hosts: some of them with oVirt 4.3 and other with oVirt 4.4 but it can run, or not, on both of versions. When I try to manage the storage domain via ovirt-engine GUI on the hosts that the script exit with the mentioned error, I recieve the following error: Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : Cannot read property 'a' of null Please have your administrator check the UI logs Any slightest idea on what is going on? Thank you for your time and help, Francesco

2 3

Best and clean way to have oVirt qemu and libvirt versions on CentOS 8
by Gianluca Cecchi 22 Nov '20

22 Nov '20

Hello, normally with current CentOS 8.2 I get qemu-kvm-core-15:2.12.0-99.module_el8.2.0+524+f765f7e0.4.x86_64 libvirt-daemon-4.5.0-42.module_el8.2.0+320+13f867d7.x86_64 With oVirt 4.4 having qemu-kvm-core-4.2.0-29.el8.3.x86_64 libvirt-daemon-6.0.0-25.2.el8.x86_64 and in current Fedora 32 updates: qemu-kvm-core-4.2.1-1.fc32.x86_64.rpm libvirt-daemon-6.1.0-4.fc32.x86_64.rpm I see on CentOS these groups somehow related to Virtualization: Virtualization Host Virtualization Client Virtualization Hypervisor Virtualization Platform Virtualization Tools What could be the best and less intrusive repo to enable on plain CentOS 8.2 to get qemu-kvm and libvirt versions quite similar to oVirt shipped ones, or fedora ones, without enabling all the ovirt 4.4 repos? Thanks, Gianluca

2 2

ovirt-imageio-proxy not working after updating SSL certificates with a wildcard cert issued by AlphaSSL (intermediate)
by Lynn Dixon 22 Nov '20

22 Nov '20

All, I recently bought a wildcard certificate for my lab domain (shadowman.dev) and I replaced all the certs on my RHV4.3 machine per our documentation. The WebUI presents the certs successfully and without any issues, and everything seemed to be fine, until I tried to upload a disk image (or an ISO) to my storage domain. I get this error in the events tab: https://share.getcloudapp.com/p9uPvegx [image: image.png] I also see that the disk is showing up in my storage domain, but its showing "Paused by System" and I can't do anything with it. I cant even delete it! I have tried following this document to fix the issue, but it didn't work: https://access.redhat.com/solutions/4148361 I am seeing this error pop into my engine.log: https://pastebin.com/kDLSEq1A And I see this error in my image-proxy.log: WARNING 2020-07-24 15:26:34,802 web:137:web:(log_error) ERROR [172.17.0.30] PUT /tickets/ [403] Error verifying signed ticket: Invalid ovirt ticket (data='------my_ticket_data-----', reason=Untrusted certificate) [request=0.002946/1] Now, when I bought my wildcard, I was given a root certificate for the CA, as well as a separate intermediate CA certificate from the provider. Likewise, they gave me a certificate and a private key of course. The root and intermediate CA's certificates have been added to /etc/pki/ca-trust/source/anchors/ and I did an update-ca-trust. I also started experiencing issues with the ovpn network provider at the same time I replaced the SSL certs, but I disregarded it at the time, but now I am thinking its related. Any advice on what to look for to fix the ovirt-imageio-proxy? Thanks! *Lynn Dixon* | Red Hat Certified Architect #100-006-188 *Solutions Architect* | NA Commercial Google Voice: 423-618-1414 Cell/Text: 423-774-3188 Click here to view my Certification Portfolio <http://red.ht/1XMX2Mi>

6 8

Re: Fix corrupt self-hosted engine
by Alex K 22 Nov '20

22 Nov '20

For the records, After having fixed the major fs issues with guestfish and since the DB was not starting up, I removed everything from DB data dir and recreated it as below: rm -rf /var/opt/rh/rh-postgresql10/lib/pgsql/data/* /opt/rh/rh-postgresql10/root/usr/bin/postgresql-setup --initdb systemctl restart rh-postgresql10-postgresql.service Then proceeded with the restoration, where I requested to provision all missing databases: engine-backup --mode=restore --file=engine-backup.gz --provision-all-databases \ --log=restore.log --restore-permissions Following this, ran engine-setup, as instructed from the restore operation. Gained engine web access and saw the same running VMs were shown as up without issues. I only observed one VM not able to start due to illegal volume, but that's another story. On Thu, Nov 19, 2020 at 9:42 PM Alex K <rightkicktech(a)gmail.com> wrote: > > > On Thu, Nov 19, 2020 at 5:31 PM Alex K <rightkicktech(a)gmail.com> wrote: > >> Hi Didi, >> >> On Thu, Nov 19, 2020 at 5:13 PM Yedidyah Bar David <didi(a)redhat.com> >> wrote: >> >>> On Thu, Nov 19, 2020 at 4:37 PM Alex K <rightkicktech(a)gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> I have a corrupt self-hosted engine (with several file system errors, >>>> postgres not able to start) and thus it does not give access to the web UI. >>>> This happened following an unlucky split brain resolution (I am running 2 >>>> nodes). The two hosts are running VMs also which I would like to keep >>>> running as they are needed. >>>> >>>> When trying to boot into rescue mode (using >>>> systemd.unit=emergency.target boot parameter) I get a cursor and nothing >>>> else. >>>> >>> >>> This means that more than just the DB is corrupt... >>> >>> >>>> >>>> I have backups of engine files with scope all (using the engine-backup >>>> tool). >>>> What is the best approach to try and fix the engine or redeploy. >>>> >>> >>> If you are careful, and know what you are doing, you can try something >>> like the following. I am not giving many details, hopefully you can find on >>> the net tutorials about how to use the things I suggest: >>> >>> 1. Move to global maintenance >>> >>> 2. Stop the current dead vm (if needed) >>> >>> 3. Find current vm conf, edit it to boot from a rescue iso image of your >>> preference or from net/PXE etc., and start the vm with '--vm-conf' pointing >>> to your edited file. >>> >>> 4. Connect a console (hosted-engine --console, or 'virsh console', or >>> use '--add-console-password' and remote viewer, if needed) >>> >>> 5. Clean the disk and install the OS, oVirt, etc. >>> >>> 6. Copy your backup into the vm and restore with engine-backup >>> >>> 7. Then cleanly stop the machine, exit global maint, and let HA start it >>> (or start it yourself with --vm-start). >>> >>> At the time, we had a bug [1] to document this. The result is [2]. It >>> does not detail how to boot/reinstall os/etc., only restore (if e.g. db is >>> dead but fs is ok). >>> For something somewhat similar to what you want, see also [3], which >>> uses guestfish. Might be useful, depending on how badly your disk is >>> corrupted. >>> >> I went with the guestfish approach. It has fixed some fs issues and now >> the yum etc seem fine apart from postgres. >> I had tried previously to uninstall/install packages so I ended >> installing them again with yum install ovirt\*setup\*. >> Now I think I have to run engine-setup but I get the error: >> >> Failed to execute stage 'Environment setup': Cannot connect to Engine >> database using existing credentials: engine@localhost:5432 >> > Seems that I need to have psql running to be able to run engine-backup > --mode=restore. Are there any steps how one could manually prepare pgsql > for ovirt so as to attempt restoration? > >> >> So I guess I need to follow [2]. What do you think? >> >> >>> How did you run into a split brain? There is a lock on the shared >>> storage that should prevent this. >>> >>> Good luck and best regards, >>> >>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1482710 >>> [2] >>> https://www.ovirt.org/documentation/administration_guide/#Overwriting_a_Sel… >>> [3] https://bugzilla.redhat.com/show_bug.cgi?id=1569827#c4 >>> -- >>> Didi >>> >>

2 1

User portal and DNS entries removal
by Nathanaël Blanchet 21 Nov '20

21 Nov '20

2 1

Can't delete a disk after a failed upload
by lorenzobarbati02＠gmail.com 21 Nov '20

21 Nov '20

Hi, After trying to upload an ISO via the web interface, the upload remains in the "paused by system" state. When I click "cancel" in the upload menu the status stops at "finalizing cleanup". Is there an alternative way to delete this disk?

1 0

Found a host rebooting - ways to watch?
by Chris Adams 20 Nov '20

20 Nov '20

I just noticed that one of my oVirt physical hosts has been rebooting due to an apparent hardware voltage fault. It's a Dell, and I've got their tools installed and am monitoring status, but the issue clears itself. It has apparently been doing this for a bit now, and we didn't catch it because (a) there weren't any VMs on it (probably were the first time but they were restarted elsewhere fast enough that it wasn't noticed) and (b) it reboots fast enough that at most it pops up in our monitoring system for one pass and then clears so our NOC either didn't see it or assumed it was okay since it cleared. oVirt has been logging alerts when it happens, but seeing that requires someone to log in and check the logs (and we've got a bunch of different systems to manage, including multiple oVirt clusters, so nobody is doing that on a regular basis). We monitor most things with SNMP and/or CLI checks (we have PRTG, Nagios, and LibreNMS for various different things). What are people doing to monitor the health of their oVirt systems? Is it possible to get alerts emailed to admins? Is there any SNMP support in oVirt to allow external systems to monitor its health? This setup is on 4.3.10 if that matters. -- Chris Adams <cma(a)cmadams.net>

2 2

Re: EPYC CPU not being detected correctly on cluster
by Lucia Jelinkova 20 Nov '20

20 Nov '20

Hi, oVirt CPU detection depends on libvirt (and that depends on qemu) CPU models. Could you please run the following command to see what libvirt reports? virsh domcapabilities That should give you the list of CPUs known to libvirt with a usability flag for each CPU. If you find out that the CPU is not usable by libvirt, you might want to dig deeper by querying quemu directly. Locate any VM running on the system by sudo virsh list --all Use the name of a VM in the following command: sudo virsh qemu-monitor-command [your-vm's-name] --pretty '{"execute":"query-cpu-definitions"}' That would give you the list of all CPUs supported by qemu and it will list all cpu's features that are not available on your system. Regards, Lucia On Thu, Nov 19, 2020 at 9:38 PM Vinícius Ferrão via Users <users(a)ovirt.org> wrote: > Hi > > > > I’ve an strange issue with two hosts (not using the hypervisor image) with > EPYC CPUs, on the engine I got this message: > > > > The host CPU does not match the Cluster CPU Type and is running in a > degraded mode. It is missing the following CPU flags: model_EPYC. Please > update the host CPU microcode or change the Cluster CPU Type. > > > > But it is an EPYC CPU, the firmware is updated to the latest versions, but > for some reason oVirt does not like it. > > > > Here’s the relevant output from VDSM: > > "cpuCores": "128", > > "cpuFlags": > "ibs,vme,abm,sep,ssse3,perfctr_core,sse4_2,skip-l1dfl-vmentry,cx16,pae,misalignsse,avx2,smap,movbe,vgif,rdctl-no,extapic,clflushopt,de,sse4_1,xsaveerptr,perfctr_llc,fma,mca,sse,rdtscp,monitor,umip,mwaitx,cr8_legacy,mtrr,stibp,bmi2,pclmulqdq,amd-ssbd,lbrv,pdpe1gb,constant_tsc,vmmcall,f16c,ibrs,fsgsbase,invtsc,nopl,lm,3dnowprefetch,smca,ht,tsc_adjust,popcnt,cpb,bmi1,mmx,arat,aperfmperf,bpext,cqm_occup_llc,virt-ssbd,tce,pse,xsave,xgetbv1,topoext,sha_ni,amd_ppin,rdrand,cpuid,tsc_scale,extd_apicid,cqm,rep_good,tsc,sse4a,flushbyasid,pschange-mc-no,mds-no,ibpb,smep,clflush,tsc-deadline,fxsr,pat,avx,pfthreshold,v_vmsave_vmload,osvw,xsavec,cdp_l3,clzero,svm_lock,nonstop_tsc,adx,hw_pstate,spec-ctrl,arch-capabilities,xsaveopt,skinit,rdt_a,svm,rdpid,lahf_lm,fpu,rdseed,fxsr_opt,sse2,nrip_save,vmcb_clean,sme,cat_l3,cqm_mbm_local,irperf,overflow_recov,avic,mce,mmxext,msr,cx8,hypervisor,wdt,mba,nx,decodeassists,cmp_legacy,x2apic,perfctr_nb,succor,pni,xsaves,clwb,cqm_llc,syscall,apic,pge,npt,pse36,cmov,ssbd,pausefilter,sev,aes,wbnoinvd,cqm_mbm_total,spec_ctrl,model_qemu32,model_Opteron_G3,model_Nehalem-IBRS,model_qemu64,model_Conroe,model_kvm64,model_Penryn,model_SandyBridge,model_pentium,model_pentium2,model_kvm32,model_Nehalem,model_Opteron_G2,model_pentium3,model_Opteron_G1,model_SandyBridge-IBRS,model_486,model_Westmere-IBRS,model_Westmere", > > "cpuModel": "AMD EPYC 7H12 64-Core Processor", > > "cpuSockets": "2", > > "cpuSpeed": "3293.405", > > "cpuThreads": "256", > > > > Any ideia on why ou what to do to fix it? > > > > Thanks, > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/WP6XL6ODTLJVB… >

2 1

Upgrade hyperconverged self-hosted ovirt from 4.3 to 4.4
by ralf＠os-s.de 20 Nov '20

20 Nov '20

Hi, has anyone attempted an upgrade from 4.3 to 4.4 in a hyperconverged self-hosted setup? The posted guidelines seem a bit contradictive and not complete. Has anyone tried it and could share his experiences? I am currently having problems when deploying the hosted engine and restoring. The host becomes unresponsive and has hung tasks. Kind regards, Ralf

3 6

change domain name from export domain
by jb 20 Nov '20

20 Nov '20

Hello, I needed to rename all domain names from my NFS storage. VM data and seconds data domains was no problem. But when I try to rename the domain from export domain, a red popup on top opens with this message: Uncaught exception occurred. Please try reloading the page. Details: (TypeError) : ZOj(...) is null Please have your administrator check the UI logs I also notice that, when I rename the path an hit enter, it doesn't write anything to the engine.log Is this a known issue? Best regards Jonathan

1 0

Ovirt 4 2 NIC's
by Facundo Badaracco 20 Nov '20

20 Nov '20

Hi everyone! Hope someone can help me with this.. I have 3 servers with centos 8 and ovirt 4 installed. Each server has 2 nic. Server A = HE (HA) Nic1= 192.169.2.24 Nic2=no ip Server B = HE (HA) Nic1= 192.169.2.25 Nic2=no ip Server C = simply host. Nic1= 192.169.2.26 Nic2=no ip How can i configure the second NIC in each server in order to use it for clients connect to the vms?. I want one nic for management, the other for connections.

2 1

Can't use ovirt web interface (500 error)
by lorenzobarbati02＠gmail.com 20 Nov '20

20 Nov '20

Hi, After updating to the latest version of ovirt (standalone installed with engine-setup) I am no longer able to use the web ui. After I log in, in fact, I get a modal error entitled "operation canceled" and with content "a request to the server failed, error 500" Looking at the requests it actually receives an error 500 when it goes to make a request to "/ovirt-engine/webadmin/GenericApiGWTService" which replies "The call failed on the server; see server log for details" These are the last lines of the engine.log: https://pastebin.com/uFgZASuW Is anyone experiencing the same problem or know how to fix it?

2 1

How do you manage OVN?
by Alex McWhirter 20 Nov '20

20 Nov '20

I'm not sure if I' missing something, but it seems there is no way built in to oVirt to manage OVN outside of network / subnet creation. In particular routing both between networks and to external networks. Of course you have the OVN utilities, but it seems that the provider API is the preffered method of interaction? As far as i can tell, the only utility that can use this API as intended is ManageIQ, which is a bit a behemoth if you only need the OVN portion of things. So is that it then? Interface with the API directly or use ManageIQ? Just curious what others are doing in regards to OVN.

2 1

Need documentation on how to use grafana with ovirt
by wodel youchi 20 Nov '20

20 Nov '20

Hi, Is there any documentation explaining how to use grafana portal to extract metrics data from ovirt ? Regards.

2 1

Re: ovirt 4.3 - locked image vm - unable to remove a failed deploy of a guest dom
by 3c Monitor 20 Nov '20

20 Nov '20

Hi, anyone with an idea on what else I can do? Thanks a lot.

1 0

EPYC CPU not being detected correctly on cluster
by Vinícius Ferrão 19 Nov '20

19 Nov '20

Hi I've an strange issue with two hosts (not using the hypervisor image) with EPYC CPUs, on the engine I got this message: The host CPU does not match the Cluster CPU Type and is running in a degraded mode. It is missing the following CPU flags: model_EPYC. Please update the host CPU microcode or change the Cluster CPU Type. But it is an EPYC CPU, the firmware is updated to the latest versions, but for some reason oVirt does not like it. Here's the relevant output from VDSM: "cpuCores": "128", "cpuFlags": "ibs,vme,abm,sep,ssse3,perfctr_core,sse4_2,skip-l1dfl-vmentry,cx16,pae,misalignsse,avx2,smap,movbe,vgif,rdctl-no,extapic,clflushopt,de,sse4_1,xsaveerptr,perfctr_llc,fma,mca,sse,rdtscp,monitor,umip,mwaitx,cr8_legacy,mtrr,stibp,bmi2,pclmulqdq,amd-ssbd,lbrv,pdpe1gb,constant_tsc,vmmcall,f16c,ibrs,fsgsbase,invtsc,nopl,lm,3dnowprefetch,smca,ht,tsc_adjust,popcnt,cpb,bmi1,mmx,arat,aperfmperf,bpext,cqm_occup_llc,virt-ssbd,tce,pse,xsave,xgetbv1,topoext,sha_ni,amd_ppin,rdrand,cpuid,tsc_scale,extd_apicid,cqm,rep_good,tsc,sse4a,flushbyasid,pschange-mc-no,mds-no,ibpb,smep,clflush,tsc-deadline,fxsr,pat,avx,pfthreshold,v_vmsave_vmload,osvw,xsavec,cdp_l3,clzero,svm_lock,nonstop_tsc,adx,hw_pstate,spec-ctrl,arch-capabilities,xsaveopt,skinit,rdt_a,svm,rdpid,lahf_lm,fpu,rdseed,fxsr_opt,sse2,nrip_save,vmcb_clean,sme,cat_l3,cqm_mbm_local,irperf,overflow_recov,avic,mce,mmxext,msr,cx8,hypervisor,wdt,mba,nx,decodeassists,cmp_legacy,x2apic,perfctr_nb,succor,pni,xsaves,clwb,cqm_llc,syscall,apic,pge,npt,pse36,cmov,ssbd,pausefilter,sev,aes,wbnoinvd,cqm_mbm_total,spec_ctrl,model_qemu32,model_Opteron_G3,model_Nehalem-IBRS,model_qemu64,model_Conroe,model_kvm64,model_Penryn,model_SandyBridge,model_pentium,model_pentium2,model_kvm32,model_Nehalem,model_Opteron_G2,model_pentium3,model_Opteron_G1,model_SandyBridge-IBRS,model_486,model_Westmere-IBRS,model_Westmere", "cpuModel": "AMD EPYC 7H12 64-Core Processor", "cpuSockets": "2", "cpuSpeed": "3293.405", "cpuThreads": "256", Any ideia on why ou what to do to fix it? Thanks,

1 0

[ANN] oVirt 4.4.4 Second Release Candidate is now available for testing
by Lev Veyde 19 Nov '20

19 Nov '20

oVirt 4.4.4 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.4 Second Release Candidate for testing, as of November 19th, 2020. This update is the fourth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.4 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.4 (redeploy in case of already being on 4.4.4). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.4 release highlights: http://www.ovirt.org/release/4.4.4/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.4/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

OVIRT and KUBEVIRT
by Andre Meyer Pflug 19 Nov '20

19 Nov '20

Is there someone who has done an NON PERSISTANT VDI over oVirt using kubevirt (on OKD) as the infraestructure for vm's? We plan to do a 1.000.000 concurrent users deployment... Any help is welcome! Kind regards, Andre Meyer Pflug DDESK LLC

3 2

Self Hosted Engine a single Bare Metal Server
by LS CHENG 19 Nov '20

19 Nov '20

Hi We are planning to set up a single ovirt node for testing. It is a single Bare Metal Server. I wonder if there is any problem setting up a Self Hosted Engine in this Bare Metal (there is no HA but we don't need it in this case)? I know it is probably not the best practice but it is for training and testing purposes. Thank you

1 0

Fix corrupt self-hosted engine
by Alex K 19 Nov '20

19 Nov '20

Hi all, I have a corrupt self-hosted engine (with several file system errors, postgres not able to start) and thus it does not give access to the web UI. This happened following an unlucky split brain resolution (I am running 2 nodes). The two hosts are running VMs also which I would like to keep running as they are needed. When trying to boot into rescue mode (using systemd.unit=emergency.target boot parameter) I get a cursor and nothing else. I have backups of engine files with scope all (using the engine-backup tool). What is the best approach to try and fix the engine or redeploy. Thanks for any help. Alex

2 2

Re: oVirt Node Crash
by Anton Louw 19 Nov '20

19 Nov '20

Hi Sandro, Have you perhaps seen anything in the SOS report that could shed some light on the issues? Thanks Anton Louw Cloud Engineer: Storage and Virtualization ______________________________________ D: 087 805 1572 | M: N/A A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg anton.louw(a)voxtelecom.co.za www.vox.co.za From: Anton Louw Sent: 16 November 2020 07:30 To: Sandro Bonazzola <sbonazzo(a)redhat.com>; Arik Hadas <ahadas(a)redhat.com>; Dominik Holler <dholler(a)redhat.com> Cc: users(a)ovirt.org; Johan Koen <Johan.Koen(a)voxtelecom.co.za> Subject: RE: [ovirt-users] oVirt Node Crash I have also attached the SOS report as requested From: Anton Louw Sent: 16 November 2020 06:54 To: Sandro Bonazzola <sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>>; Arik Hadas <ahadas(a)redhat.com<mailto:ahadas@redhat.com>>; Dominik Holler <dholler(a)redhat.com<mailto:dholler@redhat.com>> Cc: users(a)ovirt.org<mailto:users@ovirt.org>; Johan Koen <Johan.Koen(a)voxtelecom.co.za<mailto:Johan.Koen@voxtelecom.co.za>> Subject: RE: [ovirt-users] oVirt Node Crash Hi Sandro, Thanks for the response. I logged onto oVirt this morning, and I see the node is in a “Unassigned” state. I can ping it, but cannot SSH, so there is something that is causing the host to be unresponsive. On Saturday after I sent the mail, I opened a console to the node, and I saw the below entries before logging in: audit:backlog limit exceeded I the tried the solution of increasing the buffer size in the audit.rules file in /etc/audit/rules.d/ , as per below, but it did not resolve the issue. ## First rule - delete all -D ## Increase the buffers to survive stress events. ## Make this bigger for busy systems -b 8192 ## Set failure mode to syslog -f 1 Is it possible to upgrade the node to 4.4 while the engine is still on 4.3? Thanks From: Sandro Bonazzola <sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>> Sent: 13 November 2020 18:39 To: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>>; Arik Hadas <ahadas(a)redhat.com<mailto:ahadas@redhat.com>>; Dominik Holler <dholler(a)redhat.com<mailto:dholler@redhat.com>> Cc: users(a)ovirt.org<mailto:users@ovirt.org>; Johan Koen <Johan.Koen(a)voxtelecom.co.za<mailto:Johan.Koen@voxtelecom.co.za>> Subject: Re: [ovirt-users] oVirt Node Crash Il giorno ven 13 nov 2020 alle ore 17:37 Sandro Bonazzola <sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com>> ha scritto: Il giorno ven 13 nov 2020 alle ore 13:38 Anton Louw via Users <users(a)ovirt.org<mailto:users@ovirt.org>> ha scritto: Hi Everybody, I have built a new host which has been running fine for the last couple of days. I noticed today that the host crashed, but it is not giving me a reason as to why. It happened at 13:45 today, but I have given time before that on the logs as well. Is there something I am missing here? Not related to the crash, but I see in the logs that 5 out of 20 guests have qemu guest agent not responding. Also you seem to have some issues with some firewalld rules. (Maybe +Dominik Holler<mailto:dholler@redhat.com> would like to have a look) I don't see anything explaining why the host got rebooted. Still related to guest agent I find a bit alarming the following lines: Nov 13 13:29:34 jb2-node03 libvirtd: 2020-11-13 11:29:34.294+0000: 12603: error : qemuDomainAgentAvailable:9144 : Guest agent is not responding: QEMU guest agent is not connected Nov 13 13:29:34 jb2-node03 vdsm[13843]: ERROR Shutdown by QEMU Guest Agent failed#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5304, in qemuGuestAgentShutdown#012 self._dom.shutdownFlags(libvirt.VIR_DOMAIN_SHUTDOWN_GUEST_AGENT)#012 File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 100, in f#012 ret = attr(*args, **kwargs)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper#012 ret = f(*args, **kwargs)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in wrapper#012 return func(inst, *args, **kwargs)#012 File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2517, in shutdownFlags#012 if ret == -1: raise libvirtError ('virDomainShutdownFlags() failed', dom=self)#012libvirtError: Guest agent is not responding: QEMU guest agent is not connected Nov 13 13:29:42 jb2-node03 kernel: vlan0077: port 11(vnet15) entered disabled state Nov 13 13:29:42 jb2-node03 kernel: device vnet15 left promiscuous mode Nov 13 13:29:42 jb2-node03 kernel: vlan0077: port 11(vnet15) entered disabled state Nov 13 13:29:42 jb2-node03 NetworkManager[6027]: <info> [1605266982.6539] device (vnet15): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Nov 13 13:29:42 jb2-node03 NetworkManager[6027]: <info> [1605266982.6550] device (vnet15): released from master device vlan0077 Nov 13 13:29:42 jb2-node03 libvirtd: 2020-11-13 11:29:42.669+0000: 12557: error : qemuMonitorIO:718 : internal error: End of file from qemu monitor +Arik Hadas<mailto:ahadas@redhat.com> any clue? About the crash, can you please provide full sos report from the host? the log you provided is not enough to understand what caused the reported crash Also, given python2 is used here, I assume you're on 4.3 or older. I would recommend to upgrade to 4.4 as soon as practical. Thanks Anton Louw Cloud Engineer: Storage and Virtualization at Vox ________________________________ T: 087 805 0000 | D: 087 805 1572 M: N/A E: anton.louw(a)voxtelecom.co.za<mailto:anton.louw@voxtelecom.co.za> A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg www.vox.co.za<http://www.vox.co.za> [F]<https://www.facebook.com/voxtelecomZA> [T]<https://www.twitter.com/voxtelecom> [I]<https://www.instagram.com/voxtelecomza/> [L]<https://www.linkedin.com/company/voxtelecom> [Y]<https://www.youtube.com/user/VoxTelecom> [#VoxBrand]<https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME> Disclaimer The contents of this email are confidential to the sender and the intended recipient. Unless the contents are clearly and entirely of a personal nature, they are subject to copyright in favour of the holding company of the Vox group of companies. Any recipient who receives this email in error should immediately report the error to the sender and permanently delete this email from all storage devices. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more Click Here<https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>. _______________________________________________ Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html<https://www.ovirt.org/privacy-policy.html> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/<https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/XMRUDMRBYZKUJ…<https://lists.ovirt.org/archives/list/users@ovirt.org/message/XMRUDMRBYZKUJ…> -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA<https://www.redhat.com/> sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com> [https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png]<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. <https://mojo.redhat.com/docs/DOC-1199578> -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA<https://www.redhat.com/> sbonazzo(a)redhat.com<mailto:sbonazzo@redhat.com> [https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png]<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. <https://mojo.redhat.com/docs/DOC-1199578>

2 3

How to create a backup in event of hardware failure of a single hosted engine?
by ernestclydeachua＠gmail.com 18 Nov '20

18 Nov '20

Hello everyone, Currently we have a single bare metal that hosts oVirt and glusterFS which later on to be converted to a 3 nodes for HCI, currently another bare metal is coming this week and was planning to initially create it as a backup. is it possible to deploy a new hosted engine then create a gluster volume for 1st one as a backup domain then attach it to the new one if hardware failure occurred, or there is another kind of setup that can be done?

3 4

Migration VM
by tiziano.pacioni＠par-tec.it 18 Nov '20

18 Nov '20

Hi, I installed a new server, using the ovirt iso, with the target of migrating the VMs coming from another cluster, contained on another ovirt node. I tried to migrate a vm using the Export Domain, once imported on the new node, i see the vm from web dashboard but, from command line “virsh list --all” is absent, the imported vm does not appear in the list. Also if I try to start it, I get the following error: VM X is down with error. Exit message: unsupported configuration: bus must be 0 for ide controller. Can you help me?

2 3

Re: Hosted Engine can't migrate
by Strahil Nikolov 18 Nov '20

18 Nov '20

Hi Bradley, usually this is not supposed to happen. I can propose you a fast fix: - Set a node into maintenance (via the UI) and then from the "Installation" drop down menu (upper right) click "reinstall" There is a tab for the HostedEngine and you have to mark it as deployed/installed If it doesn't work,ssh to one of the hosts and provide the output of: hosted-engine --vm-status Best Regards В сряда, 18 ноември 2020 г., 08:08:36 Гринуич+2, McNamara, Bradley <bradley.mcnamara(a)seattle.gov> написа: I'm new to oVirt, but not new to virtualization technologies. I've run into a wall, but the solution has gotta be simple. I've seen other threads with the same issue, but a solution is never posted. I've followed the guide perfectly. I get the self-hosted engine up and running with no issues. I add hosts to the cluster, but it won't let me migrate the HE because of Hosted Engine HA score of "N/A" on every host except the one it was initially deployed on. The physical servers are exactly the same: same networks, storage, OS, patches, etc. The additional hosts are added thru the HE GUI and are added without issue. Is there a secret button I gotta push? What am I missing? This is with 4.3 on CentOS 7.9. HELP! Thanks. :-) _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TKNPG3TRZGZIU…

1 0

Re: Hosted Engine can't migrate
by Gianluca Cecchi 18 Nov '20

18 Nov '20

On Wed, Nov 18, 2020 at 7:08 AM McNamara, Bradley < Bradley.McNamara(a)seattle.gov> wrote: > I'm new to oVirt, but not new to virtualization technologies. I've run > into a wall, but the solution has gotta be simple. I've seen other threads > with the same issue, but a solution is never posted. > > I've followed the guide perfectly. I get the self-hosted engine up and > running with no issues. I add hosts to the cluster, but it won't let me > migrate the HE because of Hosted Engine HA score of "N/A" on every host > except the one it was initially deployed on. The physical servers are > exactly the same: same networks, storage, OS, patches, etc. The > additional hosts are added thru the HE GUI and are added without issue. Is > there a secret button I gotta push? > > What am I missing? This is with 4.3 on CentOS 7.9. > > HELP! Thanks. :-) > If you go in Compute --> Hosts in web admin gui, do the added hosts have a crown icon on the left of their "Name" column? If not, when you added them possibly you overlooked the "Hosted Engine" section in the window, where by default, if I'm not wrong, the value is "None": that means that the added host doesn't contributed to be one of the "Hosted Engine" ones electable to host the engine VM, but only an hyoervisor. Long time ago I opened two bugzillas about this default with some notes for improving a better experience.... If this is the case, you can remove the hosts one by one and add them again selecting "Deploy" in the Hosted Engine section, for how many you would like to contribute to the score and to be able to host the hosted engine VM. HIH, Gianluca

1 0

Re: Hosted Engine can't migrate
by Yedidyah Bar David 18 Nov '20

18 Nov '20

Hi, On Wed, Nov 18, 2020 at 8:08 AM McNamara, Bradley <Bradley.McNamara(a)seattle.gov> wrote: > > I'm new to oVirt, but not new to virtualization technologies. I've run into a wall, but the solution has gotta be simple. I've seen other threads with the same issue, but a solution is never posted. > > I've followed the guide perfectly. I get the self-hosted engine up and running with no issues. I add hosts to the cluster, but it won't let me migrate the HE because of Hosted Engine HA score of "N/A" on every host except the one it was initially deployed on. The physical servers are exactly the same: same networks, storage, OS, patches, etc. The additional hosts are added thru the HE GUI and are added without issue. Is there a secret button I gotta push? > > What am I missing? This is with 4.3 on CentOS 7.9. Can other VMs migrate (who use the same storage server, so you know it's not a storage/network issue)? Please check/share /var/log/ovirt-hosted-engine-ha/* on all hosts, as well as output of 'hosted-engine --vm-status' on all of them. Good luck and best regards, -- Didi

1 0

Hosted Engine can't migrate
by McNamara, Bradley 17 Nov '20

17 Nov '20

I'm new to oVirt, but not new to virtualization technologies. I've run into a wall, but the solution has gotta be simple. I've seen other threads with the same issue, but a solution is never posted. I've followed the guide perfectly. I get the self-hosted engine up and running with no issues. I add hosts to the cluster, but it won't let me migrate the HE because of Hosted Engine HA score of "N/A" on every host except the one it was initially deployed on. The physical servers are exactly the same: same networks, storage, OS, patches, etc. The additional hosts are added thru the HE GUI and are added without issue. Is there a secret button I gotta push? What am I missing? This is with 4.3 on CentOS 7.9. HELP! Thanks. :-)

1 0

Upgrading engine from 4.3 -> 4.4
by David Metcalf 17 Nov '20

17 Nov '20

Followed this for standalone hosts: https://ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3 but get this message.. engine-backup --mode=restore --file=engine-backup-2020-11-16.bak --provision-all-databases ... FATAL: Backup was created by version '4.3.9.4' and can not be restored using the installed version 4.4.3.11

2 1

ovirt-shell SSL Error
by FRIES, Dirk, SHS Informatik 17 Nov '20

17 Nov '20

Hello there, I am trying to connect via ovirt-shell to my ovirt manager. To do this I've downloaded the CA File (https://127.0.0.1/ovirt-engine/services/pki-resource?resource=ca-certificat…) to /tmp and set up my config in .ovirtshellrc : [cli] autoconnect = True autopage = True [ovirt-shell] username = adminuser renew_session = False timeout = None extended_prompt = False url = https://127.0.0.1/api insecure = False kerberos = False filter = False session_timeout = None ca_file = /tmp/pki-resource?resource=ca-certificate dont_validate_cert_chain = True key_file = None password = somepassword cert_file = None So when I am trying to connect I get the following error: (60, "Peer's certificate issuer has been marked as not trusted by the user.") While researching I also found a pretty similar issue here https://lists.ovirt.org/archives/list/users@ovirt.org/thread/IYG6AQPII25366… but unfortunally there is no solution posted. Does anyone have a hint for me what could cause this problem or where to look else ? Thanks a lot ! Bye, Dirk

2 1

Re: Really slow manager node
by Nicolás 17 Nov '20

17 Nov '20

Hi Toni, (re-adding the users(a)ovirt.org list) El 16/11/20 a las 23:37, tferic(a)swissonline.ch escribió: > > Hi, > > Chances are, that this performance issue may be unrelated to oVirt. > > The first thing that comes to my mind is that the system may have a > bottleneck on the I/O. > > > Please have a look at: > > iostat -x 5 > > The system may have problems with disk performance, if %util > 95 and > avgqu-sz > 3 over longer periods of time. > > Actually %util never goes beyond the 85%, being the average on 70%; for the avgqu-sz, the average value is about 25 (with peaks of 160 as far as I could see). > If that's not the case, you may next want to have a look at limits > (/etc/security/limits.conf). > > There may also be default limits which may be too low. (nofile, nproc > come to my mind) > > This file seems not to have been touched (all the content is commented out). > Are there any errors or warnings in the messages or audit logs? > > Nothing special, I've checked for the last couple days and everything seems ok. > And also htop, iotop, vmstat may help to get a quick overview. > > Yep, I've used most of these commands to check, but I've been unable to see something clarifying. In my opinion the slowness could be caused for not using SSD disks and because of a low polling interval by the DWHd, but that's just my assumption and I've been unable to get some data that would confirm this. Thanks for the help! Nico > Hope this helps, > > Toni > > > On 16.11.20 14:08, Nicolás wrote: >> Hi, >> >> We're running oVirt 4.3.8 and even if this is a problem we've had >> since a lot of time (I would say since 4.0.x), I decided to look for >> help in case anything can be done. >> >> Our environment is heavily used by users in our University (about >> 3000 users), and currently our oVirt infrastructure has 1928 virtual >> machines, being 882 of them currently running. We have a separate >> physical machine for the manager node, and the problem is that this >> machine is very, very, very slow, despite it has (from my point of >> view) enough physical resources to run efficiently. >> >> By slow I mean even the SSH access to it takes about 10 seconds, not >> just the admin/user portals. Any operation takes enough time to make >> the experience not comfortable to our users (enter the VM portal, >> start a VM, open a console...). >> >> Node machine's parameters are: >> 18GB of RAM memory >> 1 processor with 12CPUs >> 300GB SCSI Disk, local storage. No Storage Domain is stored in this >> node machine. >> >> Currently, most consuming processes are: >> >> 28802 ovirt 20 0 3302876 1,5g 25988 S 1,0 8,7 22:46.36 >> ovirt-engine -server -XX:+TieredCompilation -Xms1024M -Xmx1024M >> -Xss1M -Djava.aw+ >> 28701 ovirt 20 0 5465432 807704 13140 S 5,9 4,4 3:15.53 >> ovirt-engine-dwhd >> -Dorg.ovirt.engine.dwh.settings=/tmp/tmp8wtnTA/settings.proper+ >> >> # free -m >> total used free shared buff/cache >> available >> Mem: 17886 6669 2734 255 8482 10625 >> Swap: 6143 1002 5141 >> >> There are also a lot of postgresql processes: >> >> postgres 2186 0.0 0.0 261812 4136 ? Ss jun05 37:39 >> /opt/rh/rh-postgresql10/root/usr/bin/postmaster -D >> /var/opt/rh/rh-postgresql10/lib/pgsql/data >> postgres 3176 0.0 0.0 216084 656 ? Ss jun05 0:00 >> postgres: logger process >> postgres 3290 0.0 0.2 262204 37476 ? Ss jun05 77:31 >> postgres: checkpointer process >> postgres 3291 0.3 0.2 262052 36960 ? Ss jun05 754:02 >> postgres: writer process >> postgres 3292 0.0 0.0 261812 1988 ? Ss jun05 100:51 >> postgres: wal writer process >> postgres 3293 0.0 0.2 262380 36748 ? Ss jun05 21:58 >> postgres: autovacuum launcher process >> postgres 3294 0.1 0.0 219216 1412 ? Ds jun05 335:41 >> postgres: stats collector process >> postgres 3295 0.0 0.0 262220 1460 ? Ss jun05 0:11 >> postgres: bgworker: logical replication launcher >> postgres 3393 0.0 0.2 265792 40452 ? Ss jun05 15:36 >> postgres: engine engine ::1(51664) idle >> postgres 6105 0.3 0.0 271532 15976 ? Ds 13:01 0:00 >> postgres: autovacuum worker process ovirt_engine_history >> postgres 6216 0.2 0.0 263864 11440 ? Ss 13:02 0:00 >> postgres: autovacuum worker process engine >> postgres 6245 0.0 0.0 262888 6212 ? Ss 13:02 0:00 >> postgres: engine engine 127.0.0.1(42400) idle >> postgres 6246 0.0 0.0 262844 3256 ? Ss 13:02 0:00 >> postgres: autovacuum worker process template1 >> postgres 18815 0.0 0.0 262912 5852 ? Ss nov01 0:00 >> postgres: django django 127.0.0.1(59564) idle >> postgres 23148 0.0 0.2 266052 43024 ? Ss oct28 9:01 >> postgres: engine engine 127.0.0.1(59714) idle >> postgres 23149 0.0 0.0 262980 6820 ? Ss oct28 0:00 >> postgres: engine engine 127.0.0.1(59716) idle >> postgres 28784 0.0 0.0 262816 3492 ? Ss 12:02 0:00 >> postgres: ovirt_engine_history ovirt_engine_history 127.0.0.1(39470) >> idle >> postgres 28785 0.0 0.0 262816 3496 ? Ss 12:02 0:00 >> postgres: ovirt_engine_history ovirt_engine_history 127.0.0.1(39472) >> idle >> postgres 28921 0.8 0.7 375152 146452 ? Ss 12:03 0:30 >> postgres: engine engine 127.0.0.1(39484) idle >> postgres 29007 3.3 0.7 369348 142184 ? Ds 12:03 1:58 >> postgres: engine engine 127.0.0.1(39498) SELECT >> postgres 29009 5.0 0.3 294736 72776 ? Ss 12:03 2:58 >> postgres: ovirt_engine_history ovirt_engine_history 127.0.0.1(39500) >> idle >> postgres 29048 0.0 0.0 263664 12176 ? Ss 12:03 0:00 >> postgres: engine engine 127.0.0.1(39530) idle >> postgres 29064 0.6 0.8 384936 157852 ? Ss 12:03 0:24 >> postgres: engine engine 127.0.0.1(39532) idle >> postgres 29065 1.2 0.7 358944 137028 ? Ss 12:03 0:43 >> postgres: engine engine 127.0.0.1(39534) idle >> postgres 29066 1.9 0.7 355800 132800 ? Ss 12:03 1:08 >> postgres: engine engine 127.0.0.1(39536) idle >> postgres 29067 1.0 0.7 370688 140504 ? Ss 12:03 0:37 >> postgres: engine engine 127.0.0.1(39538) idle >> postgres 29068 1.7 0.7 360984 139584 ? Ss 12:03 1:02 >> postgres: engine engine 127.0.0.1(39540) idle >> postgres 29069 1.3 0.7 358140 136268 ? Ss 12:03 0:48 >> postgres: engine engine 127.0.0.1(39542) idle >> postgres 29070 3.7 0.7 372064 141724 ? Ss 12:03 2:13 >> postgres: engine engine 127.0.0.1(39544) idle >> postgres 29071 0.8 0.6 337224 114132 ? Ss 12:03 0:31 >> postgres: engine engine 127.0.0.1(39546) idle >> postgres 29072 0.5 0.6 336616 114276 ? Ss 12:03 0:18 >> postgres: engine engine 127.0.0.1(39548) idle >> postgres 29073 1.7 0.7 357872 134540 ? Ss 12:03 1:02 >> postgres: engine engine 127.0.0.1(39550) idle >> postgres 29139 3.5 0.7 361244 134176 ? Ss 12:03 2:07 >> postgres: engine engine 127.0.0.1(39572) idle >> postgres 29140 3.0 0.7 367884 138372 ? Ss 12:03 1:46 >> postgres: engine engine 127.0.0.1(39570) idle >> postgres 29141 1.0 0.9 391984 169204 ? Ss 12:03 0:38 >> postgres: engine engine 127.0.0.1(39574) idle >> postgres 29142 1.3 0.7 358820 136140 ? Ss 12:03 0:48 >> postgres: engine engine 127.0.0.1(39576) idle >> postgres 29143 1.6 0.8 385000 156592 ? Ss 12:03 0:58 >> postgres: engine engine 127.0.0.1(39578) idle >> postgres 29144 3.6 0.9 403740 174552 ? Ss 12:03 2:09 >> postgres: engine engine 127.0.0.1(39580) idle >> postgres 29145 3.4 0.7 355800 128876 ? Ss 12:03 2:01 >> postgres: engine engine 127.0.0.1(39582) idle >> postgres 29146 1.8 0.8 380884 157828 ? Ss 12:03 1:06 >> postgres: engine engine 127.0.0.1(39586) idle >> postgres 29147 3.5 0.6 353228 123200 ? Ss 12:03 2:05 >> postgres: engine engine 127.0.0.1(39584) idle >> postgres 29148 0.9 0.8 383452 156268 ? Ss 12:03 0:34 >> postgres: engine engine 127.0.0.1(39588) idle >> postgres 29149 1.3 0.7 365552 139612 ? Ss 12:03 0:47 >> postgres: engine engine 127.0.0.1(39590) idle >> postgres 29150 1.2 0.7 363448 136564 ? Ss 12:03 0:43 >> postgres: engine engine 127.0.0.1(39592) SELECT >> postgres 29151 1.4 0.7 365940 139184 ? Ss 12:03 0:51 >> postgres: engine engine 127.0.0.1(39594) idle >> postgres 29152 1.2 0.7 358328 134268 ? Ss 12:03 0:44 >> postgres: engine engine 127.0.0.1(39596) idle >> postgres 29402 1.3 0.7 362044 139812 ? Ss 12:04 0:47 >> postgres: engine engine 127.0.0.1(39698) idle >> postgres 29403 2.1 0.8 377760 154556 ? Ss 12:04 1:15 >> postgres: engine engine 127.0.0.1(39700) idle >> postgres 29404 2.2 0.7 369160 144600 ? Ss 12:04 1:18 >> postgres: engine engine 127.0.0.1(39702) idle >> postgres 32230 0.1 0.5 336252 101912 ? Ss 12:19 0:04 >> postgres: engine engine 127.0.0.1(40564) idle >> postgres 32232 3.4 0.6 357644 127732 ? Ss 12:19 1:29 >> postgres: engine engine 127.0.0.1(40566) idle >> postgres 32234 0.0 0.1 270924 19836 ? Ss 12:19 0:00 >> postgres: engine engine 127.0.0.1(40568) idle >> >> Actually, I'm not really sure why is this machine so slow. In terms >> of RAM memory and CPU, it still has a bunch of free resources. >> >> Could someone help track this down and point some advices on how to >> optimize the user experience in this case? >> >> Thanks! >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/HYVADDU3XJXYK…

1 0

Cannot copy or move disks
by suporte＠logicworks.pt 17 Nov '20

17 Nov '20

Hello, I just update to Version 4.4.3.11-1.el8. Engine and host and now I cannot copy or move disks. Storage domains are glusterfs # gluster --version glusterfs 7.8 Here is what I found on vdsm.log 2020-11-14 14:08:16,917+0000 INFO (tasks/5) [storage.SANLock] Releasing Lease(name='01178644-2ad6-4d37-8657-f33f547bee6b', path='/rhev/data-center/mnt/glusterSD/node1-teste.aclou d.pt:_data2/83f8bbfd-cfa3-46d9-a823-c36054826d13/images/97977cbf-eecc-4476-a11f-7798425d40c4/01178644-2ad6-4d37-8657-f33f547bee6b.lease', offset=0) (clusterlock:530) 2020-11-14 14:08:17,015+0000 INFO (tasks/5) [storage.SANLock] Successfully released Lease(name='01178644-2ad6-4d37-8657-f33f547bee6b', path='/rhev/data-center/mnt/glusterSD/node1 -teste.acloud.pt:_data2/83f8bbfd-cfa3-46d9-a823-c36054826d13/images/97977cbf-eecc-4476-a11f-7798425d40c4/01178644-2ad6-4d37-8657-f33f547bee6b.lease', offset=0) (clusterlock:540) 2020-11-14 14:08:17,016+0000 ERROR (tasks/5) [root] Job '8cd732fc-d69b-4c32-8b35-e4a8e47396fb' failed (jobs:223) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/jobs.py", line 159, in run self._run() File "/usr/lib/python3.6/site-packages/vdsm/storage/sdm/api/copy_data.py", line 110, in _run self._operation.run() File "/usr/lib/python3.6/site-packages/vdsm/storage/qemuimg.py", line 374, in run for data in self._operation.watch(): File "/usr/lib/python3.6/site-packages/vdsm/storage/operation.py", line 106, in watch self._finalize(b"", err) File "/usr/lib/python3.6/site-packages/vdsm/storage/operation.py", line 179, in _finalize raise cmdutils.Error(self._cmd, rc, out, err) vdsm.common.cmdutils.Error: Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'raw', '-O', 'raw', '/rhev/data-center/mnt/glusterSD/node1-teste.aclou d.pt:_data2/83f8bbfd-cfa3-46d9-a823-c36054826d13/images/789f6e50-b954-4dda-a6d5-077fdfb357d2/d95a3e83-74d2-40a6-9f8f-e6ae68794051', '/rhev/data-center/mnt/glusterSD/node1-teste.ac loud.pt:_data2/83f8bbfd-cfa3-46d9-a823-c36054826d13/images/97977cbf-eecc-4476-a11f-7798425d40c4/01178644-2ad6-4d37-8657-f33f547bee6b'] failed with rc=1 out=b'' err=bytearray(b'qem u-img: error while reading sector 260177858: No such file or directory\n') 2020-11-14 14:08:17,017+0000 INFO (tasks/5) [root] Job '8cd732fc-d69b-4c32-8b35-e4a8e47396fb' will be deleted in 3600 seconds (jobs:251) 2020-11-14 14:08:17,017+0000 INFO (tasks/5) [storage.ThreadPool.WorkerThread] FINISH task 6cb1d496-d1ca-40b5-a488-a72982738bab (threadPool:151) 2020-11-14 14:08:17,316+0000 INFO (jsonrpc/2) [api.host] START getJobs(job_type='storage', job_ids=['8cd732fc-d69b-4c32-8b35-e4a8e47396fb']) from=::ffff:192.168.5.165,36616, flow _id=49320e0a-14fb-4cbb-bdfd-b2546c260bf7 (api:48) -- Jose Ferradeira http://www.logicworks.pt

5 15

Re: VM with illegal snapshots
by Florian Schmid 17 Nov '20

17 Nov '20

Hi, I have also sometimes the issue with snapshots or disk move, which is also related to snapshots, when the engine process is running for a longer time. After restarting the engine service, then it is working again for several weeks, until it gets too long and issues starting again to happen. I had never the time to dig in deeper here and I'm never on a version, which is still supported, but it would be nice to here, if you maybe have the same issue? How long was your engine process running, until the issues have started? BR Florian Von: "Magnus Isaksson" <magnus(a)vmar.se> An: "Alex K" <rightkicktech(a)gmail.com>, "Giorgio Biacchi" <giorgio(a)di.unimi.it> CC: "users" <users(a)ovirt.org> Gesendet: Dienstag, 17. November 2020 10:37:24 Betreff: [ovirt-users] Re: VM with illegal snapshots Hello We have the same issue, and not just one VM, we have about 10-15 VMs that have either snapshots that are illegal or snapshots that is not possible to remove. This have been an issue for quite some time, all since beginning of 4.3 we get "vm with illegal snapshots" almost every week, and most often we can remove the snapshot and all is ok, but now this have escalated quite much and leaves us with customer VM that we may not be able to reboot or that the disk gets corrupted, that have happed a few times. This is the VM with most snapshots that we are unable to remove any of them. Engine is on 4.3.10 and hosts on 4.3.9 How can i safely remove these snapshots? (I am not super comfortable around database "hacking" so some informative description would be much appreciated.) And how can we eliminate that these things happen? Cheers Magnus From: Alex K <rightkicktech(a)gmail.com> Sent: 10 November 2020 05:05 To: Giorgio Biacchi <giorgio(a)di.unimi.it> Cc: users <users(a)ovirt.org> Subject: [ovirt-users] Re: VM with illegal snapshots On Fri, Oct 9, 2020, 12:59 Giorgio Biacchi < [ mailto:giorgio@di.unimi.it | giorgio(a)di.unimi.it ] > wrote: Hi, due to a bug in our Ovirt integrated backup system now we have some VMs with snapshots in illegal state. It seems that there's an inconsistency between the db and the real status of images on disk. Let me show an example: engine=# select image_guid,parentid,imagestatus,vm_snapshot_id,volume_type,volume_format,active from images where image_group_id='e34f77cb-54d5-40d0-b539-e0a5fd512d2d'; image_guid | parentid | imagestatus | vm_snapshot_id | volume_type | volume_format | active --------------------------------------+--------------------------------------+-------------+--------------------------------------+-------------+---------------+-------- a107b6c4-842e-4b40-9215-c965431a0c0f | 00000000-0000-0000-0000-000000000000 | 4 | d19d6ca3-1989-4c67-8ee7-c0c43b3e6d74 | 2 | 4 | f a4c86a68-9123-454c-b417-1b15038a4bf2 | a107b6c4-842e-4b40-9215-c965431a0c0f | 1 | e7a405ee-8fd4-4733-ae9c-5252bf07c9d3 | 2 | 4 | f f6a61f2e-26bd-4b63-97c6-d66913ce48c5 | a4c86a68-9123-454c-b417-1b15038a4bf2 | 1 | 9d0958b9-4995-4e11-a027-a32d4bac52e4 | 2 | 4 | t (3 rows) [root@host02 ~]# lvs -o+lv_tags |grep e34f77cb-54d5-40d0-b539-e0a5fd512d2d a107b6c4-842e-4b40-9215-c965431a0c0f 459011cf-ebb6-46ff-831d-8ccfafd82c8a -wi------- 149.50g IU_e34f77cb-54d5-40d0-b539-e0a5fd512d2d,MD_68,PU_00000000-0000-0000-0000-000000000000 f6a61f2e-26bd-4b63-97c6-d66913ce48c5 459011cf-ebb6-46ff-831d-8ccfafd82c8a -wi------- 10.00g IU_e34f77cb-54d5-40d0-b539-e0a5fd512d2d,MD_348,PU_a107b6c4-842e-4b40-9215-c965431a0c0f so image guid a4c86a68-9123-454c-b417-1b15038a4bf2 is not present on disk, i think that the image was correctly merged but not removed from the database. Any suggestion on how to fix the database to reflect the real situation on disk?? In those cases I delete the entry from engine DB to reflect the status of the image chain. BQ_BEGIN TIA -- gb PGP Key: [ http://pgp.mit.edu/ | http://pgp.mit.edu/ ] Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34 _______________________________________________ Users mailing list -- [ mailto:users@ovirt.org | users(a)ovirt.org ] To unsubscribe send an email to [ mailto:users-leave@ovirt.org | users-leave(a)ovirt.org ] Privacy Statement: [ https://www.ovirt.org/privacy-policy.html | https://www.ovirt.org/privacy-policy.html ] oVirt Code of Conduct: [ https://www.ovirt.org/community/about/community-guidelines/ | https://www.ovirt.org/community/about/community-guidelines/ ] List Archives: [ https://lists.ovirt.org/archives/list/users@ovirt.org/message/OF4NTAC6BPGRP… | https://lists.ovirt.org/archives/list/users@ovirt.org/message/OF4NTAC6BPGRP… ] BQ_END _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FRAXF7POUODBM…

1 0

VM with illegal snapshots
by Giorgio Biacchi 17 Nov '20

17 Nov '20

Hi, due to a bug in our Ovirt integrated backup system now we have some VMs with snapshots in illegal state. It seems that there's an inconsistency between the db and the real status of images on disk. Let me show an example: engine=# select image_guid,parentid,imagestatus,vm_snapshot_id,volume_type,volume_format,active from images where image_group_id='e34f77cb-54d5-40d0-b539-e0a5fd512d2d'; image_guid | parentid | imagestatus | vm_snapshot_id | volume_type | volume_format | active --------------------------------------+--------------------------------------+-------------+--------------------------------------+-------------+---------------+-------- a107b6c4-842e-4b40-9215-c965431a0c0f | 00000000-0000-0000-0000-000000000000 | 4 | d19d6ca3-1989-4c67-8ee7-c0c43b3e6d74 | 2 | 4 | f a4c86a68-9123-454c-b417-1b15038a4bf2 | a107b6c4-842e-4b40-9215-c965431a0c0f | 1 | e7a405ee-8fd4-4733-ae9c-5252bf07c9d3 | 2 | 4 | f f6a61f2e-26bd-4b63-97c6-d66913ce48c5 | a4c86a68-9123-454c-b417-1b15038a4bf2 | 1 | 9d0958b9-4995-4e11-a027-a32d4bac52e4 | 2 | 4 | t (3 rows) [root@host02 ~]# lvs -o+lv_tags |grep e34f77cb-54d5-40d0-b539-e0a5fd512d2d a107b6c4-842e-4b40-9215-c965431a0c0f 459011cf-ebb6-46ff-831d-8ccfafd82c8a -wi------- 149.50g IU_e34f77cb-54d5-40d0-b539-e0a5fd512d2d,MD_68,PU_00000000-0000-0000-0000-000000000000 f6a61f2e-26bd-4b63-97c6-d66913ce48c5 459011cf-ebb6-46ff-831d-8ccfafd82c8a -wi------- 10.00g IU_e34f77cb-54d5-40d0-b539-e0a5fd512d2d,MD_348,PU_a107b6c4-842e-4b40-9215-c965431a0c0f so image guid a4c86a68-9123-454c-b417-1b15038a4bf2 is not present on disk, i think that the image was correctly merged but not removed from the database. Any suggestion on how to fix the database to reflect the real situation on disk?? TIA -- gb PGP Key: http://pgp.mit.edu/ Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34

3 3

Really slow manager node
by Nicolás 17 Nov '20

17 Nov '20

Hi, We're running oVirt 4.3.8 and even if this is a problem we've had since a lot of time (I would say since 4.0.x), I decided to look for help in case anything can be done. Our environment is heavily used by users in our University (about 3000 users), and currently our oVirt infrastructure has 1928 virtual machines, being 882 of them currently running. We have a separate physical machine for the manager node, and the problem is that this machine is very, very, very slow, despite it has (from my point of view) enough physical resources to run efficiently. By slow I mean even the SSH access to it takes about 10 seconds, not just the admin/user portals. Any operation takes enough time to make the experience not comfortable to our users (enter the VM portal, start a VM, open a console...). Node machine's parameters are: 18GB of RAM memory 1 processor with 12CPUs 300GB SCSI Disk, local storage. No Storage Domain is stored in this node machine. Currently, most consuming processes are: 28802 ovirt 20 0 3302876 1,5g 25988 S 1,0 8,7 22:46.36 ovirt-engine -server -XX:+TieredCompilation -Xms1024M -Xmx1024M -Xss1M -Djava.aw+ 28701 ovirt 20 0 5465432 807704 13140 S 5,9 4,4 3:15.53 ovirt-engine-dwhd -Dorg.ovirt.engine.dwh.settings=/tmp/tmp8wtnTA/settings.proper+ # free -m total used free shared buff/cache available Mem: 17886 6669 2734 255 8482 10625 Swap: 6143 1002 5141 There are also a lot of postgresql processes: postgres 2186 0.0 0.0 261812 4136 ? Ss jun05 37:39 /opt/rh/rh-postgresql10/root/usr/bin/postmaster -D /var/opt/rh/rh-postgresql10/lib/pgsql/data postgres 3176 0.0 0.0 216084 656 ? Ss jun05 0:00 postgres: logger process postgres 3290 0.0 0.2 262204 37476 ? Ss jun05 77:31 postgres: checkpointer process postgres 3291 0.3 0.2 262052 36960 ? Ss jun05 754:02 postgres: writer process postgres 3292 0.0 0.0 261812 1988 ? Ss jun05 100:51 postgres: wal writer process postgres 3293 0.0 0.2 262380 36748 ? Ss jun05 21:58 postgres: autovacuum launcher process postgres 3294 0.1 0.0 219216 1412 ? Ds jun05 335:41 postgres: stats collector process postgres 3295 0.0 0.0 262220 1460 ? Ss jun05 0:11 postgres: bgworker: logical replication launcher postgres 3393 0.0 0.2 265792 40452 ? Ss jun05 15:36 postgres: engine engine ::1(51664) idle postgres 6105 0.3 0.0 271532 15976 ? Ds 13:01 0:00 postgres: autovacuum worker process ovirt_engine_history postgres 6216 0.2 0.0 263864 11440 ? Ss 13:02 0:00 postgres: autovacuum worker process engine postgres 6245 0.0 0.0 262888 6212 ? Ss 13:02 0:00 postgres: engine engine 127.0.0.1(42400) idle postgres 6246 0.0 0.0 262844 3256 ? Ss 13:02 0:00 postgres: autovacuum worker process template1 postgres 18815 0.0 0.0 262912 5852 ? Ss nov01 0:00 postgres: django django 127.0.0.1(59564) idle postgres 23148 0.0 0.2 266052 43024 ? Ss oct28 9:01 postgres: engine engine 127.0.0.1(59714) idle postgres 23149 0.0 0.0 262980 6820 ? Ss oct28 0:00 postgres: engine engine 127.0.0.1(59716) idle postgres 28784 0.0 0.0 262816 3492 ? Ss 12:02 0:00 postgres: ovirt_engine_history ovirt_engine_history 127.0.0.1(39470) idle postgres 28785 0.0 0.0 262816 3496 ? Ss 12:02 0:00 postgres: ovirt_engine_history ovirt_engine_history 127.0.0.1(39472) idle postgres 28921 0.8 0.7 375152 146452 ? Ss 12:03 0:30 postgres: engine engine 127.0.0.1(39484) idle postgres 29007 3.3 0.7 369348 142184 ? Ds 12:03 1:58 postgres: engine engine 127.0.0.1(39498) SELECT postgres 29009 5.0 0.3 294736 72776 ? Ss 12:03 2:58 postgres: ovirt_engine_history ovirt_engine_history 127.0.0.1(39500) idle postgres 29048 0.0 0.0 263664 12176 ? Ss 12:03 0:00 postgres: engine engine 127.0.0.1(39530) idle postgres 29064 0.6 0.8 384936 157852 ? Ss 12:03 0:24 postgres: engine engine 127.0.0.1(39532) idle postgres 29065 1.2 0.7 358944 137028 ? Ss 12:03 0:43 postgres: engine engine 127.0.0.1(39534) idle postgres 29066 1.9 0.7 355800 132800 ? Ss 12:03 1:08 postgres: engine engine 127.0.0.1(39536) idle postgres 29067 1.0 0.7 370688 140504 ? Ss 12:03 0:37 postgres: engine engine 127.0.0.1(39538) idle postgres 29068 1.7 0.7 360984 139584 ? Ss 12:03 1:02 postgres: engine engine 127.0.0.1(39540) idle postgres 29069 1.3 0.7 358140 136268 ? Ss 12:03 0:48 postgres: engine engine 127.0.0.1(39542) idle postgres 29070 3.7 0.7 372064 141724 ? Ss 12:03 2:13 postgres: engine engine 127.0.0.1(39544) idle postgres 29071 0.8 0.6 337224 114132 ? Ss 12:03 0:31 postgres: engine engine 127.0.0.1(39546) idle postgres 29072 0.5 0.6 336616 114276 ? Ss 12:03 0:18 postgres: engine engine 127.0.0.1(39548) idle postgres 29073 1.7 0.7 357872 134540 ? Ss 12:03 1:02 postgres: engine engine 127.0.0.1(39550) idle postgres 29139 3.5 0.7 361244 134176 ? Ss 12:03 2:07 postgres: engine engine 127.0.0.1(39572) idle postgres 29140 3.0 0.7 367884 138372 ? Ss 12:03 1:46 postgres: engine engine 127.0.0.1(39570) idle postgres 29141 1.0 0.9 391984 169204 ? Ss 12:03 0:38 postgres: engine engine 127.0.0.1(39574) idle postgres 29142 1.3 0.7 358820 136140 ? Ss 12:03 0:48 postgres: engine engine 127.0.0.1(39576) idle postgres 29143 1.6 0.8 385000 156592 ? Ss 12:03 0:58 postgres: engine engine 127.0.0.1(39578) idle postgres 29144 3.6 0.9 403740 174552 ? Ss 12:03 2:09 postgres: engine engine 127.0.0.1(39580) idle postgres 29145 3.4 0.7 355800 128876 ? Ss 12:03 2:01 postgres: engine engine 127.0.0.1(39582) idle postgres 29146 1.8 0.8 380884 157828 ? Ss 12:03 1:06 postgres: engine engine 127.0.0.1(39586) idle postgres 29147 3.5 0.6 353228 123200 ? Ss 12:03 2:05 postgres: engine engine 127.0.0.1(39584) idle postgres 29148 0.9 0.8 383452 156268 ? Ss 12:03 0:34 postgres: engine engine 127.0.0.1(39588) idle postgres 29149 1.3 0.7 365552 139612 ? Ss 12:03 0:47 postgres: engine engine 127.0.0.1(39590) idle postgres 29150 1.2 0.7 363448 136564 ? Ss 12:03 0:43 postgres: engine engine 127.0.0.1(39592) SELECT postgres 29151 1.4 0.7 365940 139184 ? Ss 12:03 0:51 postgres: engine engine 127.0.0.1(39594) idle postgres 29152 1.2 0.7 358328 134268 ? Ss 12:03 0:44 postgres: engine engine 127.0.0.1(39596) idle postgres 29402 1.3 0.7 362044 139812 ? Ss 12:04 0:47 postgres: engine engine 127.0.0.1(39698) idle postgres 29403 2.1 0.8 377760 154556 ? Ss 12:04 1:15 postgres: engine engine 127.0.0.1(39700) idle postgres 29404 2.2 0.7 369160 144600 ? Ss 12:04 1:18 postgres: engine engine 127.0.0.1(39702) idle postgres 32230 0.1 0.5 336252 101912 ? Ss 12:19 0:04 postgres: engine engine 127.0.0.1(40564) idle postgres 32232 3.4 0.6 357644 127732 ? Ss 12:19 1:29 postgres: engine engine 127.0.0.1(40566) idle postgres 32234 0.0 0.1 270924 19836 ? Ss 12:19 0:00 postgres: engine engine 127.0.0.1(40568) idle Actually, I'm not really sure why is this machine so slow. In terms of RAM memory and CPU, it still has a bunch of free resources. Could someone help track this down and point some advices on how to optimize the user experience in this case? Thanks!

2 1

easy way to migrate to new engine
by jb 17 Nov '20

17 Nov '20

Hello everybody! At the moment I have here a standalone engine and two nodes. Storage type is NFS. Now I want to setup a 3 node self hosted cluster with Glusterfs and import my VMs from the old engine. I know, there is a guide for migration from standalone to self-hosted engine, but there is so many changes (new Subnet/DNS names, different type of storage, new CPU type) that I would like to skip this migration guide. Is there a different way to migrate my VMs? Mounting my old storage and moving the disks to the Gluster would be nice, but I guess I can not just mount a storage with existing VM images. Best regards Jonathan

3 2

Re: Problem with Cluster-wise BIOS Settings in oVirt 4.4
by Vladislav S 17 Nov '20

17 Nov '20

PLEASE HELP I changed the type in the cluster and now my hosted-engine machine won't start!. There are no backups. How can I manually change the parameters of the machine from under the roof so that it starts and I can restore ovirt to work Error in logs: XML error: The device at PCI address 0000:00:02.0 cannot be plugged into the PCI controller with index='0'. It requires a controller that accepts a pcie-root-port

2 1

Root Password Reset
by ilirdaka＠live.com 16 Nov '20

16 Nov '20

Hello! I'm new to oVirt, one of my customers has a 2 node (cluster) of oVirt but has no password access to it! Is there any way to reset that password? Best regards, Ilir

3 4

Async release for oVirt 4.4.3
by Sandro Bonazzola 16 Nov '20

16 Nov '20

On November 16th the oVirt project released an async update to the following packages: - ovirt-ansible-collection-1.2.2-1 - ovirt-engine-4.4.3.12 - ovirt-engine-sdk 4.4.7 Fixing the following bugs: - [BZ 1884599 <https://bugzilla.redhat.com/1884599>] - Hosted-engine deploy is failing with error "Unable to access credentials /etc/pki/vdsm/libvirt-vnc/ca-cert.pem" - [BZ 1894111 <https://bugzilla.redhat.com/1894111>] - After host upgrade from 4.4.2 to 4.4.3 there are still packages left to upgrade - [BZ 1894758 <https://bugzilla.redhat.com/1894758>] - [DR] Remote data sync to the secondary site never completes - Support enum URL parameters in Python SDK -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV 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 0

Migrate old storage domains to new oVirt
by Joris Dobbelsteen 16 Nov '20

16 Nov '20

Hi All, I still have a single-node (all-in-one) oVirt 3.5 setup that has worked great and uses a local storage domain. I’m migrating to oVirt 4.4 hosted setup as I need to replace disks. However, since this is a single node setup, making the migration a bit tricker than usual. My plan is to move the physical disks over, mount the old local storage domains and use them in oVirt 4.4. E.g. to move the images. Is this still possible with old domains? Or is there something special that should be taken care of? Since the original domains are local is this something to take care of? E.g. can hosted engine setup be running on a “local” datacentre? Best regards, Joris Dobbelsteen

1 0

oVirt Node Crash
by Anton Louw 15 Nov '20

15 Nov '20

Hi Everybody, I have built a new host which has been running fine for the last couple of days. I noticed today that the host crashed, but it is not giving me a reason as to why. It happened at 13:45 today, but I have given time before that on the logs as well. Is there something I am missing here? Thanks Anton Louw Cloud Engineer: Storage and Virtualization ______________________________________ D: 087 805 1572 | M: N/A A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg anton.louw(a)voxtelecom.co.za www.vox.co.za

2 3

Backporting of Fixes
by Gillingham, Eric J (US 393D) 15 Nov '20

15 Nov '20

I'm still running on oVirt 4.3 due to some hardware that will require some extra effort to move to 4.4 we're not quite ready to do yet, and am currently hitting what I believe to be https://bugzilla.redhat.com/show_bug.cgi?id=1820998 which is fixed in 4.4. I'm wondering if there's a process to request a backport, or should I just open a new bug against 4.3? Thank You - Eric

2 1

oVirt 4.4 vnic profile to substitute vdsm mac spoof hook
by Gianluca Cecchi 15 Nov '20

15 Nov '20

Hello, I have an Openstack Queens environment that is composed by VMs inside oVirt. Initially this oVirt environment was on 4.3 and on director I had to set vdsm mac spoof to be able to give dhcp address to the overcloud nodes. I tried something at that time with vnic profiles but I was not able to have it work as expected, so I used the hook. Now I have migrated this same environment to 4.4.2 and I see that vdsm mac spoof is no more an option: https://bugzilla.redhat.com/show_bug.cgi?id=1703840 I tried some combinations of vnic profiles on director vnic but it seems not to work as a dhcpserver as before. I see DHCPDISCOVER from overcloud node in director messages (while before I saw DHCPREQUEST), I see the DHCPOFFER from director, but I don't see the DHCPACK from the overcloud node... On director I have the br-ctlplane vswitch using its interface eth1: ovs-vsctl show . . . Bridge br-ctlplane Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port br-ctlplane Interface br-ctlplane type: internal Port "eth1" Interface "eth1" Port phy-br-ctlplane Interface phy-br-ctlplane type: patch options: {peer=int-br-ctlplane} ovs_version: "2.11.0" [root@director ~]# ovs-ofctl show br-ctlplane OFPT_FEATURES_REPLY (xid=0x2): dpid:0000566f3d480014 n_tables:254, n_buffers:0 capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst 1(eth1): addr:56:6f:3d:48:00:13 config: 0 state: 0 speed: 0 Mbps now, 0 Mbps max 2(phy-br-ctlplane): addr:76:76:8b:08:d4:2f config: 0 state: 0 speed: 0 Mbps now, 0 Mbps max LOCAL(br-ctlplane): addr:56:6f:3d:48:00:14 config: 0 state: 0 speed: 0 Mbps now, 0 Mbps max OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0 [root@director ~]# [root@director ~]# ip addr show dev br-ctlplane 6: br-ctlplane: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 56:6f:3d:48:00:14 brd ff:ff:ff:ff:ff:ff inet 172.23.0.220/24 brd 172.23.0.255 scope global br-ctlplane valid_lft forever preferred_lft forever inet 172.23.0.222/32 scope global br-ctlplane valid_lft forever preferred_lft forever inet 172.23.0.221/32 scope global br-ctlplane valid_lft forever preferred_lft forever inet6 fe80::546f:3dff:fe48:14/64 scope link valid_lft forever preferred_lft forever [root@director ~]# The eth1 interface is configured in oVirt on vlan23. The overcloud nodes have one vnic on vlan 23. I have two dnsmasq processes on director, for ironic and for overcloud nodes: nobody 1527 1 0 Nov14 ? 00:00:00 /sbin/dnsmasq --conf-file=/etc/ironic-inspector/dnsmasq.conf nobody 3288 1 0 Nov14 ? 00:00:00 dnsmasq --no-hosts --no-resolv --pid-file=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/pid --dhcp-hostsfile=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/host --addn-hosts=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/addn_hosts --dhcp-optsfile=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/opts --dhcp-leasefile=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/leases --dhcp-match=set:ipxe,175 --local-service --bind-dynamic --dhcp-range=set:subnet-d48e002b-f269-4ed5-a96e-9aeba0b119b9,172.23.0.0,static,255.255.255.0,86400s --dhcp-option-force=option:mtu,1500 --dhcp-lease-max=256 --conf-file=/etc/dnsmasq-ironic.conf --domain=localdomain In messages of director when booting the overcloud node: Nov 15 00:42:45 director dnsmasq-dhcp[3288]: DHCPDISCOVER(tap9fdd5920-62) 172.23.0.232 56:6f:3d:48:00:3c Nov 15 00:42:45 director dnsmasq-dhcp[1527]: 3792136019 DHCPDISCOVER(br-ctlplane) 56:6f:3d:48:00:3c ignored Nov 15 00:42:45 director dnsmasq-dhcp[3288]: DHCPOFFER(tap9fdd5920-62) 172.23.0.232 56:6f:3d:48:00:3c Nov 15 00:42:45 director dnsmasq-dhcp[3288]: DHCPOFFER(tap9fdd5920-62) 172.23.0.232 56:6f:3d:48:00:3c In oVirt 4.3 with the same setup and VDSM MAC spoof hook configured I saw this inside messages of director when booting the overcloud nodes: Oct 18 04:50:05 director dnsmasq-dhcp[3230]: DHCPREQUEST(tap9fdd5920-62) 172.23.0.232 56:6f:3d:48:00:3c Oct 18 04:50:05 director dnsmasq-dhcp[3230]: DHCPACK(tap9fdd5920-62) 172.23.0.232 56:6f:3d:48:00:3c host-172-23-0-232 Questions: what is the filter to give to have it work? is it dynamic the effect at runtime for a running VM to edit its vnic and change its profile? is it dynamic for running VMs that for a vNIC with a certain profile if I go in Networks --> vNIC Profiles --> Edit vNIC Profile and change its network filter value? Thanks for any insight. Gianluca

1 2

Failed to add new host to oVirt 4.4.3.11-1.el8
by Winfried de Heiden 14 Nov '20

14 Nov '20

Hi all, Adding a brand new installed oVirt node to oVirt 4.4.3.11-1.el8 fails; engine.log will tell: 2020-11-13 10:05:40,777+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-5) [80e3f255-f8b9-4d5f-9be2-ebb59fec28db] EVENT_ID: VDS_ANSIBLE_INSTALL_STARTED(560), Ansible host-deploy playbook execution has started on host Bigvirt. 2020-11-13 10:05:40,784+01 ERROR [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-engine-Thread-5) [80e3f255-f8b9-4d5f-9be2-ebb59fec28db] Exception: Failed to read the runner-service response. Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') at [Source: org.apache.http.conn.EofSensorInputStream@6cc9953a; line: 1, column: 2] 2020-11-13 10:05:40,785+01 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-5) [80e3f255-f8b9-4d5f-9be2-ebb59fec28db] Host installation failed for host 'df87842f-0852-4a3a-898b-2b724b068199', 'Bigvirt': Failed to execute Ansible host-deploy role: Failed to read the runner-service response. Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') Anyone got a clue? Winfried

3 2

Re: Network profile filtering
by Dominik Holler 13 Nov '20

13 Nov '20

On Fri, Nov 13, 2020 at 4:19 PM Pascal DeMilly <Pascal(a)butterflyit.com> wrote: > Thank you > > That is exactly what I was looking for. Any chance it could be back > ported to 4.3. Maybe list the rules and I could use rest API to add it to > my court install > On ovirt-4.3 there is only *Bug 1009608* <https://bugzilla.redhat.com/show_bug.cgi?id=1009608> - [RFE] Limit east-west traffic of VMs with network filter The isolated ports cannot be backported to oVirt 4.3, because the isolated ports require a new feature from CentOS 8 kernel and CentOS 8.3 libvirt. > > I'm not eager to move yet to 4.4 since I'm reading on this list lot of > people have issue migrating and I have 20 hosts running currently > > Are you aware that you could upgrade oVirt Engine and go on with the oVirt 4.3 hosts? This way you could have some new CentOS 8 based oVirt-4.4 hosts which use the new features, and leave the other hosts on CentOS 7 based oVirt 4.3 . > > > Get Outlook for Android <https://aka.ms/ghei36> > > ------------------------------ > *From:* Dominik Holler <dholler(a)redhat.com> > *Sent:* Friday, November 13, 2020 6:21:56 AM > *To:* Pascal DeMilly <Pascal(a)butterflyit.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Network profile filtering > > > > On Fri, Nov 13, 2020 at 5:13 AM <pascal(a)butterflyit.com> wrote: > > I am using ovirt 4.3. I am in need to isolate all my VM from each other > (without using VLAN) except to a virtual gateway which is also the DHCP > server. > > Basically only allowing traffic from 1 MAC address to another MAC address. > Everything else should be filter out by ovirt filtering subsystem > > How will I go about that? I can see in network profile the ability to set > different filter but can't find a way to create new filter. > > > Does the Doc Text of > *Bug 1009608* <https://bugzilla.redhat.com/show_bug.cgi?id=1009608> - [RFE] > Limit east-west traffic of VMs with network filter > https://bugzilla.redhat.com/show_bug.cgi?id=1009608 > explain the configuration of the filter? > > Please note that there will be isolated ports > > https://www.ovirt.org/develop/release-management/features/network/isolated-… > available in ovirt-4.4.3 on CentOS 8.3 , which might address your scenario > even better. > > > > Thanks for your help > > Pascal > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/QIYX2SA7TBEFG… > >

2 1

Fail to upgrade cluster from 4.3 to 4.4
by Gianluca Cecchi 13 Nov '20

13 Nov '20

Hello, my environment was oVirt 4.3.10 with an external engine and 3 hosts. I have updated to 4.4.3 the whole infra, but know if I go and update the cluster to 4.4 I get the message in this window: https://drive.google.com/file/d/1hfs4FC8uZ-EjiCzQyitA3945U0Knnz2m/view?usp=… What is the reason for it? My Cluster is with Cluster CPU Type: "Intel Westmere IBRS SSBD Family" The signalled 'hostmaster' VM is a powered off VM used in the past to test nested virtualization and in "Virtual Machines" page aside it I see an exclamation mark with "The VM CPU doesn't match the Cluster Cpu Type" The VM is set as custom, optimized for Server Custom Chipset/Firmware Type "Cluster default (i440FX Chipset with BIOS)" Custom Emulated Machine (in grey): "Cluster default(pc-i440fx-rhel7.6.0)" Custom CPU (in grey): "Cluster default(Intel Westmere IBRS SSBD Family)" What I'm expected to change? Thanks, Gianluca

1 1

Terraform provider build
by Muhsin Tawafig 13 Nov '20

13 Nov '20

Hi Trying to test terraform ovirt provider keep getting failure on pulling modules ( on centos 7 & 8 ) #make ==> Checking that code complies with gofmt requirements... go install go: github.com/hashicorp/go-getter@v1.4.2-0.20200106182914-9813cbd4eb02: Get "https://proxy.golang.org/github.com/hashicorp/go-getter/@v/v1.4.2-0.2020010…": net/http: TLS handshake timeout make: *** [build] Error 1 Any help is appretiated

2 1

Network profile filtering
by pascal＠butterflyit.com 13 Nov '20

13 Nov '20

I am using ovirt 4.3. I am in need to isolate all my VM from each other (without using VLAN) except to a virtual gateway which is also the DHCP server. Basically only allowing traffic from 1 MAC address to another MAC address. Everything else should be filter out by ovirt filtering subsystem How will I go about that? I can see in network profile the ability to set different filter but can't find a way to create new filter. Thanks for your help Pascal

3 2

ovirt glusterfs
by garcialiang.anne＠gmail.com 13 Nov '20

13 Nov '20

Hello, I try use Gluster deploymont. I've the message error: failed: [llrovirttest02.in2p3.fr] (item={u'path': u'/gluster_bricks/engine', u'vgname': u'gluster_vg_sdb', u'lvname': u'gluster_lv_engine'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_engine", "path": "/gluster_bricks/engine", "vgname": "gluster_vg_sdb"}, "msg": "SELinux is disabled on this host."} Could you help me ? Thanks, Anne Garcia

2 1

Unable to attach VLAN-based logical networks to a bond oVirt 4.4
by simon＠justconnect.ie 13 Nov '20

13 Nov '20

When attempting to add a VLAN to a bonded interface (Broadcom NICs) in oVirt Management portal the process fails as per: https://bugzilla.redhat.com/show_bug.cgi?id=1860479 This issue has rendered mu upgrade to 4.4 useless. Does anyone have a patched kernel to resolve this please? Regards Shimme

2 1

Ballooning disabled when creating a VmPool
by Nicolás 13 Nov '20

13 Nov '20

Hi, We're using oVirt 4.3.8 along with ovirt-engine-sdk-python (4.4.1) to handle our pools. Pools are based on a template which has ballooning enabled. However, when deploying a VmPool based on that template, has the "Ballooning enabled" field disabled, uneditable and an icon which states: "The field is not attached to any instance type" (screenshot attached). We're handling a big number of VMs based on pools (> 1500), and we think this should be enabled. However, I don't see a field in the types.VmPool definition that allows that. Is that even doable? Our Python code is similar to this: newpool = types.VmPool(name='test', cluster=cl, template=t, max_user_vms=1, size=1, type=types.VmPoolType.MANUAL) vmpool_serv.add(newpool) * cl is a types.Cluster instance with ballooning_enabled=True * t is a types.Template instance with Ballooning enabled. Thanks. Nico

2 4

Old and new hardware mix
by nick＠creativitysoftware.net 12 Nov '20

12 Nov '20

Hi All, I've just joined the mailing list as my organisation needs a new virtualisation solution. VMware is prohibitively expensive for a small company like ours and of all the opensource solutions, oVirt looks like the best fit for our needs. Our existing virtual infrastructure is primarily made up of an old vSphere 5 cluster (expired license on old and out of warranty hardware) and a couple of newer standalone (free) ESXi servers. Both the cluster and the standalones have shared NFS storage so I can move VMs around. I want to take a couple of older (2014ish) servers which will serve as the management host and one compute node initially. Then, I'd like to migrate VMs from one vSphere host at a time to the newly created oVirt cluster and convert the now empty vSphere ESXi hosts into oVirt compute nodes as I go. Firstly - Would new compute host hardware (2020) work in a (2014) based ovirt cluster? If so Would I be able to take advantage of the more advanced features of ovirt like live migration etc.. with a mix of new and old hardware Thanks

3 5

Re: sshd_config AuthorizedKeysFile
by Strahil Nikolov 12 Nov '20

12 Nov '20

What happens when you change the default, but also add a "Match" directive overriding that option for the engine ? Best Regards, Strahil Nikolov В четвъртък, 12 ноември 2020 г., 10:01:12 Гринуич+2, Angus Clarke <angus(a)charworth.com> написа: Hello Sharing for anyone who needs it, this was carried out on OL7, they use ovirt 4.3 In short: both the hosted-engine deployment routine and the host add to cluster routine distribute public ssh keys to /root/.ssh/authorized_keys regardless of the AuthorizedKeysFile setting in /etc/ssh/sshd_config. Both routines fail if AuthorizedKeysfile is not default. The hosted-engine setup assumes AuthorizedKeysFile to be default (~/.ssh/authorized_keys) and creates a public key there, instead of following the sshd_config directive. The setup fails on the back of this. Once I commented this out of sshd_config file (assumes default) and restarted sshd on the KVM host that was running the hosted-engine deployment, the hosted-engine setup completed successfully. Similarly, I could not deploy a second KVM host to the compute cluster until I had altered this setting on that 2nd KVM host - presumably that process has some similar routine that unwittingly writes keys to ~/.ssh/authorized_keys.HTH Angus _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UMJ4Y622RALUU…

1 0

rhv 4.3.11 but not ovirt 4.3.11
by Gianluca Cecchi 12 Nov '20

12 Nov '20

Hello, I see that a 4.3.11 version is available for downstream RHV but not for upstream oVirt. Will it be released for oVirt too? Are there only security fixes inside or also bug fixes (like the few lines one related to export as OVA)? Thanks, Gianluca

3 3

oVrit 4.3.10 on CentOS 7.9
by Christoph Timm 12 Nov '20

12 Nov '20

Hi list, I want to update my oVirt installation to 4.3.10 on the weekend to get ready to move to 4.4 by end of December. Would it be OK to update to oVirt 4.3.10 on CentOS 7.9 which was release today? Best regards Christoph

1 0

Engine update error from 4.4.2 to 4.4.3
by Gianluca Cecchi 12 Nov '20

12 Nov '20

Hello, is this still the correct command during updates through minor releases in 4.4.x? yum update ovirt\*setup\* Because my standalone external engine is now at level ovirt-engine-4.4.2.6-1.el8.noarch with [root@ovmgr1 ~]# yum repolist repo id repo name AppStream CentOS-8 - AppStream BaseOS CentOS-8 - Base PowerTools CentOS-8 - PowerTools extras CentOS-8 - Extras ovirt-4.4 Latest oVirt 4.4 Release ovirt-4.4-advanced-virtualization Advanced Virtualization packages for x86_64 ovirt-4.4-centos-gluster7 CentOS-8 - Gluster 7 ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd ovirt-4.4-centos-ovirt44 CentOS-8 - oVirt 4.4 ovirt-4.4-copr:copr.fedorainfracloud.org:mdbarroso:ovsdbapp Copr repo for ovsdbapp owned by mdbarroso ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.22 Copr repo for NetworkManager-1.22 owned by networkmanager ovirt-4.4-copr:copr.fedorainfracloud.org:nmstate:nmstate-0.2 Copr repo for nmstate-stable owned by nmstate ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo for gluster-ansible owned by sac ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr repo for EL8_collection owned by sbonazzo ovirt-4.4-epel Extra Packages for Enterprise Linux 8 - x86_64 ovirt-4.4-virtio-win-latest virtio-win builds roughly matching what will be shipped in upcoming RHEL [root@ovmgr1 ~]# yum repolist repo id repo name AppStream CentOS-8 - AppStream BaseOS CentOS-8 - Base PowerTools CentOS-8 - PowerTools extras CentOS-8 - Extras ovirt-4.4 Latest oVirt 4.4 Release ovirt-4.4-advanced-virtualization Advanced Virtualization packages for x86_64 ovirt-4.4-centos-gluster7 CentOS-8 - Gluster 7 ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd ovirt-4.4-centos-ovirt44 CentOS-8 - oVirt 4.4 ovirt-4.4-copr:copr.fedorainfracloud.org:mdbarroso:ovsdbapp Copr repo for ovsdbapp owned by mdbarroso ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.22 Copr repo for NetworkManager-1.22 owned by networkmanager ovirt-4.4-copr:copr.fedorainfracloud.org:nmstate:nmstate-0.2 Copr repo for nmstate-stable owned by nmstate ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo for gluster-ansible owned by sac ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr repo for EL8_collection owned by sbonazzo ovirt-4.4-epel Extra Packages for Enterprise Linux 8 - x86_64 ovirt-4.4-virtio-win-latest virtio-win builds roughly matching what will be shipped in upcoming RHEL [root@ovmgr1 ~]# - /etc/yum.repos.d/ovirt-4.4.repo [ovirt-4.4] name=Latest oVirt 4.4 Release #baseurl=https://resources.ovirt.org/pub/ovirt-4.4/rpm/el$releasever/ mirrorlist= https://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.4-el$releasever enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.4 But if I run the command above I get: [root@ovmgr1 ~]# yum update ovirt\*setup\* Last metadata expiration check: 0:39:59 ago on Wed 11 Nov 2020 09:02:05 AM CET. Error: Problem 1: package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.11-1.el8.noarch requires ovirt-engine >= 4.4.0, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-setup-plugin-ovirt-engine-4.4.2.6-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.9-1.el8.noarch is filtered out by exclude filtering Problem 2: package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.11-1.el8.noarch requires ovirt-engine >= 4.4.0, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-engine-setup-4.4.3.11-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine = 4.4.3.11-1.el8, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-setup-4.4.2.6-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-disaster-recovery-1.3.0-1.el8.noarch - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.9-1.el8.noarch is filtered out by exclude filtering Problem 3: package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.11-1.el8.noarch requires ovirt-engine >= 4.4.0, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-engine-setup-plugin-cinderlib-4.4.3.11-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine = 4.4.3.11-1.el8, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-setup-plugin-cinderlib-4.4.2.6-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-engine-setup-1.2.4-1.el8.noarch - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.9-1.el8.noarch is filtered out by exclude filtering Problem 4: package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.11-1.el8.noarch requires ovirt-engine >= 4.4.0, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-engine-setup-plugin-imageio-4.4.3.11-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine = 4.4.3.11-1.el8, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-setup-plugin-imageio-4.4.2.6-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.9-1.el8.noarch is filtered out by exclude filtering Problem 5: package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.11-1.el8.noarch requires ovirt-engine >= 4.4.0, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.4.3.11-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine = 4.4.3.11-1.el8, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.4.2.6-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-image-template-1.2.2-1.el8.noarch - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.9-1.el8.noarch is filtered out by exclude filtering Problem 6: problem with installed package ovirt-engine-4.4.2.6-1.el8.noarch - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-infra-1.2.2-1.el8.noarch Problem 7: problem with installed package ovirt-engine-ui-extensions-1.2.3-1.el8.noarch - package ovirt-engine-ui-extensions-1.2.3-1.el8.noarch requires ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-cluster-upgrade provided by ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-cluster-upgrade provided by ovirt-ansible-cluster-upgrade-1.2.2-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-manageiq-1.2.1-1.el8.noarch Problem 8: problem with installed package ovirt-engine-setup-plugin-ovirt-engine-4.4.2.6-1.el8.noarch - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.11-1.el8.noarch requires ovirt-engine >= 4.4.0, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.2.6-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.10-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.10-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.3-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.3-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.4-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.4-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.5-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.5-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.6-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.6-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.7-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.7-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.8-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.8-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.9-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.9-1.el8, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.2.6-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.10-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.3-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.4-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.5-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.6-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.7-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.8-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.9-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-setup-plugin-ovirt-engine-common-4.4.2.6-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-repositories-1.2.5-1.el8.noarch - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.9-1.el8.noarch is filtered out by exclude filtering Problem 9: problem with installed package ovirt-engine-webadmin-portal-4.4.2.6-1.el8.noarch - package ovirt-engine-webadmin-portal-4.4.2.6-1.el8.noarch requires ovirt-engine = 4.4.2.6-1.el8, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-roles-1.2.3-1.el8.noarch Problem 10: problem with installed package ovirt-engine-tools-4.4.2.6-1.el8.noarch - package ovirt-engine-tools-4.4.2.6-1.el8.noarch requires ovirt-engine = 4.4.2.6-1.el8, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-shutdown-env-1.1.0-1.el8.noarch Problem 11: problem with installed package ovirt-engine-restapi-4.4.2.6-1.el8.noarch - package ovirt-engine-restapi-4.4.2.6-1.el8.noarch requires ovirt-engine = 4.4.2.6-1.el8, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-vm-infra-1.2.3-1.el8.noarch (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) [root@ovmgr1 ~]# Thanks, Gianluca

4 12

[ANN] oVirt 4.4.4 First Release Candidate is now available for testing
by Lev Veyde 12 Nov '20

12 Nov '20

oVirt 4.4.4 First Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.4 First Release Candidate for testing, as of November 12th, 2020. This update is the fourth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.4 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.4 (redeploy in case of already being on 4.4.4). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.4 release highlights: http://www.ovirt.org/release/4.4.4/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.4/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Re: sshd_config AuthorizedKeysFile
by Yedidyah Bar David 12 Nov '20

12 Nov '20

On Thu, Nov 12, 2020 at 11:44 AM Angus Clarke <angus(a)charworth.com> wrote: > > Righto > > For sure the ssh-copy-id is not happy either - in 20something years I've never used this before, I've always just manipulated files. > > I did start raising a bug ... missed some field, had to click back and lost all the previously inputted information - I forgot about this ... > > > Overall, tracing the issue is the thing that took too long, there was some message in the hosted-engine-deployment logs (one of the logs from the engine VM itself) which said something like "check you ssh host keys" (sorry, I've lost that information now) - it would have been useful to see it say something about editing the file /root/.ssh/authorized_keys on the KVM host prior to this. > > I didn't spend too long debugging the kvm-add-host-to-cluster issue - I didn't find too much in the way of obvious errors in logs on the 2nd KVM host for that either; rather - having just realised and resolved the hosted-engine deployment issue - I guessed the same response to the add-kvm-host to cluster issue which resolved that too. > > So maybe a bit of extra logging on the matter would be a great way forwards, or with such few use cases (am I really the only one to manipulate AuthorizedKeysFile? - wow!) then no action at all might be appropriate. If you still have the logs, please file a bug and attach them, and perhaps point out what you'd expect there that is missing (or just let us look at them, and if we decide that the information there is enough, we'll ask you, after finding the most relevant line). Generally speaking, and assuming your only problem was in "Add host to engine" flow (specifically also during hosted-engine deploy), you should find these logs in the _engine_ machine, in /var/log/ovirt-engine (and subdirs). The deploy process also tries to copy these logs to the _host_, under /var/log/ovirt-hosted-engine-setup, and this part was enhanced somewhat in 4.4.3 (see https://bugzilla.redhat.com/1844965 ). Best regards, > > Cheers > Angus > > # ls .ssh > ls: cannot access .ssh: No such file or directory > # ssh-copy-id server2 > > /usr/bin/ssh-copy-id: ERROR: failed to open ID file '/root/.pub': No such file or directory > (to install the contents of '/root/.pub' anyway, look at the -f option) > > ________________________________ > From: Martin Perina <mperina(a)redhat.com> > Sent: 12 November 2020 09:43 > To: Angus Clarke <angus(a)charworth.com> > Cc: users(a)ovirt.org <users(a)ovirt.org>; Dana Elfassy <delfassy(a)redhat.com>; Yedidyah Bar David <didi(a)redhat.com> > Subject: Re: [ovirt-users] sshd_config AuthorizedKeysFile > > Hi, > > could you please try if ssh-copy-id works with your non-standard sshd configuration? Because last time I've checked I haven't noticed that behavior and keys were always added to $HOME/.ssh/authorized_keys > > So feel free to create a bug for that, but up until now you are the first user using this non-standard configuration ... > > Regards, > Martin > > On Thu, Nov 12, 2020 at 9:00 AM Angus Clarke <angus(a)charworth.com> wrote: > > Hello > > Sharing for anyone who needs it, this was carried out on OL7, they use ovirt 4.3 > > In short: both the hosted-engine deployment routine and the host add to cluster routine distribute public ssh keys to /root/.ssh/authorized_keys regardless of the AuthorizedKeysFile setting in /etc/ssh/sshd_config. Both routines fail if AuthorizedKeysfile is not default. > > > The hosted-engine setup assumes AuthorizedKeysFile to be default (~/.ssh/authorized_keys) and creates a public key there, instead of following the sshd_config directive. The setup fails on the back of this. > > Once I commented this out of sshd_config file (assumes default) and restarted sshd on the KVM host that was running the hosted-engine deployment, the hosted-engine setup completed successfully. > > > Similarly, I could not deploy a second KVM host to the compute cluster until I had altered this setting on that 2nd KVM host - presumably that process has some similar routine that unwittingly writes keys to ~/.ssh/authorized_keys. > > HTH > Angus > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UMJ4Y622RALUU… > > > > -- > Martin Perina > Manager, Software Engineering > Red Hat Czech s.r.o. -- Didi

1 0

Re: sshd_config AuthorizedKeysFile
by Martin Perina 12 Nov '20

12 Nov '20

Hi, could you please try if ssh-copy-id works with your non-standard sshd configuration? Because last time I've checked I haven't noticed that behavior and keys were always added to $HOME/.ssh/authorized_keys So feel free to create a bug for that, but up until now you are the first user using this non-standard configuration ... Regards, Martin On Thu, Nov 12, 2020 at 9:00 AM Angus Clarke <angus(a)charworth.com> wrote: > Hello > > Sharing for anyone who needs it, this was carried out on OL7, they use > ovirt 4.3 > > In short: both the hosted-engine deployment routine and the host add to > cluster routine distribute public ssh keys to /root/.ssh/authorized_keys > regardless of the AuthorizedKeysFile setting in /etc/ssh/sshd_config. Both > routines fail if AuthorizedKeysfile is not default. > > > The hosted-engine setup assumes AuthorizedKeysFile to be default > (~/.ssh/authorized_keys) and creates a public key there, instead of > following the sshd_config directive. The setup fails on the back of this. > > Once I commented this out of sshd_config file (assumes default) and > restarted sshd on the KVM host that was running the hosted-engine > deployment, the hosted-engine setup completed successfully. > > > Similarly, I could not deploy a second KVM host to the compute cluster > until I had altered this setting on that 2nd KVM host - presumably that > process has some similar routine that unwittingly writes keys to > ~/.ssh/authorized_keys. > > HTH > Angus > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/UMJ4Y622RALUU… > -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

2 1

Re: Cluster compatibility version 4.5 on oVirt 4.4
by Christopher Law 12 Nov '20

12 Nov '20

I should have pointed out that in my case the hosted engine failed to install. After the Local VM came up the host was marked as non-operational because the cluster (which I had given a custom name via ansible input) was set to compatibility 4.5 and was not changeable. No idea why the cluster was created at 4.5 if that is not supposed to be available yet or marked for some sort of future release. This caused the host to be non-operational with a warning that the “host” needed upgrading, so perhaps it’s a slightly different issue to that faced below. If you have faced this issue though I would appreciated some advice on how to resolve it. I noticed the default cluster was marked as 4.4. My plan is therefore to re-install the hosted engine and use the “Default” datacentre and cluster names and changes these later. From: Christopher Law <chris(a)chrislaw.me> Sent: 12 November 2020 09:21 To: Ritesh Chikatwar <rchikatw(a)redhat.com>; shadow emy <shadow.emy1(a)gmail.com> Cc: users <users(a)ovirt.org> Subject: [ovirt-users] Re: Cluster compatibility version 4.5 on oVirt 4.4 I’ve also faced this issue, which is surprising since I used an ovirt node download for 4.4. How did you resolve it? How can you upgrade to CentOS 8.3 or downgrade the cluster? Thanks, Chris. From: Ritesh Chikatwar <rchikatw(a)redhat.com<mailto:rchikatw@redhat.com>> Sent: 12 November 2020 05:10 To: shadow emy <shadow.emy1(a)gmail.com<mailto:shadow.emy1@gmail.com>> Cc: users <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: [ovirt-users] Re: Cluster compatibility version 4.5 on oVirt 4.4 Hello, To upgrade to cluster 4.5 you need a 8.3 host. I guess still CentOS 8.3 is not available. I am not sure on CentOS 8.3 availability. If it's available please make sure your host is upgraded to 8.3 . On Thu, Nov 12, 2020, 5:38 AM shadow emy <shadow.emy1(a)gmail.com<mailto:shadow.emy1@gmail.com>> wrote: Just to confirm i face similar problem. Yes i saw that warning too : "Upgrade Cluster Compatibility Level" to upgrade the Cluster to version 4.5. Though when i try to do that there are a lot of errors. In GUI : Error while executing action: Cannot change Cluster Compatibility Version to higher version when there are active Hosts with lower version. -Please move Host host1, host2, host3 with lower version to maintenance first. In engine.log : WARN [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-163) [2c681b74-8666-4f2f-b2e0-6b20e98f417e] Validation of action 'UpdateCluster' failed for user admin@internal-authz. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,$host host1, host2, host3,CLUSTER_CANNOT_UPDATE_COMPATIBILITY_VERSION_WITH_LOWER_HOSTS I did not find any documentation for 4.5 cluster compatibility, so i like as well to understand why is that option present there. It will be used when ovirt 4.5.x will be released ? _______________________________________________ Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/3UGQ6HPT2HTEG…

1 0

Cluster compatibility version 4.5 on oVirt 4.4
by tferic＠swissonline.ch 12 Nov '20

12 Nov '20

Hi Today, I upgraded oVirt from 4.3 to 4.4.3. After the upgrade, I upgraded the compatibility from 4.3 to 4.4. I noticed that the cluster config is offering me another upgrade of the compatibility to version 4.5. Up until now, I was under the impression that the compatibility version must match the oVirt version. I am now reluctant to upgrade the compatibility to 4.5, while my oVirt version is still at 4.4 (there is no oVirt 4.5 at this time). Is it safe to upgrade the compatibility in any case, or are there certain circumstances, where we should refrain from upgrading it? I wasn't able to find anything in the documentation. Kind regards Toni Feric

4 3

Re: sshd_config AuthorizedKeysFile
by Yedidyah Bar David 12 Nov '20

12 Nov '20

On Thu, Nov 12, 2020 at 10:01 AM Angus Clarke <angus(a)charworth.com> wrote: > > Hello > > Sharing for anyone who needs it, this was carried out on OL7, they use ovirt 4.3 > > In short: both the hosted-engine deployment routine and the host add to cluster routine distribute public ssh keys to /root/.ssh/authorized_keys regardless of the AuthorizedKeysFile setting in /etc/ssh/sshd_config. Both routines fail if AuthorizedKeysfile is not default. > > > The hosted-engine setup assumes AuthorizedKeysFile to be default (~/.ssh/authorized_keys) and creates a public key there, instead of following the sshd_config directive. The setup fails on the back of this. > > Once I commented this out of sshd_config file (assumes default) and restarted sshd on the KVM host that was running the hosted-engine deployment, the hosted-engine setup completed successfully. > > > Similarly, I could not deploy a second KVM host to the compute cluster until I had altered this setting on that 2nd KVM host - presumably that process has some similar routine that unwittingly writes keys to ~/.ssh/authorized_keys. Thanks for the report. Would you like to open one or two bugs about this? I think it's just bug, though - from searching relevant source - in the code adding a host to the engine. This code is also used during hosted-engine deploy. We also have code there to add lines to this file on the appliance (engine vm image), but I do not believe users will work so hard as to update the image before deploy. So one bug is probably enough. To make sure, please include there all relevant details about how "they" (your customer?) configure their machines - e.g. is it only during their installation (image/PXE/etc.) or also routinely (puppet etc.) I admit I am not sure what the expected behavior should be, though: An admin can run sshd with a custom file. So should we also check that? Perhaps it's enough if we allow the admin to set a custom location also for oVirt, instead of trying to guess. And make sure that the failure error message is clear and unique enough so that people searching the net for it find your bug, so can find how to configure it :-) Best regards, -- Didi

1 0

sshd_config AuthorizedKeysFile
by Angus Clarke 12 Nov '20

12 Nov '20

Hello Sharing for anyone who needs it, this was carried out on OL7, they use ovirt 4.3 In short: both the hosted-engine deployment routine and the host add to cluster routine distribute public ssh keys to /root/.ssh/authorized_keys regardless of the AuthorizedKeysFile setting in /etc/ssh/sshd_config. Both routines fail if AuthorizedKeysfile is not default. The hosted-engine setup assumes AuthorizedKeysFile to be default (~/.ssh/authorized_keys) and creates a public key there, instead of following the sshd_config directive. The setup fails on the back of this. Once I commented this out of sshd_config file (assumes default) and restarted sshd on the KVM host that was running the hosted-engine deployment, the hosted-engine setup completed successfully. Similarly, I could not deploy a second KVM host to the compute cluster until I had altered this setting on that 2nd KVM host - presumably that process has some similar routine that unwittingly writes keys to ~/.ssh/authorized_keys. HTH Angus

1 0

Upgrade OVIRT from 3.6 to 4.3
by Miguel Angel Costas 12 Nov '20

12 Nov '20

Hi Guys! I need to upgrade from 3.6 to 4.3 and I have a doubt. Do I need to restard VMs for each upgrade (DC Compatibilty 1° 4.0 - 2° 4.1 - 3° 4.2 and 4° 4.3) or can modify the compatibilty from 3.6 to 4.2 and restart the vms in this only step. Best regards

2 1

Adding iscsi issue 4.3
by thilburn＠generalpacific.com 11 Nov '20

11 Nov '20

When connecting an iscsi connection from an array I get the following popup "A database error occurred. Please contact your system administrator." I have checked everything and the only device connected right now is the single host in the datacenter. If I check the box " Approve operation" and click Ok it will error out with "A database error occurred. Please contact your system administrator." This is a new volume and no other machine is connected to this LUN or array. Below is from the vdsm log 2020-11-11 10:42:26,087-0800 INFO (jsonrpc/0) [vdsm.api] START getDeviceList(storageType=3, guids=[u'32021001378a6ddad'], checkStatus=True, options={}) from=::ffff:XXXXXX,46208, flow_id=d09dbfd6-2256-48ad-8597-b6c581def1fd, task_id=67c17255-3ffb-4e8b-b6d3-a4e40836d12c (api:48) 2020-11-11 10:42:26,650-0800 INFO (jsonrpc/0) [storage.LVM] Overriding read_only mode current=True override=False (lvm:398) 2020-11-11 10:42:26,822-0800 INFO (jsonrpc/0) [vdsm.api] FINISH getDeviceList return={'devList': [{'status': 'used', 'vendorID': 'ETIUSA', 'capacity': '3999688294400', 'fwrev': '10E', 'discard_zeroes_data': 0, 'vgUUID': '', 'pvsize': '', 'pathlist': [{'connection': u'10.87.172.100', 'iqn': u'XXXXXX.XXXXXX.XXXXXX:storage3', 'portal': '0', 'port': '3260', 'initiatorname': u'default'}], 'logicalblocksize': '512', 'discard_max_bytes': 0, 'pathstatus': [{'type': 'iSCSI', 'physdev': 'sdc', 'capacity': '3999688294400', 'state': 'active', 'lun': '0'}], 'devtype': 'iSCSI', 'physicalblocksize': '512', 'pvUUID': '', 'serial': 'SETIUSA_UltraStorRS8IP4_2021001378A6DDAD', 'GUID': '32021001378a6ddad', 'productID': 'UltraStorRS8IP4'}]} from=::ffff:XXXXX,46208, flow_id=d09dbfd6-2256-48ad-8597-b6c581def1fd, task_id=67c17255-3ffb-4e8b-b6d3-a4e40836d12c (api:54) 2020-11-11 10:42:26,823-0800 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.getDeviceList succeeded in 0.74 seconds (__init__:312) 2020-11-11 10:42:27,158-0800 INFO (jsonrpc/2) [api.host] START getAllVmStats() from=::1,48480 (api:48) 2020-11-11 10:42:27,159-0800 INFO (jsonrpc/2) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::1,48480 (api:54) 2020-11-11 10:42:27,159-0800 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312) 2020-11-11 10:42:27,393-0800 INFO (jsonrpc/1) [api.host] START getAllVmStats() from=::ffff:XXXXX,46208 (api:48) 2020-11-11 10:42:27,394-0800 INFO (jsonrpc/1) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::ffff:XXXXX,46208 (api:54) 2020-11-11 10:42:27,394-0800 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312) 2020-11-11 10:43:12,323-0800 INFO (jsonrpc/6) [vdsm.api] START createVG(vgname=u'35e95355-75db-4640-bf99-e576b9ce39aa', devlist=[u'32021001378a6ddad'], force=True, options=None) from=::ffff:XXXXX,46208, flow_id=2c973734, task_id=91f2ab5b-017a-4c88-aa45-ece3bd920ce0 (api:48) 2020-11-11 10:43:12,348-0800 INFO (jsonrpc/6) [storage.LVM] Overriding read_only mode current=True override=False (lvm:398) 2020-11-11 10:43:12,409-0800 INFO (jsonrpc/4) [api.host] START getAllVmStats() from=::ffff:XXXXXX,46208 (api:48) 2020-11-11 10:43:12,410-0800 INFO (jsonrpc/4) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::ffff:XXXXXXX,46208 (api:54) 2020-11-11 10:43:12,410-0800 INFO (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312) 2020-11-11 10:43:12,520-0800 ERROR (jsonrpc/6) [storage.LVM] pvcreate failed with rc=5 (lvm:988) 2020-11-11 10:43:12,520-0800 ERROR (jsonrpc/6) [storage.LVM] [], [' Device /dev/mapper/32021001378a6ddad excluded by a filter.'] (lvm:989) 2020-11-11 10:43:12,520-0800 INFO (jsonrpc/6) [vdsm.api] FINISH createVG error=Failed to initialize physical device: ("[u'/dev/mapper/32021001378a6ddad']",) from=::ffff:XXXXXX,46208, flow_id=2c973734, task_id=91f2ab5b-017a-4c88-aa45-ece3bd920ce0 (api:52) 2020-11-11 10:43:12,520-0800 ERROR (jsonrpc/6) [storage.TaskManager.Task] (Task='91f2ab5b-017a-4c88-aa45-ece3bd920ce0') Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in createVG File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2146, in createVG force=force) File "/usr/lib/python2.7/site-packages/vdsm/storage/lvm.py", line 1256, in createVG _initpvs(pvs, metadataSize, force) File "/usr/lib/python2.7/site-packages/vdsm/storage/lvm.py", line 990, in _initpvs raise se.PhysDevInitializationError(str(devices)) PhysDevInitializationError: Failed to initialize physical device: ("[u'/dev/mapper/32021001378a6ddad']",) 2020-11-11 10:43:12,520-0800 INFO (jsonrpc/6) [storage.TaskManager.Task] (Task='91f2ab5b-017a-4c88-aa45-ece3bd920ce0') aborting: Task is aborted: 'Failed to initialize physical device: ("[u\'/dev/mapper/32021001378a6ddad\']",)' - code 601 (task:1181) 2020-11-11 10:43:12,521-0800 ERROR (jsonrpc/6) [storage.Dispatcher] FINISH createVG error=Failed to initialize physical device: ("[u'/dev/mapper/32021001378a6ddad']",) (dispatcher:83) 2020-11-11 10:43:12,521-0800 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call LVMVolumeGroup.create failed (error 601) in 0.20 seconds (__init__:312)

1 1

Dependencies failure when upgrading from version 4.4.2 to 4.4.3
by jorgevisentini＠gmail.com 11 Nov '20

11 Nov '20

When I update the Engine and Host, many dependencies are missing, as shown by the host error log: Error: Problem 1: package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch requires ovirt-ansible-engine-setup >= 1.1.9, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-engine-setup provided by ovirt-ansible-engine-setup-1.2.4-1.el8.noarch - cannot install the best update candidate for package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-engine-setup-1.2.4-1.el8.noarch Problem 2: package ovirt-host-4.4.1-4.el8.x86_64 requires ovirt-hosted-engine-setup, but none of the providers can be installed - package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch requires ovirt-ansible-hosted-engine-setup >= 1.0.34, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-hosted-engine-setup provided by ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch - cannot install the best update candidate for package ovirt-host-4.4.1-4.el8.x86_64 - cannot install the best update candidate for package ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch - package ovirt-ansible-hosted-engine-setup-1.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-ansible-hosted-engine-setup-1.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-ansible-hosted-engine-setup-1.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-ansible-hosted-engine-setup-1.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-hosted-engine-setup-2.4.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-hosted-engine-setup-2.4.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-hosted-engine-setup-2.4.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-hosted-engine-setup-2.4.8-1.el8.noarch is filtered out by exclude filtering (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

3 3

Single Node HCI upgrade procedure from CentOS7/oVirt 4.3 to CentOS8/oVirt 4.4?
by thomas＠hoberg.net 11 Nov '20

11 Nov '20

I can hear you saying: "You did understand that single node HCI is just a toy, right?" For me the primary use of a single node HCI is adding some disaster resilience in small server edge type scenarios, where a three node HCI provides the fault tolerance: 3+1 with a bit of distance, warm or even cold stand-by, potentially manual switch and reduced workload in case disaster strikes. Of course, another 3nHCI would be better, but who gets that type of budget, right? What I am trying say: If you want oVirt to gain market share, try to give HCI more love. And while you're at it, try to make expanding from 1nHCI to 3nHCI (and higher counts) a standard operational procedure to allow expanding a disaster stand-by into a production setup, while the original 3nHCI is being rebuilt. For me low-budget HCI is where oVirt has its biggest competitive advantage against vSan and Nutanix, so please don't treat the HCI/gluster variant like an unwanted child any more. In the mean-time OVA imports (from 4.3.10 exports) on my 4.4.2 1nHCI fail again, which I'll report separately.

2 1

Upgrade Problem oVirt engine 4.4.1.8-1.el8 -> 4.4.3
by Andrei Verovski 11 Nov '20

11 Nov '20

Hi ! I’m trying to upgrade oVirt engine 4.4.1.8-1.el8 to the latest 4.4.3, running as KVM appliance (not hosted engine). This sequence of commands yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm engine-upgrade-check yum update ovirt\*setup\* Results in a long list of dependency errors, short excerpt below. Looks like something (e.g. repo) is missing. How to fix this? Thanks in advance. ————— LOG ---------- Problem 1: problem with installed package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch - package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch requires ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be installed Problem 2: package ovirt-engine-4.4.1.8-1.el8.noarch requires ovirt-engine-ui-extensions >= 1.0.4, but none of the providers can be installed - package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch requires ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be installed - package ovirt-engine-4.4.1.8-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-cluster-upgrade provided by ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch

3 3

Cluster with Hosted Engine update BIOS Setting Ovirt 4.4.3
by scrik787＠gmail.com 11 Nov '20

11 Nov '20

I changed the type in the cluster and now my hosted-engine machine won't start!. There are no backups. How can I manually change the parameters of the machine from under the roof so that it starts and I can restore ovirt to work Error in logs: XML error: The device at PCI address 0000:00:02.0 cannot be plugged into the PCI controller with index='0'. It requires a controller that accepts a pcie-root-port VDSM.log https://pastebin.com/vsAKy9rX

2 1

Host NonResponsive after migration to oVirt 4.4
by tferic＠swissonline.ch 11 Nov '20

11 Nov '20

Hi I am looking for help after my oVirt upgrade failed. I have upgraded from ovirt 4.3 to 4.4 following the instructions here: https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3 <https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3> It's a single-host (standalone engine) test environment. I wiped CentOS 7 and reinstalled a fresh CentOS 8. I installed the oVirt 4.4 repo and all the necessary software packets. I used `engine-backup --mode=restore --file=/tmp/ovirt-engine-pre-upgrade.backup --provision-all-databases` from a backup file I created before I started the upgrade. After the restore, I ran `engine-setup`. I did not get any errors during any of these steps on the console. So the upgrade could be considered successful from that perspective. After the upgrade, I login to the ovirt admin portal, and I try to "Activate" my host (was set to "Maintenance" mode before upgrade). The Activation fails with error "NonResponsive" in the GUI. Under the "bell" icon, I find the Event "Host nuc1.feric.ch is non responsive.” In /var/log/ovirt-engine/engine.log, I find the following error: ``` 2020-11-09 23:12:21,080+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [] Command 'GetCapabilitiesAsyncVDSCommand(HostName = nuc1.feric.ch, VdsIdAndVdsVDSCommandParametersBase:{hostId='d7c30cc0-ac59-4cf3-a1e7-b9fae9db83fb', vds=‘Host[nuc1.feric.h,d7c30cc0-ac59-4cf3-a1e7-b9fae9db83fb]'})' execution failed: java.net.ConnectException: Connection refused ``` `systemctl status ovirt-engine` shows that the engine is running. I am able to reboot the host from the oVirt GUI directly. Does anyone have an idea how to proceed? Many thanks Toni

3 7

Clone a VM in the User Portal
by Nicolás 11 Nov '20

11 Nov '20

Hi, We're using oVirt 4.3.8, having an organization that intensively uses the User Portal. After upgrading from 4.2, we've noticed that cloning a VM from within the User Portal is not possible anymore. In our case, this feature was heavily used by hundreds of students deploying their VMs. Is this feature in the roadmap yet? If not, do you consider it useful to open a RFE? Thank you. Regards, Nico

3 6

Cannot restore engine from 4.3.9 to 4.4.3
by tferic＠swissonline.ch 11 Nov '20

11 Nov '20

Hi I just tried to restore my engine backup taken from release 4.3.9.4 to a newer oVirt installation release 4.4.3.11. The restore process fails with a FATAL error. I was under the impression that backups from all 4.3 versions were supposed to be restorable on 4.4. My installation is a single-box all-in-one (Standalone Engine installed together with oVirt node). # engine-backup --mode=restore --file=/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup --provision-all-databases Start of engine-backup with mode 'restore' scope: all archive file: /exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup log file: /var/log/ovirt-engine-backup/ovirt-engine-restore-20201111031500.log Preparing to restore: - Unpacking file '/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup' FATAL: Backup was created by version '4.3.9.4' and can not be restored using the installed version 4.4.3.11 Complete content of the restore log file: 2020-11-11 03:15:00 23143: Start of engine-backup mode restore scope all file /exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup 2020-11-11 03:15:00 23143: OUTPUT: Start of engine-backup with mode 'restore' 2020-11-11 03:15:00 23143: OUTPUT: scope: all 2020-11-11 03:15:00 23143: OUTPUT: archive file: /exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup 2020-11-11 03:15:00 23143: OUTPUT: log file: /var/log/ovirt-engine-backup/ovirt-engine-restore-20201111031500.log 2020-11-11 03:15:00 23143: OUTPUT: Preparing to restore: 2020-11-11 03:15:01 23143: OUTPUT: - Unpacking file '/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup' 2020-11-11 03:15:01 23143: Opening tarball /exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup to /tmp/engine-backup.UAcLerghwY 2020-11-11 03:15:01 23143: Verifying hash 2020-11-11 03:15:01 23143: Verifying version 2020-11-11 03:15:01 23143: FATAL: Backup was created by version '4.3.9.4' and can not be restored using the installed version 4.4.3.11 regards, Toni Feric

2 1

Problem with Cluster-wise BIOS Settings in oVirt 4.4
by Rodrigo G. López 11 Nov '20

11 Nov '20

Hi all, We are running an oVirt 4.4 Hosted Engine as a VM, and after changing the Cluster's BIOS type from Q35 with Legacy BIOS (the default one after installation) to Preexistent, the VM fails with the following error: XML error: The device at PCI address 0000:00:02.0 cannot be plugged into the PCI controller with index='0'. It requires a controller that accepts a pcie-root-port. We need it so that we can run imported VMs from a previous version of oVirt, namely 4.0. Applying the BIOS settings individually works but as an attempt to generalize the settings we decided to apply it to the full cluster. Tell me if you need more data. Cheers, -rodri

4 6

oVirt 4.4.2 MS Windows 10 sysprep floppy
by ozmen62＠hotmail.com 11 Nov '20

11 Nov '20

Hi, I've cretated a template which has sysprep. Every document about sysprep says use "Attach Floppy" , but we know this function has been disabled/deprecated So, when i use Run One, attach windows cdrom and put in it definitions (domain name, user credentials etc) , nothing happens. I also have correct properties and sysprep files in engine Just windows boot like it is new machine and ask lots of questions for prepare itself. Would someone please explain this? How can i run sysprep correctly?

4 11

setting routing rules for guests?
by yam yam 10 Nov '20

10 Nov '20

Hello everyone! I'm wondering there is any feature like applying routing rules for VM to reach the external network (and vice versa). and I guess it's different according to using external provider(OVN). if not, how to users usually assign floating IP to VM?? Thanks Sincerely,

3 7

Re: Clone a VM in the User Portal
by Arik Hadas 10 Nov '20

10 Nov '20

On Tue, Nov 10, 2020 at 10:10 PM tferic(a)swissonline.ch < tferic(a)swissonline.ch> wrote: > Cloning VM's is a core feature of virtualization. > > I remember having cloned VM's back in the 90's with the free VMware > version 0.9. > > My main use case ever since is cloning fully configured production servers > into a testservers, for isolated testing. > > Why would a hypervisor not offer cloning, when it is possible and useful? > > regards, Toni > (Added users(a)ovirt.org back) Sure, it can be handy in some cases - that's why we've implemented it in oVirt and enhance it in 4.4.3 (for running VMs). But I wouldn't expect it to be commonly used via the user portal, that's why I am interested in the use-case. > > On 10.11.20 16:22, Arik Hadas wrote: > > > > On Tue, Nov 10, 2020 at 4:37 PM Nicolás <nicolas(a)devels.es> wrote: > >> Hi Arik, >> >> El 10/11/20 a las 13:21, Arik Hadas escribió: >> >> >> >> On Tue, Nov 10, 2020 at 3:08 PM Nicolás <nicolas(a)devels.es> wrote: >> >>> Hi Sharon, >>> >>> Thanks for the reply! I've opened [1], so hopefully someone will be able >>> to implement it. >>> >>> Regards, >>> >>> Nico >>> >>> [1]: https://github.com/oVirt/ovirt-site/issues/2389 >>> >>> El 10/11/20 a las 11:38, Sharon Gratch escribió: >>> >>> Hi, >>> >>> This feature of cloning a VM was indeed part of the old User Portal and >>> you are right that it's not supported by the newer VM Portal (since oVirt >>> 4.3). >>> It seemed that this wasn't required by VM Portal users (no user >>> complained up till now) and that's why we omitted it and it's not part of >>> our current roadmap to implement it as well. >>> >>> Nevertheless, there is no real reason not to include that ability as >>> part of VM Portal, so you are most welcome to open an issue on >>> https://github.com/oVirt/ovirt-web-ui/issues >>> <https://github.com/oVirt/ovirt-site/issues> >>> and you can push a fix yourself if you have time (or someone else from >>> the community) :-) >>> >>> Thanks! >>> Sharon >>> >>> On Fri, Nov 6, 2020 at 11:06 AM Nicolás <nicolas(a)devels.es> wrote: >>> >>>> Hi, >>>> >>>> We're using oVirt 4.3.8, having an organization that intensively uses >>>> the User Portal. After upgrading from 4.2, we've noticed that cloning a >>>> VM from within the User Portal is not possible anymore. In our case, >>>> this feature was heavily used by hundreds of students deploying their >>>> VMs. >>>> >>> >> Out of curiosity, why cloning a VM and not provisioning the VMs from >> template(s)? >> >> >> >> Most of our students are IT-related, and their professors want to teach >> them the procedure to deploy a VM from scratch. Some other courses surely >> deploy their VMs from a template as they are not that IT oriented and they >> just want to have a working VM instead of building it from scratch. We have >> a lot of casuistry, but in our case about 400~500 students would very >> welcome having back the clone option. >> > > Thanks Nicolás. > I'd say that even for the IT-related students it may make more sense to > provision VMs from templates instead of cloning VMs - > so you want them to deploy VMs from scratch, which means starting with a > VM that is based on the blank template, add disk(s) and other devices, > install and configure the guest and such; and then the students would use > clone-VM to duplicate the VM they just prepared, right? > Why would you want them to clone the VM rather than creating a template > out of this VM and provision further VMs from that template with > thin-provisioned disks? > > >> >> Regards, >> >> Nico >> >> >>>> Is this feature in the roadmap yet? If not, do you consider it useful >>>> to >>>> open a RFE? >>>> >>>> Thank you. >>>> >>>> Regards, >>>> >>>> Nico >>>> _______________________________________________ >>>> Users mailing list -- users(a)ovirt.org >>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>>> oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> List Archives: >>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/HFMFJRV3AC3GV… >>>> >>> >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/RUEW52WZUD27I… >>> >> >> > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/QXPS6FCRT66HF… > >

1 0

[ANN] oVirt 4.4.3 is now generally available
by Sandro Bonazzola 10 Nov '20

10 Nov '20

oVirt 4.4.3 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.3 , as of November 10th, 2020. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.4.3 Release? This update is the third in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.2 / 8.3 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.2 / 8.3 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) Please note that this release introduces cluster compatibility level 4.5 which is supported only with Red Hat Enterprise Linux 8.3 or equivalent. oVirt Node and Appliance have been updated, including: - oVirt 4.4.3: https://www.ovirt.org/release/4.4.3/ - Ansible 2.9.15: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Glusterfs 7.8: https://docs.gluster.org/en/latest/release-notes/7.8/ See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG will be available soon for CentOS Linux 8 Additional resources: - Read more about the oVirt 4.4.3 release highlights: https://www.ovirt.org/release/4.4.3/ - Get more oVirt project updates on Twitter: https://twitter.com/ovirt - Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/release/4.4.3/ <https://www.ovirt.org/release/4.4.3/> [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV 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 0

VM's gone to unknown state
by hjadavalluva＠ukaachen.de 10 Nov '20

10 Nov '20

Hello, I have an issue with ovirt 4.3 console. The exact issue is, except hosted engine, all other VM's gone to unknown state. I wonder what's the problem is? And how bring back the VM's to normal state. I can see that nothing is enable (for instance, acktivate option, maintaiance option, etc). Can anyone guide me please in this? Thanks in advance! Best Regards, Hariharan

3 9

Re: LiveStorageMigration fail
by Christoph Köhler 10 Nov '20

10 Nov '20

yes, the output is: -[ RECORD 1 ]---------+------------------------------------- image_guid | 77af2f70-f3e3-4e69-a062-b0dd9970e9e3 creation_date | 2019-05-23 10:08:39+02 size | 348966092800 it_guid | 00000000-0000-0000-0000-000000000000 parentid | 00000000-0000-0000-0000-000000000000 imagestatus | 1 lastmodified | 2020-11-09 15:39:56.22+01 vm_snapshot_id | edade1d1-05ce-46a4-9929-984e5ad3e025 volume_type | 2 volume_format | 4 image_group_id | 02240cf3-65b6-487c-b5af-c266a1dd18f8 _create_date | 2018-01-11 17:31:50.075047+01 _update_date | 2020-11-09 15:41:01.008245+01 active | t volume_classification | 1 qcow_compat | 2 On 09.11.20 17:23, Benny Zlotnik wrote: > Can you share the output of: > $ psql -U engine -d engine -c "\x on" -c "SELECT * FROM images where > image_group_id = '02240cf3-65b6-487c-b5af-c266a1dd18f8';" > > On Mon, Nov 9, 2020 at 5:18 PM Christoph Köhler > <koehler(a)luis.uni-hannover.de <mailto:koehler@luis.uni-hannover.de>> wrote: > > yes sure, here they are: > > On 09.11.20 15:30, Benny Zlotnik wrote: > > Can you send me the full logs with the failure (vdsm+engine)? > > > > On Mon, Nov 9, 2020 at 4:26 PM Christoph Köhler > > <koehler(a)luis.uni-hannover.de > <mailto:koehler@luis.uni-hannover.de> > <mailto:koehler@luis.uni-hannover.de > <mailto:koehler@luis.uni-hannover.de>>> wrote: > > > > engine runs with 4.3.10.4-1 > > and yes, the message is persistently the same, so I cannot > migrate this > > disk. > > > > > > > > On 09.11.20 15:10, Benny Zlotnik wrote: > > > Which version are you using? > > > Did this happen more than once for the same disk? > > > A similar bug was fixed in 4.3.10.1[1] > > > There is another bug with a similar symptom which occurs very > > rarely and > > > we were unable to reproduce it > > > > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1758048 > > > > > > On Mon, Nov 9, 2020 at 3:57 PM Christoph Köhler > > > <koehler(a)luis.uni-hannover.de > <mailto:koehler@luis.uni-hannover.de> > > <mailto:koehler@luis.uni-hannover.de > <mailto:koehler@luis.uni-hannover.de>> > > <mailto:koehler@luis.uni-hannover.de > <mailto:koehler@luis.uni-hannover.de> > > <mailto:koehler@luis.uni-hannover.de > <mailto:koehler@luis.uni-hannover.de>>>> wrote: > > > > > > Hello experts, > > > > > > perhaps someone has an idea about that error. It appears > when > > in try to > > > migrate a disk to another storage, and this live. > Generally it > > works > > > good but - this is the log snippet: > > > > > > HSMGetAllTasksStatusesVDS failed: Error during > destination image > > > manipulation: > u"image=02240cf3-65b6-487c-b5af-c266a1dd18f8, dest > > > domain=3c4fbbfe-6796-4007-87ab-d7f205b7fae3: msg=Invalid > > parameter: > > > 'capacity=134217728000'" > > > > > > Surely the is enough space on the target domain for this > operation > > > (~4TB). > > > > > > Any ideas..? > > > > > > Greetings from > > > Chris > > > _______________________________________________ > > > Users mailing list -- users(a)ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>> > > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>> > > > To unsubscribe send an email to users-leave(a)ovirt.org > <mailto:users-leave@ovirt.org> > > <mailto:users-leave@ovirt.org <mailto:users-leave@ovirt.org>> > > > <mailto:users-leave@ovirt.org > <mailto:users-leave@ovirt.org> <mailto:users-leave@ovirt.org > <mailto:users-leave@ovirt.org>>> > > > Privacy Statement: https://www.ovirt.org/privacy-policy.html > > > oVirt Code of Conduct: > > > https://www.ovirt.org/community/about/community-guidelines/ > > > List Archives: > > > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/6KT5HQXEFB477… > > > > > >

1 0

The Master data domain can't be activated
by Miguel Angel Costas 09 Nov '20

09 Nov '20

Hi all!! I had a terrible problem with my blade and I lost the 2 nodes. I have installed a new server as a node ( ovirt-node-iso-3.6-0.999.201608311021.el7.centos.iso) but for any reason the data domain don't start. It the same node version. The ovirt manager is 3.6.7 If I create a new datacenter I can attach a lv from the same lun with the problem.. Someone could help me.. I have been working to solve the problem fron the saturday.. Thanks!

2 3

Cannot access ovirt engine
by suporte＠logicworks.pt 09 Nov '20

09 Nov '20

Hi, I was installing a VM and than I notice that cannot access the CD, after this could not access the engine anymore. The ovirt-engine service is running. But I have this error in the engine log: 2020-11-09 13:49:16,356Z ERROR [org.ovirt.engine.ui.frontend.server.dashboard.DashboardDataServlet.CacheUpdate.Inventory] (EE-ManagedThreadFactory-default-Thread-5) [] Could not update the Inventory Cache: Error while running SQL query: org.ovirt.engine.ui.frontend.server.dashboard.DashboardDataException: Error while running SQL query ovirt-engine-dwh.log 2020-11-09 13:57:21|Yd4P7G|GUQ4i7|NlyWRj|OVIRT_ENGINE_DWH|SampleTimeKeepingJob|Default|5|tWarn|tWarn_1|Can not sample data, oVirt Engine is not updating the statistics. Please check your oVirt Engine status.|9704 ovirt-engine-4.3.4.3-1.el7.noarch ovirt-engine-dwh-setup-4.3.8-1.el7.noarch Any idea? Thanks -- Jose Ferradeira http://www.logicworks.pt

2 4

Change compatibility level for data center/cluster, what exactly we are changing?
by Patrick Chiang 09 Nov '20

09 Nov '20

Hi all, From the procedure I learned at the last phase of upgrade, we should change compatibility level for data center/cluster, respectively. But may I know what exactly the settings we are changing - a config in a database or in a file? Actually my question is, are these changes can lead to any service downtime for "guest VM" or "Storage domain", "hypervisors"? Because lately my RHV 4.2 suffered a few network disconnections and that causes hosts to be fenced forcefully. I hope I can collect more info here to prepare for 4.2->4.3 upgrade. Thanks, Patrick Chiang

1 0

LiveStorageMigration fail
by Christoph Köhler 09 Nov '20

09 Nov '20

Hello experts, perhaps someone has an idea about that error. It appears when in try to migrate a disk to another storage, and this live. Generally it works good but - this is the log snippet: HSMGetAllTasksStatusesVDS failed: Error during destination image manipulation: u"image=02240cf3-65b6-487c-b5af-c266a1dd18f8, dest domain=3c4fbbfe-6796-4007-87ab-d7f205b7fae3: msg=Invalid parameter: 'capacity=134217728000'" Surely the is enough space on the target domain for this operation (~4TB). Any ideas..? Greetings from Chris

2 1

ovirt guest agent ubuntu 16.04.6 LTS
by suporte＠logicworks.pt 09 Nov '20

09 Nov '20

What is the best way to install ovirt guest on Ubuntu 16.04.6? What I did: # apt-get install ovirt-guest-agent I changed value in /etc/ovirt-guest-agent.conf to look like: [virtio] # device = /dev/virtio-ports/com.redhat.rhevm.vdsm device = /dev/virtio-ports/ovirt-guest-agent.0 # systemctl start ovirt-guest-agent Error on the log: OSError: [Errno 13] Permission denied: '/dev/virtio-ports/ovirt-guest-agent.0 Than I set the owner and group # chown ovirtagent:ovirtagent /dev/virtio-ports/ovirt-guest-agent.0 Than I was able to start the agent # systemctl status ovirt-guest-agent ● ovirt-guest-agent.service - oVirt Guest Agent Loaded: loaded (/lib/systemd/system/ovirt-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2020-10-31 19:50:03 WET; 9min ago Process: 6531 ExecStartPre=/bin/chown ovirtagent:ovirtagent /run/ovirt-guest-agent.pid (code=exited, status=0/SUCCESS) Process: 6527 ExecStartPre=/bin/touch /run/ovirt-guest-agent.pid (code=exited, status=0/SUCCESS) Process: 6524 ExecStartPre=/sbin/modprobe virtio_console (code=exited, status=0/SUCCESS) Main PID: 6537 (python) Tasks: 3 Memory: 68.7M CPU: 5.462s CGroup: /system.slice/ovirt-guest-agent.service └─6537 /usr/bin/python /usr/share/ovirt-guest-agent/ovirt-guest-agent.py Oct 31 19:52:05 alfa.acloud.pt python[6537]: [100B blob data] Oct 31 19:54:06 alfa.acloud.pt python[6537]: [90B blob data] Oct 31 19:54:06 alfa.acloud.pt python[6537]: [155B blob data] Oct 31 19:54:06 alfa.acloud.pt python[6537]: [100B blob data] Oct 31 19:56:06 alfa.acloud.pt python[6537]: [90B blob data] Oct 31 19:56:07 alfa.acloud.pt python[6537]: [155B blob data] Oct 31 19:56:07 alfa.acloud.pt python[6537]: [100B blob data] Oct 31 19:58:07 alfa.acloud.pt python[6537]: [90B blob data] Oct 31 19:58:08 alfa.acloud.pt python[6537]: [155B blob data] Oct 31 19:58:08 alfa.acloud.pt python[6537]: [100B blob data] Everytime I restart the VM I need to set the owner and group # chown ovirtagent:ovirtagent /dev/virtio-ports/ovirt-guest-agent.0 -- Jose Ferradeira http://www.logicworks.pt

4 8

cannot live migrate the hosted engine
by Rob Verduijn 07 Nov '20

07 Nov '20

Hello, In my hyperconverged environment I cannot live migrate the hosted engine. However shutting down the hosted engine then starting it on another host works fine. This is the only way to migrate the engine to any of the hosts that are configured for the engine. I can't seem to find anything in the logs and hosted-engine vm-status doesn't tell me anything. Anybody any ideas where to start looking ? Rob

2 3

Issue with ovirt self hosted engine instalaltion 4.4
by hjadavalluva＠ukaachen.de 06 Nov '20

06 Nov '20

Hello, Good Day! I'm Hariharan and I'm working as System Administrator in Linux platform for RWTH Uniklink - Germany. Currently I'm managing the Ovirt environment and I'm very new to this domain. Currently I'm facing an issue with Ovirt self hosted engine installation 4.4 in CentOS 8 server. I have an issue when mounting the glusterfs storage to a target machine. Below is the exact issue what I face; Error: "changed": false, "msg": "Error: the target storage domain contains only 11.0GiB of available space while a minimum of 61.0GiB is required If you wish to use the current target storage domain by extending it, make sure it contains nothing before adding it. Note: (gluster storage was installed and configured in Linux work station with adding additional hard disk in one of the two gluster storage linux work station. I used replicated volumes (replica 2) in creating gluster volumes) Hardware detail: device model: Dell R540 Capacity: 240 GB I tried best possibilities to resolve this issue but still I'm facing the same issue. Could you please help me in resolving this issue with your guidance or support.

4 18

Bond creation issue via hosted engine
by Harry O 06 Nov '20

06 Nov '20

Hi guys and girls, Every time I try to create a bond with my two onboard intel nic's (any type of bond) via hosted engine, it will fail with the following error "Error while executing action HostSetupNetworks: Unexpected exception", it will still get created on the node but then the engine will get the capabilities out of sync with the node and can't refresh. I will need to delete the bond manually on the node for the engine to be happy again. Anyone knows why? Here is some logs from engine log file: [root@ovirt1-engine ~]# cat /var/log/ovirt-engine/engine.log 2020-11-06 08:29:56,230+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.OvfDataUpdater] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [] Attempting to update VMs/Templates Ovf. 2020-11-06 08:29:56,236+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Before acquiring and wait lock 'EngineLock:{exclusiveLocks='[b150e472-1f45-11eb-8e70-00163e78288d=OVF_UPDATE]', sharedLocks=''}' 2020-11-06 08:29:56,236+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Lock-wait acquired to object 'EngineLock:{exclusiveLocks='[b150e472-1f45-11eb-8e70-00163e78288d=OVF_UPDATE]', sharedLocks=''}' 2020-11-06 08:29:56,237+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Running command: ProcessOvfUpdateForStoragePoolCommand internal: true. Entities affected : ID: b150e472-1f45-11eb-8e70-00163e78288d Type: StoragePool 2020-11-06 08:29:56,242+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Attempting to update VM OVFs in Data Center 'Default' 2020-11-06 08:29:56,243+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Successfully updated VM OVFs in Data Center 'Default' 2020-11-06 08:29:56,243+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Attempting to update template OVFs in Data Center 'Default' 2020-11-06 08:29:56,243+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Successfully updated templates OVFs in Data Center 'Default' 2020-11-06 08:29:56,243+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Attempting to remove unneeded template/vm OVFs in Data Center 'Default' 2020-11-06 08:29:56,245+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Successfully removed unneeded template/vm OVFs in Data Center 'Default' 2020-11-06 08:29:56,245+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Lock freed to object 'EngineLock:{exclusiveLocks='[b150e472-1f45-11eb-8e70-00163e78288d=OVF_UPDATE]', sharedLocks=''}' 2020-11-06 08:29:56,284+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] START, GetStorageDeviceListVDSCommand(HostName = ovirtn3.5ervers.lan, VdsIdVDSCommandParametersBase:{hostId='4ec53a62-5cf3-479a-baf5-44c5b7624d39'}), log id: 59a1c9e 2020-11-06 08:29:56,284+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22514) [] START, GetStorageDeviceListVDSCommand(HostName = ovirtn2.5ervers.lan, VdsIdVDSCommandParametersBase:{hostId='a4904c7c-92d7-4e4f-adf7-755f3c17335d'}), log id: 735f6d30 2020-11-06 08:29:57,020+01 WARN [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "'NoneType' object has no attribute 'iface'"}] 2020-11-06 08:29:57,020+01 WARN [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "'NoneType' object has no attribute 'iface'"}] 2020-11-06 08:29:57,020+01 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] Failed in 'GetStorageDeviceListVDS' method 2020-11-06 08:29:57,020+01 WARN [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "'NoneType' object has no attribute 'iface'"}] 2020-11-06 08:29:57,057+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-22513) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirtn3.5ervers.lan command GetStorageDeviceListVDS failed: Internal JSON-RPC error: {'reason': "'NoneType' object has no attribute 'iface'"} 2020-11-06 08:29:57,057+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] Command 'org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand' return value 'StorageDeviceListReturn:{status='Status [code=-32603, message=Internal JSON-RPC error: {'reason': "'NoneType' object has no attribute 'iface'"}]'}' 2020-11-06 08:29:57,057+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] HostName = ovirtn3.5ervers.lan 2020-11-06 08:29:57,057+01 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] Command 'GetStorageDeviceListVDSCommand(HostName = ovirtn3.5ervers.lan, VdsIdVDSCommandParametersBase:{hostId='4ec53a62-5cf3-479a-baf5-44c5b7624d39'})' execution failed: VDSGenericException: VDSErrorException: Failed to GetStorageDeviceListVDS, error = Internal JSON-RPC error: {'reason': "'NoneType' object has no attribute 'iface'"}, code = -32603 2020-11-06 08:29:57,057+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] FINISH, GetStorageDeviceListVDSCommand, return: , log id: 59a1c9e 2020-11-06 08:29:57,057+01 ERROR [org.ovirt.engine.core.bll.gluster.StorageDeviceSyncJob] (EE-ManagedThreadFactory-engine-Thread-22513) [] Exception retriving storage device from vds EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to GetStorageDeviceListVDS, error = Internal JSON-RPC error: {'reason': "'NoneType' object has no attribute 'iface'"}, code = -32603 (Failed with error unexpected and code 16) 2020-11-06 08:29:57,433+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22514) [] FINISH, GetStorageDeviceListVDSCommand, return: [StorageDevice:{id='null', name='ST4000NM0033-9ZM170_Z1Z8JT3C', devUuid='null', fsUuid='null', vdsId='null', description='ST4000NM0033-9ZM (dm-multipath)', devType='ATA', devPath='/dev/mapper/ST4000NM0033-9ZM170_Z1Z8JT3C', fsType='null', mountPoint='null', size='3815447', canCreateBrick='true', isGlusterBrick='false'}, StorageDevice:{id='null', name='gluster_vg_sda', devUuid='9TjMR1-Mk1p-fS6M-w6sP-jEfx-FmPe-A2L5iO', fsUuid='null', vdsId='null', description='lvmvg', devType='ATA', devPath='/dev/gluster_vg_sda', fsType='null', mountPoint='null', size='3815444', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='gluster_vg_sda-gluster_lv_data', devUuid='FuEGn2-BVzA-JDyB-fZPY-BlsU-QYO4-xFVmD0', fsUuid='3d5d228e-ece8-4e59-92ae-c1eb6094e493', vdsId='null', desc ription='lvmthinlv', devType='null', devPath='/dev/mapper/gluster_vg_sda-gluster_lv_data', fsType='xfs', mountPoint='null', size='51200', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='gluster_vg_sda-gluster_lv_engine', devUuid='i2p1Ps-Ix6M-hmJG-VFqJ-2zVE-w14m-71j7KW', fsUuid='6280a49f-f49b-49f6-bc92-139834aae959', vdsId='null', description='lvmlv', devType='null', devPath='/dev/mapper/gluster_vg_sda-gluster_lv_engine', fsType='xfs', mountPoint='null', size='102400', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='gluster_vg_sda-gluster_lv_vmstore', devUuid='DggrnE-C127-U0la-XoyW-eA2w-LOzk-82UmrT', fsUuid='1349ed39-21ed-418a-a2c9-26e67f403d11', vdsId='null', description='lvmthinlv', devType='null', devPath='/dev/mapper/gluster_vg_sda-gluster_lv_vmstore', fsType='xfs', mountPoint='null', size='3225600', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='gluster_vg_sda-gluster_thinpool_glu ster_vg_sda', devUuid='x0Sy1g-WRtr-ZODw-J1il-wJcv-MbKM-Hrfcr9', fsUuid='null', vdsId='null', description='lvmthinpool', devType='null', devPath='/dev/mapper/gluster_vg_sda-gluster_thinpool_gluster_vg_sda', fsType='null', mountPoint='null', size='3680660', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='sda', devUuid='null', fsUuid='fgvWOq-CB7k-qIjJ-iY15-ljEK-aaFG-CvRLQW', vdsId='null', description='ST4000NM0033-9ZM (disk)', devType='ATA', devPath='/dev/sda', fsType='lvmpv', mountPoint='null', size='3815447', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='sdb', devUuid='null', fsUuid='null', vdsId='null', description='ST4000NM0033-9ZM (disk)', devType='ATA', devPath='/dev/sdb', fsType='multipath_member', mountPoint='null', size='3815447', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='sdc', devUuid='null', fsUuid='545ca4c8', vdsId='null', description='Ultra Fit (disk)', devType='USB', devPath='/dev/sdc', fsType='disklabel', mountPoint='null', size='14664', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='sdc1', devUuid='null', fsUuid='null', vdsId='null', description='partition', devType='USB', devPath='/dev/sdc1', fsType='zfs_member', mountPoint='null', size='14663', canCreateBrick='true', isGlusterBrick='false'}], log id: 735f6d30 2020-11-06 08:30:00,403+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetLldpVDSCommand] (default task-71) [474a11f9-ea66-4fd2-bad3-488ce157d197] START, GetLldpVDSCommand(HostName = ovirtn1.5ervers.lan, GetLldpVDSCommandParameters:{hostId='285fc148-62ed-4243-8106-ed01eff28295'}), log id: 66e6c0c1 2020-11-06 08:30:00,522+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetLldpVDSCommand] (default task-71) [474a11f9-ea66-4fd2-bad3-488ce157d197] FINISH, GetLldpVDSCommand, return: {enp0s29u1u1=LldpInfo:{enabled='false', tlvs='[]'}, eno1=LldpInfo:{enabled='false', tlvs='[]'}, enp9s0=LldpInfo:{enabled='true', tlvs='[]'}}, log id: 66e6c0c1 2020-11-06 08:30:05,665+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-75) [] START, GlusterServersListVDSCommand(HostName = ovirtn3.5ervers.lan, VdsIdVDSCommandParametersBase:{hostId='4ec53a62-5cf3-479a-baf5-44c5b7624d39'}), log id: 7f602482 2020-11-06 08:30:05,859+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-75) [] FINISH, GlusterServersListVDSCommand, return: [192.168.4.128/24:CONNECTED, ovirtn2.5ervers.lan:CONNECTED, ovirtn1.5ervers.lan:CONNECTED], log id: 7f602482 2020-11-06 08:30:05,862+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-75) [] START, GlusterVolumesListVDSCommand(HostName = ovirtn3.5ervers.lan, GlusterVolumesListVDSParameters:{hostId='4ec53a62-5cf3-479a-baf5-44c5b7624d39'}), log id: 7f8c7e41 2020-11-06 08:30:05,968+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-75) [] FINISH, GlusterVolumesListVDSCommand, return: {95817a31-0623-44ed-a8bc-d2f37af7644d=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@92ac351e, 03874a87-1e23-4e54-8445-159ba27b48fe=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@25915a3c, 90de405f-60f0-401a-8bdf-7203d8db21f3=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@56a4cd2d}, log id: 7f8c7e41 2020-11-06 08:30:07,416+01 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Before acquiring lock-timeout 'EngineLock:{exclusiveLocks='[HOST_NETWORK285fc148-62ed-4243-8106-ed01eff28295=HOST_NETWORK]', sharedLocks=''}' 2020-11-06 08:30:07,416+01 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Lock-timeout acquired to object 'EngineLock:{exclusiveLocks='[HOST_NETWORK285fc148-62ed-4243-8106-ed01eff28295=HOST_NETWORK]', sharedLocks=''}' 2020-11-06 08:30:07,464+01 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Running command: HostSetupNetworksCommand internal: false. Entities affected : ID: 285fc148-62ed-4243-8106-ed01eff28295 Type: VDSAction group CONFIGURE_HOST_NETWORK with role type ADMIN 2020-11-06 08:30:07,464+01 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Before acquiring lock in order to prevent monitoring for host 'ovirtn1.5ervers.lan' from data-center 'Default' 2020-11-06 08:30:07,464+01 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Lock acquired, from now a monitoring of host will be skipped for host 'ovirtn1.5ervers.lan' from data-center 'Default' 2020-11-06 08:30:07,466+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] START, HostSetupNetworksVDSCommand(HostName = ovirtn1.5ervers.lan, HostSetupNetworksVdsCommandParameters:{hostId='285fc148-62ed-4243-8106-ed01eff28295', vds='Host[ovirtn1.5ervers.lan,285fc148-62ed-4243-8106-ed01eff28295]', rollbackOnFailure='true', commitOnSuccess='true', connectivityTimeout='120', networks='[]', removedNetworks='[]', bonds='[CreateOrUpdateBond:{id='null', name='bond0', bondingOptions='mode=4 miimon=100 xmit_hash_policy=2', slaves='[eno1, enp9s0]'}]', removedBonds='[]', clusterSwitchType='LEGACY', managementNetworkChanged='false'}), log id: 695498c2 2020-11-06 08:30:07,466+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] FINISH, HostSetupNetworksVDSCommand, return: , log id: 695498c2 2020-11-06 08:30:12,118+01 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "Attempt to call function: <bound method Global.getCapabilities of <vdsm.API.Global object at 0x7faebc45cfd0>> with arguments: () error: 'module' object is not callable"}] 2020-11-06 08:30:12,119+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Failed in 'GetCapabilitiesVDS' method 2020-11-06 08:30:12,119+01 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "Attempt to call function: <bound method Global.getCapabilities of <vdsm.API.Global object at 0x7faebc45cfd0>> with arguments: () error: 'module' object is not callable"}] 2020-11-06 08:30:12,164+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirtn1.5ervers.lan command GetCapabilitiesVDS failed: Internal JSON-RPC error: {'reason': "Attempt to call function: <bound method Global.getCapabilities of <vdsm.API.Global object at 0x7faebc45cfd0>> with arguments: () error: 'module' object is not callable"} 2020-11-06 08:30:12,164+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand' return value 'org.ovirt.engine.core.vdsbroker.vdsbroker.VDSInfoReturn@5ccc140e' 2020-11-06 08:30:12,164+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] HostName = ovirtn1.5ervers.lan 2020-11-06 08:30:12,164+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Command 'GetCapabilitiesVDSCommand(HostName = ovirtn1.5ervers.lan, VdsIdAndVdsVDSCommandParametersBase:{hostId='285fc148-62ed-4243-8106-ed01eff28295', vds='Host[ovirtn1.5ervers.lan,285fc148-62ed-4243-8106-ed01eff28295]'})' execution failed: VDSGenericException: VDSErrorException: Failed to GetCapabilitiesVDS, error = Internal JSON-RPC error: {'reason': "Attempt to call function: <bound method Global.getCapabilities of <vdsm.API.Global object at 0x7faebc45cfd0>> with arguments: () error: 'module' object is not callable"}, code = -32603 2020-11-06 08:30:12,165+01 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Host setup networks finished. Lock released. Monitoring can run now for host 'ovirtn1.5ervers.lan' from data-center 'Default' 2020-11-06 08:30:12,165+01 ERROR [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Command 'org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to GetCapabilitiesVDS, error = Internal JSON-RPC error: {'reason': "Attempt to call function: <bound method Global.getCapabilities of <vdsm.API.Global object at 0x7faebc45cfd0>> with arguments: () error: 'module' object is not callable"}, code = -32603 (Failed with error unexpected and code 16) 2020-11-06 08:30:12,222+01 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Lock freed to object 'EngineLock:{exclusiveLocks='[HOST_NETWORK285fc148-62ed-4243-8106-ed01eff28295=HOST_NETWORK]', sharedLocks=''}'

2 10

Issue in importing ISO storage domain in Ovirt 4.3
by hjadavalluva＠ukaachen.de 06 Nov '20

06 Nov '20

Hello, I'm managing Ovirt environment 4.3 and I'm very new to this area. The setup was already done by former colleague and right now I'm managing this environment. Recently, one VM's OS got corrupted and I have to re-install the OS in that VM to bring the VM up and running. For doing this, I need to import the ISO domain from gluster storage (this ISO domain is not present in ovirt engine now). While importing the ISO domain, I face the following error; "Error while executing the action: Cannot add memory connection. Memory connection 63566129-bb20-4b11-b5c2-5e943ab94bed already exists" I already searched this "63566129-bb20-4b11-b5c2-5e943ab94bed" image in ovirt server, target server and gluster storage server but I couldn't find it. Could you please help me in resolving this issue? I got stuck badly here. Thanks in advance! Best Regards, Hariharan

1 0

is there a way to run the cockpit playbooks on the cli ?
by Rob Verduijn 06 Nov '20

06 Nov '20

Hi, For some reason my browser and network like to produce hiccups during the running of the hyperconverge script and the hosted engine install script. ( My prime suspect is Murphy ) This is a default feature in all browsers on any platform. This is why I try to avoid the use of cockpit for complex matters. ( ie anything more complex than proces listing or the viewing of logs ) On the cockpit host, from what directory with which options and what playbook do I need to use to get the same result. Rob

1 1

Fence Agent in Virtual Environment
by jb 05 Nov '20

05 Nov '20

Hello, I would like to build a hyperconverged gluster with hosted engine in a virtual environment, on Fedora 33 with KVM. The setup is for testing purposes, specially for test upgrades before running them on the real physical Servers. But I want to have the setup as close as possible to the real environment, so the only thing is missing is a fence agent. Is there a way to simulate power management in a virtual environment? Jonathan

3 4

Re: Fence Agent in Virtual Environment
by Jonathan Baecker 05 Nov '20

05 Nov '20

Am 05.11.20 um 19:19 schrieb Strahil Nikolov: > You need to enable HA for the VM. Yes this I know and I had this on. When I set the host in maintenance mode, the VM was moving to another host, but not when I kill the host. > About the XVM , I think that you first need to install it on all hosts and then check in UI, if you can find that fence agent in "Power Management". Thanks, I will try this! Best Regard Jonathan > > Best Regards, > Strahil Nikolov > > > > > > > В четвъртък, 5 ноември 2020 г., 18:41:40 Гринуич+2, jb <jonbae77(a)gmail.com> написа: > > > > > > Yes I know, is just a guest... I wanted to test what is happen with a > VM, when I kill it's host. After that, I have not seen that the VM is > moving to another host. > > So I thought maybe ovirt needs the power management for that. > > I have read about fence_xvm, but I don't know how to configure oVirt > with that. > > > > Am 05.11.20 um 17:11 schrieb Strahil Nikolov: >> This is just a guess , but you might be able to install fence_xvm on all Virtualized Hosts . >> >> Best Regards, >> Strahil Nikolov >> >> >> >> >> >> >> В четвъртък, 5 ноември 2020 г., 16:00:40 Гринуич+2, jb <jonbae77(a)gmail.com> написа: >> >> >> >> >> >> Hello, >> >> I would like to build a hyperconverged gluster with hosted engine in a >> virtual environment, on Fedora 33 with KVM. >> >> The setup is for testing purposes, specially for test upgrades before >> running them on the real physical Servers. But I want to have the setup >> as close as possible to the real environment, so the only thing is >> missing is a fence agent. >> >> Is there a way to simulate power management in a virtual environment? >> >> >> Jonathan >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/V5SHGKNLTK24D…

1 0

configuration of hyperconverged setup with ssd cache for slow drives
by Rob Verduijn 05 Nov '20

05 Nov '20

Hello, After a serious struggle I finally managed to get ovirt-hosted engine with the hyperconverged setup to work. However I did not manage to get the ssd cache option for my slow sata drives to work. The installation script complained about mismatching block sizes. Is there a way to make the cockpit hyperconverged installation handle this ? Rob fdisk -l /dev/sda Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes fdisk -l /dev/mapper/gluster_vg_sdc-gluster_lv_data Disk /dev/mapper/gluster_vg_sdc-gluster_lv_data: 4.9 TiB, 5368709120000 bytes, 1310720000 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 1310720 bytes / 2621440 bytes

2 1

[ANN] oVirt 4.4.3 Eighth Release Candidate is now available for testing
by Lev Veyde 05 Nov '20

05 Nov '20

oVirt 4.4.3 Eighth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.3 Eighth Release Candidate for testing, as of November 5th, 2020. This update is the third in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. You can hit: Problem: cannot install the best update candidate for package ovirt-engine-metrics-1.4.1.1-1.el8.noarch - nothing provides rhel-system-roles >= 1.0-19 needed by ovirt-engine-metrics-1.4.2-1.el8.noarch in order to get rhel-system-roles >= 1.0-19 you need https://buildlogs.centos.org/centos/8/virt/x86_64/ovirt-44/ repo since that package can be promoted to release only at 4.4.3 GA. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.3 release highlights: http://www.ovirt.org/release/4.4.3/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.3/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

回复:[ovirt-devel] Re: Host's status how to change to UP when I execute Management--> Active command
by 李伏琼 05 Nov '20

05 Nov '20

thanks very much --------------原始邮件-------------- 发件人："Liran Rotenberg "<lrotenbe(a)redhat.com>; 发送时间：2020年11月5日(星期四) 晚上11:52 收件人："lifuqiong(a)sunyainfo.com" <lifuqiong(a)sunyainfo.com>; 抄送："users "<users(a)ovirt.org>;"devel "<devel(a)ovirt.org>; 主题：[ovirt-devel] Re: Host's status how to change to UP when I execute Management--> Active command ----------------------------------- Hi,The engine will monitor that host. Once it's reachable and we can get information from it the status will change accordingly. Please check out the HostMonitoring class. On Thu, Nov 5, 2020 at 11:57 AM lifuqiong(a)sunyainfo.com <lifuqiong(a)sunyainfo.com> wrote: Hi,      I checkout ovirt-engine's code with branch 4.2;  When execute Host's Management --> Active  command,  ovirt engine just set vds's status to "Unassigned" but how the vds's status changed to "UP" in ovirt-engine?  The code in ActiveVdsCommand.executeCommand() as follows: protected void executeCommand() {         final VDS vds = getVds();         try (EngineLock monitoringLock = acquireMonitorLock("Activate host")) {             executionHandler.updateSpecificActionJobCompleted(vds.getId(), ActionType.MaintenanceVds, false);             setSucceeded(setVdsStatus(VDSStatus.Unassigned).getSucceeded());             if (getSucceeded()) {                 TransactionSupport.executeInNewTransaction(() -> {                     // set network to operational / non-operational                     List<Network> networks = networkDao.getAllForCluster(vds.getClusterId());                     networkClusterHelper.setStatus(vds.getClusterId(), networks);                     return null;                 });                 // Start glusterd service on the node, which would haven been stopped due to maintenance                 if (vds.getClusterSupportsGlusterService()) {                     runVdsCommand(VDSCommandType.ManageGlusterService,                             new GlusterServiceVDSParameters(vds.getId(), Arrays.asList("glusterd"), "restart"));                     // starting vdo service                     GlusterStatus isRunning = glusterUtil.isVDORunning(vds.getId());                     switch (isRunning) {                     case DOWN:                         log.info("VDO service is down in host : '{}' with id '{}', starting VDO service",                                 vds.getHostName(),                                 vds.getId());                         startVDOService(vds);                         break;                     case UP:                         log.info("VDO service is up in host : '{}' with id '{}', skipping starting of VDO service",                                 vds.getHostName(),                                 vds.getId());                            break;                     case UNKNOWN:                         log.info("VDO service is not installed host : '{}' with id '{}', ignoring to start VDO service",                                 vds.getHostName(),                                 vds.getId());                         break;                     }                 }             }         }     } Your Sincerely Mark Lee _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/36745S77NLH3K…

1 0

Re: [ovirt-devel] Host's status how to change to UP when I execute Management--> Active command
by Liran Rotenberg 05 Nov '20

05 Nov '20

Hi, The engine will monitor that host. Once it's reachable and we can get information from it the status will change accordingly. Please check out the HostMonitoring class. On Thu, Nov 5, 2020 at 11:57 AM lifuqiong(a)sunyainfo.com < lifuqiong(a)sunyainfo.com> wrote: > > Hi, > I checkout ovirt-engine's code with branch 4.2; When execute Host's > Management --> Active command, ovirt engine just set vds's status to > "Unassigned" but how the vds's status changed to "UP" in ovirt-engine? The > code in ActiveVdsCommand.executeCommand() as follows: > protected void executeCommand() { > > final VDS vds = getVds(); > try (EngineLock monitoringLock = acquireMonitorLock("Activate > host")) { > executionHandler.updateSpecificActionJobCompleted(vds.getId(), > ActionType.MaintenanceVds, false); > > setSucceeded(setVdsStatus(VDSStatus.Unassigned).getSucceeded()); > > if (getSucceeded()) { > TransactionSupport.executeInNewTransaction(() -> { > // set network to operational / non-operational > List<Network> networks = > networkDao.getAllForCluster(vds.getClusterId()); > networkClusterHelper.setStatus(vds.getClusterId(), > networks); > return null; > }); > > // Start glusterd service on the node, which would haven > been stopped due to maintenance > if (vds.getClusterSupportsGlusterService()) { > runVdsCommand(VDSCommandType.ManageGlusterService, > new GlusterServiceVDSParameters(vds.getId(), > Arrays.asList("glusterd"), "restart")); > // starting vdo service > GlusterStatus isRunning = > glusterUtil.isVDORunning(vds.getId()); > switch (isRunning) { > case DOWN: > log.info("VDO service is down in host : '{}' with > id '{}', starting VDO service", > vds.getHostName(), > vds.getId()); > startVDOService(vds); > break; > case UP: > log.info("VDO service is up in host : '{}' with > id '{}', skipping starting of VDO service", > vds.getHostName(), > vds.getId()); > break; > case UNKNOWN: > log.info("VDO service is not installed host : > '{}' with id '{}', ignoring to start VDO service", > vds.getHostName(), > vds.getId()); > break; > } > > } > } > } > } > > > Your Sincerely > Mark Lee > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/36745S77NLH3K… >

1 0

Affinity Group Graceful Migration
by thilburn＠generalpacific.com 05 Nov '20

05 Nov '20

Hello, I'm trying to get an Affinity Group setup that will gracefully remove VMs from a Host. Below is what I've tried but the VMs will not migrate off. oVirt 4.3 Priority: 1 VM Affinity Rule: Disabled Host Affinity Rule: Negative ( Soft ) Virtual Machines: Select a VM ( My understanding is this would mean all VMs? ) Hosts: Host: <Name of host> Also, is this right place to ask for help on this?

2 1

Coffee Lake CPU
by jb 05 Nov '20

05 Nov '20

Hello, sorry there comes many questions today from me! I plan a new cluster setup, and for that I bought ASUS Barebone with Intel Xeon E-2246G CPUs. Sadly I pay not enough attention to the system requirements from oVirt and now I say that theCoffee Lake-ER architecture is not in the supported CPU list from oVirt. Is there any downsides with using a Coffee Lake CPU? Jonathan

1 0

locked disk making it impossible to remove vm
by igor.lustosa＠hybriddc.com.br 05 Nov '20

05 Nov '20

I have a vm that has two disks one active and another disabling when trying to migrate the disk to another storage the task was in a loop creating several snapshots, I turned off the VM and the loop stopped and after several hours the task disappeared and the VM disk was left blocking making it impossible to be deleted and when trying to delete the vm it does not exclude from the following message locked disk making it impossible to remove vm How can I solve this?

2 3

VM Struck in Shutdown Mode
by Andrei Verovski 05 Nov '20

05 Nov '20

Hi, I have oVirt 4.4 engine and v4.2 nodes. On one node newly created VM struck in shutdown mode (with green round recycle icon) - I can’t anything, neither power off neither shutdown, both operation fail (with no explanation). This VM have no value whatsoever, but I can’t delete it either. Restarted oVirt engine, all same. Process list (on node) clearly shows absence of this VM as KVM process. VM is down. How to reset its status in oVirt? Thanks in advance. Andrei

2 3

enabling BaseOS repo in oVirt Node 4.4
by jb 05 Nov '20

05 Nov '20

Hello everybody, is it a problem to enable the BaseOS on a oVirt Node? I ask, because I would like to install nano 😁... I could just disable it again, after installation, but what can happen when it stays enabled? Jonathan

1 0

Host's status how to change to UP when I execute Management--> Active command
by lifuqiong＠sunyainfo.com 05 Nov '20

05 Nov '20

Hi, I checkout ovirt-engine's code with branch 4.2; When execute Host's Management --> Active command, ovirt engine just set vds's status to "Unassigned" but how the vds's status changed to "UP" in ovirt-engine? The code in ActiveVdsCommand.executeCommand() as follows: protected void executeCommand() { final VDS vds = getVds(); try (EngineLock monitoringLock = acquireMonitorLock("Activate host")) { executionHandler.updateSpecificActionJobCompleted(vds.getId(), ActionType.MaintenanceVds, false); setSucceeded(setVdsStatus(VDSStatus.Unassigned).getSucceeded()); if (getSucceeded()) { TransactionSupport.executeInNewTransaction(() -> { // set network to operational / non-operational List<Network> networks = networkDao.getAllForCluster(vds.getClusterId()); networkClusterHelper.setStatus(vds.getClusterId(), networks); return null; }); // Start glusterd service on the node, which would haven been stopped due to maintenance if (vds.getClusterSupportsGlusterService()) { runVdsCommand(VDSCommandType.ManageGlusterService, new GlusterServiceVDSParameters(vds.getId(), Arrays.asList("glusterd"), "restart")); // starting vdo service GlusterStatus isRunning = glusterUtil.isVDORunning(vds.getId()); switch (isRunning) { case DOWN: log.info("VDO service is down in host : '{}' with id '{}', starting VDO service", vds.getHostName(), vds.getId()); startVDOService(vds); break; case UP: log.info("VDO service is up in host : '{}' with id '{}', skipping starting of VDO service", vds.getHostName(), vds.getId()); break; case UNKNOWN: log.info("VDO service is not installed host : '{}' with id '{}', ignoring to start VDO service", vds.getHostName(), vds.getId()); break; } } } } } Your Sincerely Mark Lee

1 0

20+ Fresh Installs Failing in 20+ days [newbie & frustrated]
by info＠worldhostess.com 05 Nov '20

05 Nov '20

I have no idea if it is Hardware or Software. It crashed every time after it starts with the storage setup Error in ovirt-hosted-engine-setup-ansilble-setup-final_clean [FAILED] DESTROYED LOCAL STORAGE-POOL HTTPS --- "certificate invalid" The system is very unstable and impossible to do anything remotely ONLY accessible on local terminal. This is my hardware SuperMicro X11SSF-M Intel Xeon E3-1230 16 GB ECC RAM 2 x 1 TB Micron 1300 SSD Key Features X11SSM-F specifications Single socket H4 (LGA 1151) supports IntelR XeonR processor E3-1200 v6/v5, IntelR 7th/6th Gen. CoreT i3 series, IntelR CeleronR and IntelR PentiumR IntelR C236 chipset Up to 64GB Unbuffered ECC UDIMM DDR4 2400MHz; 4 DIMM slots Expansion slots: 1 PCI-E 3.0 x8 (in x16), 1 PCI-E 3.0 x8, 2 PCI-E 3.0 x4 (in x8) Dual GbE LAN with IntelR i210-AT 8 SATA3 (6Gbps) via C236; RAID 0, 1, 5, 10 I/O: 1 VGA, 2 COM, 2 SuperDOM, and TPM header 5 USB 3.0 (2 rear, 2 via header(s), 1 Type A), 6 USB 2.0 (2 rear, 4 via header(s)) Integrated IPMI 2.0 and KVM with Dedicated LAN Yours Sincerely, Henni

6 38

lose my server ovirt-engine in network
by garcialiang.anne＠gmail.com 05 Nov '20

05 Nov '20

Hello, I installed my ovirt-engine during 1 month. I can connect with ssh or website. Yesterday, I rebooted my server ovirt-engine. But I can't connect it with ssh. My server lost in network. I can login with the machine, but I can't ping with network. Is there the problem with network setting ? Could you help me, please? Thanks, Anne Garcia

1 0

Removal of dpdk
by Ales Musil 04 Nov '20

04 Nov '20

Hello, we have decided to remove dpdk in the upcoming version of oVirt namely 4.4.4. Let us know if there are any concerns about this. Thank you. Regards, Ales Musil -- Ales Musil Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

4 6

Requesting for a help in resolving ovirt self hosted engine installation issue
by Jadavalluvar Sethuraman, Hariharan 04 Nov '20

04 Nov '20

Hello, Good Day! I'm Hariharan and I'm working as System Administrator in Linux platform for RWTH Uniklink - Germany. Currently I'm managing the Ovirt environment and I'm very new to this domain. Currently I'm facing an issue with Ovirt self hosted engine installation 4.4 in CentOS 8 server. I have an issue when mounting the glusterfs storage to a target machine. Below is the exact issue what I face; Error: "changed": false, "msg": "Error: the target storage domain contains only 22.0GiB of available space while a minimum of 61.0GiB is required If you wish to use the current target storage domain by extending it, make sure it contains nothing before adding it. Note: (gluster storage was installed and configured in Linux work station with adding additional hard disk in one of the two gluster storage linux work station. I used replicated volumes (replica 2) in creating gluster volumes) Hardware detail: device model: Dell R540 Capacity: 240 GB I tried best possibilities to resolve this issue but still I'm facing the same issue. Could you please help me in resolving this issue with your guidance or support. Hariharan Jadavalluvar Sethuraman Systemadministrator der Brain Imaging Facility (BIF) des interdisziplinären Zentrums für klinische Forschung (IZKF) Universitätsklinikum Aachen (AöR) Pauwelsstraße 30 52074 Aachen Tel: +49 241 80-89150 E-Mail: hjadavalluva(a)ukaachen.de<mailto:rrodriguez@ukaachen.de> ________________________________

1 0

Ovirt 4.4 ilo_ssh version HP ILO3. ERROR: Unable to connect/login to fencing device
by melnyksergii＠gmail.com 04 Nov '20

04 Nov '20

Dears, I have a 3 nodes with HP blade servers G7 and ILO3. ILO3 with the latest firmware 1.93 from Aug 07 2020. I'm try to migrate from Ovirt 4.3 to 4.4 with Centos 8, but I had a problem with setup ssh ilo fence on this nodes. In Ovirt 4.3 with Centos 7 all is works. When I try to Test fence, I see ERROR: Unable to connect/login to fencing device. When I try to use /usr/sbin/fence_ilo_ssh I see the same error. So, I know where is a problem. The problem in an old ssh security keys HostKeyAlgorithms=+ssh-dss. When I add to /root/.ssh/config some exclude for use HostKeyAlgorithms=+ssh-dss I can connect to ilo over ssh from root with: /usr/sbin/fence_ilo_ssh -a 10.0.11.157 -l user -p passwordh -x -u 22 --login-timeout=10 -o status and see: Status: ON But when I try again setup ilo_ssh fence in Ovirt-engine UI I still have the same ERROR: Unable to connect/login to fencing device. How can I solve this problem in Ovirt? Thanks

1 1

HCI with 5 node quest
by simon＠justconnect.ie 03 Nov '20

03 Nov '20

I have a 3 node HCI setup with 2 Replica 3 volumes using nodes 1, 2 & 3 and have added 2 additional Compute nodes to this Cluster. What is stopping me from adding nodes 4 & 5 as Gluster Peers and creating a glusterfs Replica 3 Volume using nodes 3, 4 & 5? Shimme

3 4

ovirt glusterfs
by garcialiang.anne＠gmail.com 03 Nov '20

03 Nov '20

Hello, I've some problem with Hyperconverged Configure Gluster storage and oVirt hosted engine. I've the message error: failed: [node2.xxxxx.fr] (item={u'key': u'gluster_vg_sdb', u'value': [{u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}]}) => {"ansible_loop_var": "item", "changed": false, "err": " Device /dev/sdb excluded by a filter.\n", "item": {"key": "gluster_vg_sdb", "value": [{"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}]}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5} Could you help me for know where is the problem, please? Thanks, Anne Garcia

4 3

POWER9 (ppc64le) Support on oVirt 4.4.1
by Vinícius Ferrão 03 Nov '20

03 Nov '20

Hello, I was using oVirt 4.3.10 with IBM AC922 (POWER9 / ppc64le) without any issues. Since I’ve moved to 4.4.1 I can’t add the AC922 machine to the engine anymore, it complains with the following error: The host CPU does not match the Cluster CPU type and is running in degraded mode. It is missing the following CPU flags: model_POWER9, powernv. Any ideia of what’s may be happening? The engine runs on x86_64, and I was using this way on 4.3.10. Machine info: timebase : 512000000 platform : PowerNV model : 8335-GTH machine : PowerNV 8335-GTH firmware : OPAL MMU : Radix Thanks,

3 18

Re: Migrate hosted-engine to new storage domain
by Yedidyah Bar David 03 Nov '20

03 Nov '20

On Tue, Nov 3, 2020 at 7:07 AM Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> wrote: > > I’ve migrated my iSCSI storage to a new array, and the only thing remaining is to migrate the hosted-engine. > > > > Any directions on how I should proceed. I understand that I will need to back-up the existing, create a new hosted-engine on the new storage, specifying the backup a reference. > > > > I just would like to see a step-by-step, so I know I am doing everything, and in the right order. Generally speaking, you should follow the hosted-engine backup and restore flows/documents. I strongly suggest to test this first on a test machine before production. You can take a backup without downtime. Restore on some machine (can be a VM, with nested-kvm) that has no access to your production storage and hosts (to make sure the restored engine won't start managing them/competing with the production one). See that all looks good. Then plan production... Good luck and best regards, -- Didi

1 0

Migrate hosted-engine to new storage domain
by Matthew.Stier＠fujitsu.com 03 Nov '20

03 Nov '20

I've migrated my iSCSI storage to a new array, and the only thing remaining is to migrate the hosted-engine. Any directions on how I should proceed. I understand that I will need to back-up the existing, create a new hosted-engine on the new storage, specifying the backup a reference. I just would like to see a step-by-step, so I know I am doing everything, and in the right order.

1 0

Select host for image upload
by C Williams 02 Nov '20

02 Nov '20

Hello, I am having problems selecting the host that I want to use for .iso and other image uploads via the oVirt Web Console. I have 20+ servers of varying speeds. Somehow oVirt keeps wanting to select my oldest and slowest system to use for image uploads. Please Help ! Thank You ! C Williams

2 3

Q: Failed creating snapshot
by Andrei Verovski 02 Nov '20

02 Nov '20

Hi, I have oVirt 4.4 with nodes 4.2.8 Attempt to create snapshot failed with: EventID 10802 VDSM node11 command SnapshotVDS failed: Message timeout can be caused by communication issues. Event ID 2022 Add-disk operation failed to complete. However, snapshot is on disk since VM now takes 1200GB instead of 500. Yes snapshot list in VM details is empty. How to recover disk space occupied by unsuccessful snapshot ? I looked at /vmraid/nfs/disks/xxxx-xxxx-xxx/images and there are no distinctive files which I can identify as snapshot. Thanks in advance. Andrei

2 1

ovirt installation with proxy or katello
by Markus Schaufler 02 Nov '20

02 Nov '20

Hi, in our environment we need to either specify proxy settings or use foreman/katello repositories. I'd like to test both ways but the installer with the ansible scripts behind don't seem to use the hosts settings. Where do I have to adopt the install scripts and will there be in future a GUI option to specify those things? Can't understand why disconnected environments or environments with proxies aren't better taken into consideration...? Thanks in advance, Markus

1 0

Question about OVN MTU
by Strahil Nikolov 02 Nov '20

02 Nov '20

Hello All, I would like to learn more about OVN and especially the maximum MTU that I can use in my environment. Current Setup 4.3.10 Network was created via UI -> MTU Custom -> 8976 -> Create on External Provider -> Connect to Physical Network So my physical connection is MTU 9000 and I have read that Geneve uses 24 bits (maybe that's wrong ?) , thus I have reduced the MTU to 8976. I did some testing on the VMs and ping with payload of '8914' was the maximum I could pass without fragmenting and thus the MTU on the VMs was set to 8942. Did I correctly configure the test network's MTU and am I understanding it correctly that we need extra 34 bits inside the network for encapsulation ? I have checked https://www.ovirt.org/develop/release-management/features/network/managed_m… but I don't see any refference how to calculate the max MTU. Best Regards, Strahil Nikolov

3 8

different rendering chrome and firefox and corruptions in both
by Gianluca Cecchi 01 Nov '20

01 Nov '20

Hello, I'm using Fedora 31 with google-chrome-stable-86.0.4240.111-1.x86_64 firefox-82.0-4.fc31.x86_64 Engine was deployed from a CentOS Linux 8.2 host and then with hosted engine wizard, using the appliance rpm (Package ovirt-engine-appliance.x86_64 4.4-20200916125954.1.el8) Connecting to the same 4.4.2 engine I get: 1) different landing page graphics firefox: https://drive.google.com/file/d/142Ch7qXmmIP9sQQCS1rD75yexX64RmSu/view?usp=… chrome: https://drive.google.com/file/d/1KPvlNk65ltIBhr8GFdVm-GMtfq1Elt7J/view?usp=… 2) corruption in several editing pages in firefox, where a sort of top white part seems to compromise the lower part of the window, making impossible to complete. eg in new network I don't see the lower part related to MTU...: https://drive.google.com/file/d/18aQfDbl_9R9oQsTMwebJSiRZHETkUWIc/view?usp=… 3) in Stotrage --> volumes page if I click on a volume, firefox shows no problem, but chrome gives a gui exception: https://drive.google.com/file/d/1svzQjrGctRMQFvZEpW9zpOlUbv8XXl3Q/view?usp=… Gianluca

2 1

Discard after Delete
by Joris DEDIEU 01 Nov '20

01 Nov '20

Hi list, I forgot to check "Discard after Delete" when creating a new volume. Is there a way (other than to empty the volume) to reclaim free blocks. In https://bugzilla.redhat.com/show_bug.cgi?id=981626 I read about blkdiscard, but as far as I understand it will erase my VMs ... Thanks for your answers Joris

4 4

Training Video or document or training session
by info＠worldhostess.com 01 Nov '20

01 Nov '20

Can someone recommend a training video of some kind of step by step document to do the installation and administration for OVirt? Or if someone that wants to do a one on one online training? I would be super excited to do online training. I have been trying many time to install and I am sure I make some mistakes because I can't get OVirt to work properly. I have done numerous installations during the last few weeks. Yours Sincerely, Henni

4 3