August 2020 - Users - oVirt List Archives

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

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 18 Jul '23

18 Jul '23

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

4 6

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 27 Feb '23

27 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

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

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

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

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 10 Dec '20

10 Dec '20

7 14

"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

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

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

hosted engine migration
by 董青龙 22 Sep '20

22 Sep '20

Hi all, I have an ovirt4.3.10.4 environment of 2 hosts. Normal vms in this environment could be migrated, but the hosted engine vm could not be migrated. Anyone can help? Thanks a lot! hosts status: normal vm migration: hosted engine vm migration:

4 27

iSCSI multipath issue
by Nick Kas 08 Sep '20

08 Sep '20

Hello evryone, setup ovirt 4.4.1 on CentOS 8.2 as an experiment, and I am trying to get an iSCSI domain working but have issues. The little experimental cluster has 3 hosts. There is an ovirtmgmt network on the default vlan, and two iSCSI network (172.27.0/1.X) with vlans 20/21. ovirtmgmt has all the functions (Data, display, migration etc), and the iSCSI networks nothing yet, and they are not set as required. The SAN device is already serving a few iSCSI volumes to a vmware cluster, so I know things are fine on this end. It has two controllers, and four NICs per controller so a total of 8 NICs, half of the NICS per controller on 172.27.0.X and half on 172.27.1.X. When I create the iSCSI domain, I login to only one of the targets, and add the Volume, all is good and I can use the disc fine. However when I login to more than one of the targets, then I start having issues with the Volume. Even when I enabled multipath in the cluster, and I created a single multipath by selecting both of the 172.27.0/1.X networks, and all the targets, the end result was the same. The hosts have difficulty accessing the volume, they may even swing between 'non-operational' and 'up' if I transfer data to the volume. When I ssh to the hosts and i check things in the command line I also get inconsistent results between hosts, and blocks that appear with lsblk when I first setup iSCSI have dissapeared after I try to actively use the volume. I am new to iSCSI so I am not sure how to debug this. I am not sure if my multipath configuration is correct or not. The documentation on this part was not very detailed. I also tried to remove the domain, and try to experiment with mounting the iSCSI volume from the command line, but I cannot even discover the target from the command line, which is very bizarre. The command iscsiadm --mode discovery --target sendtargets --portal 172.27.0.55 --discover returns the message 'iscsiadm: cannot make connection to 172.27.0.55: No route to host'. Yet through ovirt, and if I select only one target, everything work fine! Any suggestions on how to start debugging this would really be appreciated.

2 3

How to Backup a VM
by Stefan Wolf 03 Sep '20

03 Sep '20

Hello to all I try to backup a normal VM. But It seems that I don't really understand the concept. At first I found the possibility to backup with the api https://www.ovirt.org/documentation/administration_guide/#Setting_a_storage…. Create a snapshot of the VM, finding the ID of the snapshot and the configuration of the VM makes sense to me. But at this point, I would download the config an the snapshot and put it to my backup storage. And not create a new VM attach the disk and run a backup with backup programm. And for restoring do the sam way backwards. If i look at other project, there seems do be a way to download the snapshot and configfile, or am I wrong? Maybe someone can explain to me why I should use additional software to install in an additional machine. Or even better someone can explain to me how I don't have to use additional backup software. And to the same topic backup. There is in the documentation the possibility to set up a backup storage It is nearly the same, create a snapshot, or clone the machine and export it to backup storage > Export the new virtual machine to a backup domain. See Exporting a Virtual Machine to a Data Domain in the Virtual Machine Management Guide. Sadly there is just writen what to do, not how, the link points to 404 page. maybe someone can explain to me how to use backup storage thank you very much shb

5 15

How can Gluster be a HCI default, when it's hardly ever working?
by thomas＠hoberg.net 02 Sep '20

02 Sep '20

I've just tried to verify what you said here. As a base line I started with the 1nHCI Gluster setup. From four VMs, two legacy, two Q35 on the single node Gluster, one survived the import, one failed silently with an empty disk, two failed somewhere in the middle of qemu-img trying to write the image to the Gluster storage. For each of those two, this always happened at the same block number, a unique one per machine, not in random places, as if qemu-img reading and writing the very same image could not agree. That's two types of error and a 75% failure rate I created another domain, basically using an NFS automount export from one of the HCI nodes (a 4.3 node serving as 4.4 storage) and imported the very same VMs (source all 4.3) transported via a re-attached export domain to 4.4. Three of the for imports worked fine, no error with qemu-img writing to NFS. All VMs had full disk images and launched, which verified that there is nothing wrong with the exports at least. But there was still one, that failed with the same qemu-img error. I then tried to move the disks from NFS to Gluster, which internally is also done via qemu-img, and I had those fail every time. Gluster or HCI seems a bit of a Russian roulette for migrations, and I am wondering how much it is better for normal operations. I'm still going to try moving via a backup domain (on NFS) and moving between that and Gluster, to see if it makes any difference. I really haven't done a lot of stress testing yet with oVirt, but this experience doesn't build confidence.

2 2

HP blade G7, with be2net.
by Remulo 01 Sep '20

01 Sep '20

Hello I have some blades with 10GE interface that have / need the Emulex be2net driver, however it is no longer available on Redhat8 / Centos8. Is there any way to install ovirt to work on these machines? Here are some links to problems with Redhat. Emulex NIC using be2net driver https://access.redhat.com/solutions/1229853 https://access.redhat.com/solutions/514353 I did a lot of research and couldn't get a functional driver for ovirt. Thank you. -- Atenciosamente, Rêmulo Ferreira.

3 2

Problem installing Windows VM on 4.4.1
by fgarat＠gmail.com 01 Sep '20

01 Sep '20

Hi, I'm having problem after I upgraded to 4.4.1 with Windows machines. The installation sees no disk. Even IDE disk doesn't get detected and installation won't move forward no matter what driver i use for the disk. Any one else having this issue?. Regards, Facundo

4 3

How can you avoid breaking 4.3.11 legacy VMs imported in 4.4.1 during a migration?
by thomas＠hoberg.net 01 Sep '20

01 Sep '20

Testing the 4.3 to 4.4 migration... what I describe here is facts is mostly observations and conjecture, could be wrong, just makes writing easier... While 4.3 seems to maintain a default emulated machine type (pc-i440fx-rhel7.6.0 by default), it doesn't actually allow setting it in the cluster settings: Could be built-in, could be inherited from the default template... Most of my VMs were created with the default on 4.3. oVirt 4.4 presets that to pc-q35-rhel8.1.0 and that has implications: 1. Any VM imported from an export on a 4.3 farm, will get upgraded to Q35, which unfortunately breaks things, e.g. network adapters getting renamed as the first issue I stumbled on some Debian machines 2. If you try to compensate by lowering the cluster default from Q35 to pc-i44fx the hosted-engine will fail, because it was either built or came as Q35 and can no longer find critical devices: It evidently doesn't take/use the VM configuration data it had at the last shutdown, but seems to re-generate it according to some obscure logic, which fails here. I've tried creating a bit of backward compatibility by creating another template based on pc-i440fx, but at the time of the import, I cannot switch the template. If I try to downgrade the cluster, the hosted-engine will fail to start and I can't change the template of the hosted-engine to something Q35. Currently this leaves me in a position where I can't separate the move of VMs from 4.3 to 4.4 and the upgrade of the virtual hardware, which is a different mess for every OS in the mix of VMs. Recommendations, tips anyone? P.S. A hypervisor reconstructing the virtual hardware from anywhere but storage at every launch, is difficult to trust IMHO.

3 6

Upgrade Doc typo.
by carl langlois 01 Sep '20

01 Sep '20

Hi, Not sure if this is relevant but in the ovirt doc in the 4.2 to 4.3 upgrade the repo rpm is specified with 4,4 rpm . Thanks Carl [image: image.png]

2 2

Re: Promiscuous Mode
by thomas＠hoberg.net 31 Aug '20

31 Aug '20

Not sure it will actually do that, but if you create a new network profile, you can select a 'port mirroring' option: It is my understanding that is what you need. You may also want to deselect the filtering rules in the same place.

1 0

can't mount an export domain with 4K block size (VDO) as PosixFS (xfs)
by thomas＠hoberg.net 31 Aug '20

31 Aug '20

After this (https://devconfcz2020a.sched.com/event/YOtG/ovirt-4k-teaching-an-old-dog-ne…) I sure do not expect this (log below): Actually I am trying to evaluate just how portable oVirt storage is and this case I had prepared a USB3 HDD with VDO, which I could literally move between farms to transport VMs. Logical disks are typically large for simplicity within the VMs, QCOW2 and VDO assumed to compensate for this 'lack of planning' while the allocated storage easily fits the HDD. Once I got beyond the initial issues, I came across this somewhat unexpected issue: VDO storage uses 4k blocks all around, but evidently when you mount an export domain (or I guess any domain) as POSIX, 512byte blocks are assumed somewhere and 4k blocks rejected. I'd say that is a bug in VDSM, right? Or is there anything in the mount options to fix this? 020-08-31 18:44:40,424+0200 INFO (periodic/0) [vdsm.api] START repoStats(domains=()) from=internal, task_id=7a293dec-85b3-4b82-92b7-4e7d03b40343 (api:48) 2020-08-31 18:44:40,425+0200 INFO (periodic/0) [vdsm.api] FINISH repoStats return={'9992dc21-edf2-4951-9020-7c78f1220e02': {'code': 0, 'lastCheck': '1.6', 'delay': '0.00283651', 'valid': True, 'version': 5, 'acquired': True, 'actual': True}, '25d95783-44df-4fda-b642-55fe09162149': {'code': 0, 'lastCheck': '2.2', 'delay': '0.00256944', 'valid': True, 'version': 5, 'acquired': True, 'actual': True}, '148d9e9e-d7b8-4220-9ee8-057da96e608c': {'code': 0, 'lastCheck': '2.2', 'delay': '0.00050217', 'valid': True, 'version': 5, 'acquired': True, 'actual': True}} from=internal, task_id=7a293dec-85b3-4b82-92b7-4e7d03b40343 (api:54) 2020-08-31 18:44:41,121+0200 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312) 2020-08-31 18:44:41,412+0200 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312) 2020-08-31 18:44:41,414+0200 INFO (jsonrpc/2) [vdsm.api] START repoStats(domains=['9992dc21-edf2-4951-9020-7c78f1220e02']) from=::1,44782, task_id=657c820e-e2eb-4b1d-b2fb-1772b3af6f32 (api:48) 2020-08-31 18:44:41,414+0200 INFO (jsonrpc/2) [vdsm.api] FINISH repoStats return={'9992dc21-edf2-4951-9020-7c78f1220e02': {'code': 0, 'lastCheck': '2.6', 'delay': '0.00283651', 'valid': True, 'version': 5, 'acquired': True, 'actual': True}} from=::1,44782, task_id=657c820e-e2eb-4b1d-b2fb-1772b3af6f32 (api:54) 2020-08-31 18:44:41,414+0200 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call Host.getStorageRepoStats succeeded in 0.00 seconds (__init__:312) 2020-08-31 18:44:41,965+0200 INFO (jsonrpc/3) [IOProcessClient] (Global) Starting client (__init__:308) 2020-08-31 18:44:41,984+0200 INFO (ioprocess/87332) [IOProcess] (Global) Starting ioprocess (__init__:434) 2020-08-31 18:44:42,006+0200 INFO (jsonrpc/3) [storage.StorageDomainCache] Removing domain fe9fb0db-2743-457a-80f0-9a4edc509e9d from storage domain cache (sdc:211) 2020-08-31 18:44:42,006+0200 INFO (jsonrpc/3) [storage.StorageDomainCache] Invalidating storage domain cache (sdc:74) 2020-08-31 18:44:42,006+0200 INFO (jsonrpc/3) [vdsm.api] FINISH connectStorageServer return={'statuslist': [{'id': '00000000-0000-0000-0000-000000000000', 'status': 0}]} from=::ffff:192.168.0.87,40378, flow_id=05fe72ef-c8ac-4e03-8453-5171e5fc5f8b, task_id=b92d4144-a9db-4423-ba6b-35934d4f9200 (api:54) 2020-08-31 18:44:42,008+0200 INFO (jsonrpc/3) [jsonrpc.JsonRpcServer] RPC call StoragePool.connectStorageServer succeeded in 3.11 seconds (__init__:312) 2020-08-31 18:44:42,063+0200 INFO (jsonrpc/5) [vdsm.api] START getStorageDomainsList(spUUID='00000000-0000-0000-0000-000000000000', domainClass=3, storageType='', remotePath='/dev/mapper/vdo1', options=None) from=::ffff:192.168.0.87,40378, flow_id=eff548f9-b663-45dd-b8a5-5854f9b5dde8, task_id=98ca66a5-edee-40d4-9253-6a46409241cc (api:48) 2020-08-31 18:44:42,063+0200 INFO (jsonrpc/5) [storage.StorageDomainCache] Refreshing storage domain cache (resize=True) (sdc:80) 2020-08-31 18:44:42,063+0200 INFO (jsonrpc/5) [storage.ISCSI] Scanning iSCSI devices (iscsi:442) 2020-08-31 18:44:42,101+0200 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312) 2020-08-31 18:44:42,128+0200 INFO (jsonrpc/5) [storage.ISCSI] Scanning iSCSI devices: 0.06 seconds (utils:390) 2020-08-31 18:44:42,129+0200 INFO (jsonrpc/5) [storage.HBA] Scanning FC devices (hba:60) 2020-08-31 18:44:42,182+0200 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312) 2020-08-31 18:44:42,184+0200 INFO (jsonrpc/4) [vdsm.api] START repoStats(domains=['9992dc21-edf2-4951-9020-7c78f1220e02']) from=::1,44782, task_id=7b3f1eb8-f7e3-4467-93a1-27ef9721c90c (api:48) 2020-08-31 18:44:42,184+0200 INFO (jsonrpc/4) [vdsm.api] FINISH repoStats return={'9992dc21-edf2-4951-9020-7c78f1220e02': {'code': 0, 'lastCheck': '3.4', 'delay': '0.00283651', 'valid': True, 'version': 5, 'acquired': True, 'actual': True}} from=::1,44782, task_id=7b3f1eb8-f7e3-4467-93a1-27ef9721c90c (api:54) 2020-08-31 18:44:42,184+0200 INFO (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC call Host.getStorageRepoStats succeeded in 0.00 seconds (__init__:312) 2020-08-31 18:44:42,277+0200 INFO (jsonrpc/5) [storage.HBA] Scanning FC devices: 0.15 seconds (utils:390) 2020-08-31 18:44:42,309+0200 INFO (jsonrpc/5) [storage.Multipath] Resizing multipath devices (multipath:104) 2020-08-31 18:44:42,312+0200 INFO (jsonrpc/5) [storage.Multipath] Resizing multipath devices: 0.00 seconds (utils:390) 2020-08-31 18:44:42,312+0200 INFO (jsonrpc/5) [storage.StorageDomainCache] Refreshing storage domain cache: 0.25 seconds (utils:390) 2020-08-31 18:44:42,418+0200 INFO (tmap-569/0) [IOProcessClient] (_dev_mapper_vdo1) Starting client (__init__:308) 2020-08-31 18:44:42,445+0200 INFO (tmap-569/1) [IOProcessClient] (glusterSD/nucvirt.mtk.hoberg.net:_data) Starting client (__init__:308) 2020-08-31 18:44:42,449+0200 INFO (ioprocess/87496) [IOProcess] (_dev_mapper_vdo1) Starting ioprocess (__init__:434) 2020-08-31 18:44:42,457+0200 INFO (tmap-569/2) [IOProcessClient] (glusterSD/nucvirt.mtk.hoberg.net:_vmstore) Starting client (__init__:308) 2020-08-31 18:44:42,465+0200 INFO (ioprocess/87508) [IOProcess] (glusterSD/nucvirt.mtk.hoberg.net:_data) Starting ioprocess (__init__:434) 2020-08-31 18:44:42,478+0200 INFO (tmap-569/3) [IOProcessClient] (glusterSD/nucvirt.mtk.hoberg.net:_engine) Starting client (__init__:308) 2020-08-31 18:44:42,486+0200 INFO (ioprocess/87516) [IOProcess] (glusterSD/nucvirt.mtk.hoberg.net:_vmstore) Starting ioprocess (__init__:434) 2020-08-31 18:44:42,514+0200 INFO (ioprocess/87533) [IOProcess] (glusterSD/nucvirt.mtk.hoberg.net:_engine) Starting ioprocess (__init__:434) 2020-08-31 18:44:42,522+0200 INFO (jsonrpc/5) [IOProcessClient] (fe9fb0db-2743-457a-80f0-9a4edc509e9d) Starting client (__init__:308) 2020-08-31 18:44:42,553+0200 INFO (ioprocess/87552) [IOProcess] (fe9fb0db-2743-457a-80f0-9a4edc509e9d) Starting ioprocess (__init__:434) 2020-08-31 18:44:42,582+0200 ERROR (jsonrpc/5) [storage.HSM] Unexpected error (hsm:2843) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 2829, in getStorageDomainsList dom = sdCache.produce(sdUUID=sdUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 115, in produce domain.getRealDomain() File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 51, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 139, in _realProduce domain = self._findDomain(sdUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 156, in _findDomain return findMethod(sdUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/nfsSD.py", line 146, in findDomain return NfsStorageDomain(NfsStorageDomain.findDomainPath(sdUUID)) File "/usr/lib/python3.6/site-packages/vdsm/storage/fileSD.py", line 390, in __init__ manifest.block_size, storage_block_size) File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 939, in _validate_storage_block_size raise se.StorageDomainBlockSizeMismatch(block_size, storage_block_size) vdsm.storage.exception.StorageDomainBlockSizeMismatch: Block size does not match storage block size: 'block_size=512, storage_block_size=4096' 2020-08-31 18:44:42,582+0200 INFO (jsonrpc/5) [vdsm.api] FINISH getStorageDomainsList return={'domlist': []} from=::ffff:192.168.0.87,40378, flow_id=eff548f9-b663-45dd-b8a5-5854f9b5dde8, task_id=98ca66a5-edee-40d4-9253-6a46409241cc (api:54) 2020-08-31 18:44:42,582+0200 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call Host.getStorageDomains succeeded in 0.52 seconds (__init__:312) 2020-08-31 18:44:42,801+0200 INFO (jsonrpc/7) [vdsm.api] START disconnectStorageServer(domType=6, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'password': '********', 'vfs_type': 'xfs', 'port': '', 'mnt_options': 'rw,relatime,seclabel,attr2,inode64,noquota,_netdev,x-systemd.device-timeout=0', 'iqn': '', 'connection': '/dev/mapper/vdo1', 'ipv6_enabled': 'false', 'id': 'b4a73d6a-344c-446b-a33d-7b665e78578d', 'user': '', 'tpgt': '1'}], options=None) from=::ffff:192.168.0.87,40378, flow_id=6678917a-b29c-416c-aa2d-5abc1d5351a3, task_id=3d0cf36e-427d-4000-8857-a8a2af641b10 (api:48) 2020-08-31 18:44:42,801+0200 INFO (jsonrpc/7) [storage.Mount] unmounting /rhev/data-center/mnt/_dev_mapper_vdo1 (mount:215) 2020-08-31 18:44:42,806+0200 INFO (jsonrpc/0) [vdsm.api] START disconnectStorageServer(domType=6, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'password': '********', 'vfs_type': 'xfs', 'port': '', 'mnt_options': 'rw,relatime,seclabel,attr2,inode64,noquota,_netdev,x-systemd.device-timeout=0', 'iqn': '', 'connection': '/dev/mapper/vdo1', 'ipv6_enabled': 'false', 'id': 'b4a73d6a-344c-446b-a33d-7b665e78578d', 'user': '', 'tpgt': '1'}], options=None) from=::ffff:192.168.0.87,40378, flow_id=bb449405-5b78-4b65-a352-e2e94a269df9, task_id=09783e0a-933c-448d-b0ca-1b5d351eb042 (api:48) 2020-08-31 18:44:42,806+0200 INFO (jsonrpc/0) [storage.Mount] unmounting /rhev/data-center/mnt/_dev_mapper_vdo1 (mount:215) 2020-08-31 18:44:42,821+0200 ERROR (jsonrpc/0) [storage.HSM] Could not disconnect from storageServer (hsm:2528) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 2524, in disconnectStorageServer conObj.disconnect() File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 201, in disconnect self._mount.umount(True, True) File "/usr/lib/python3.6/site-packages/vdsm/storage/mount.py", line 217, in umount umount(self.fs_file, force=force, lazy=lazy, freeloop=freeloop) File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ return callMethod() File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda> **kwargs) File "<string>", line 2, in umount File "/usr/lib64/python3.6/multiprocessing/managers.py", line 772, in _callmethod raise convert_to_error(kind, result) vdsm.storage.mount.MountError: Command ['/usr/bin/umount', '-f', '-l', '/rhev/data-center/mnt/_dev_mapper_vdo1'] failed with rc=32 out=b'' err=b'umount: /rhev/data-center/mnt/_dev_mapper_vdo1: not mounted.\n' 2020-08-31 18:44:42,821+0200 INFO (jsonrpc/0) [storage.StorageDomainCache] Refreshing storage domain cache (resize=False) (sdc:80)

2 2

Promiscuous Mode
by Anton Louw 31 Aug '20

31 Aug '20

Hi All, I would like to deploy a VM that will monitor a specific network. I know in VMware you can set the port group to allow Promiscuous Mode. Is there something similar I can do in oVirt? 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

1 0

Error exporting into ova
by Gianluca Cecchi 31 Aug '20

31 Aug '20

Hello, I'm playing with export_vm_as_ova.py downloaded from the examples github: https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/export_v… My environment is oVirt 4.3.3.7 with iSCSI storage domain. It fails leaving an ova.tmp file In webadmin gui: Starting to export Vm enginecopy1 as a Virtual Appliance 7/19/1911:55:12 AM VDSM ov301 command TeardownImageVDS failed: Cannot deactivate Logical Volume: ('General Storage Exception: ("5 [] [\' Logical volume fa33df49-b09d-4f86-9719-ede649542c21/0420ef47-0ad0-4cf9-babd-d89383f7536b in use.\']\\nfa33df49-b09d-4f86-9719-ede649542c21/[\'a7480dc5-b5ca-4cb3-986d-77bc12165be4\', \'0420ef47-0ad0-4cf9-babd-d89383f7536b\']",)',) 7/19/1912:25:36 PM Failed to export Vm enginecopy1 as a Virtual Appliance to path /save_ova/base/dump/myvm2.ova on Host ov301 7/19/1912:25:37 PM During export I have this qemu-img process creating the disk over the loop device: root 30878 30871 0 11:55 pts/2 00:00:00 su -p -c qemu-img convert -T none -O qcow2 '/rhev/data-center/mnt/blockSD/fa33df49-b09d-4f86-9719-ede649542c21/images/59a4a324-4c99-4ff5-abb1-e9bbac83292a/0420ef47-0ad0-4cf9-babd-d89383f7536b' '/dev/loop1' vdsm vdsm 30882 30878 10 11:55 ? 00:00:00 qemu-img convert -T none -O qcow2 /rhev/data-center/mnt/blockSD/fa33df49-b09d-4f86-9719-ede649542c21/images/59a4a324-4c99-4ff5-abb1-e9bbac83292a/0420ef47-0ad0-4cf9-babd-d89383f7536b /dev/loop1 The ova.tmp file is getting filled while command runs eg: [root@ov301 ]# du -sh /save_ova/base/dump/myvm2.ova.tmp 416M /save_ova/base/dump/myvm2.ova.tmp [root@ov301 sysctl.d]# [root@ov301 sysctl.d]# du -sh /save_ova/base/dump/myvm2.ova.tmp 911M /save_ova/base/dump/myvm2.ova.tmp [root@ov301 ]# and the final generated / not completed file is in this state: [root@ov301 ]# qemu-img info /save_ova/base/dump/myvm2.ova.tmp image: /save_ova/base/dump/myvm2.ova.tmp file format: raw virtual size: 30G (32217446400 bytes) disk size: 30G [root@ov301 sysctl.d]# But I notice that the timestamp of the file is about 67 minutes after start of job and well after the notice of its failure.... [root@ov301 sysctl.d]# ll /save_ova/base/dump/ total 30963632 -rw-------. 1 root root 32217446400 Jul 19 13:02 myvm2.ova.tmp [root@ov301 sysctl.d]# [root@ov301 sysctl.d]# du -sh /save_ova/base/dump/myvm2.ova.tmp 30G /save_ova/base/dump/myvm2.ova.tmp [root@ov301 sysctl.d]# In engine.log the first error I see is 30 minutes after start 2019-07-19 12:25:31,563+02 ERROR [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-engineScheduled-Thread-64) [2001ddf4] Ansible playbook execution failed: Timeout occurred while executing Ansible playbook. 2019-07-19 12:25:31,563+02 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-engineScheduled-Thread-64) [2001ddf4] Ansible playbook command has exited with value: 1 2019-07-19 12:25:31,564+02 ERROR [org.ovirt.engine.core.bll.CreateOvaCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-64) [2001ddf4] Failed to create OVA. Please check logs for more details: /var/log/ovirt-engine/ova/ovirt-export-ova-ansible-20190719115531-ov301-2001ddf4.log 2019-07-19 12:25:31,565+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.TeardownImageVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-64) [2001ddf4] START, TeardownImageVDSCommand(HostName = ov301, ImageActionsVDSCommandParameters:{hostId='8ef1ce6f-4e38-486c-b3a4-58235f1f1d06'}), log id: 3d2246f7 2019-07-19 12:25:36,569+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-64) [2001ddf4] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ov301 command TeardownImageVDS failed: Cannot deactivate Logical Volume: ('General Storage Exception: ("5 [] [\' Logical volume fa33df49-b09d-4f86-9719-ede649542c21/0420ef47-0ad0-4cf9-babd-d89383f7536b in use.\']\\nfa33df49-b09d-4f86-9719-ede649542c21/[\'a7480dc5-b5ca-4cb3-986d-77bc12165be4\', \'0420ef47-0ad0-4cf9-babd-d89383f7536b\']",)',) In ansible playbook suggested log file I don't see anything useful. It ends with timestamps when the script has been launched. Last lines are: 2019-07-19 11:55:33,877 p=5699 u=ovirt | TASK [ovirt-ova-export-pre-pack : Retrieving the temporary path for the OVA file] *** 2019-07-19 11:55:34,198 p=5699 u=ovirt | changed: [ov301] => { "changed": true, "dest": "/save_ova/base/dump/myvm2.ova.tmp", "gid": 0, "group": "root", "mode": "0600", "owner": "root", "secontext": "system_u:object_r:nfs_t:s0", "size": 32217446912, "state": "file", "uid": 0 } 2019-07-19 11:55:34,204 p=5699 u=ovirt | TASK [ovirt-ova-pack : Run packing script] ************************************* It seems 30 minutes... for timeout? About what, ansible job? Or possibly implicit user session created when running the python script? The snapshot has been correctly deleted (as I see also in engine.log), I don't see it in webadmin gui. Any known problem? Just for test I executed again at 14:24 and I see same Ansible error at 14:54 The snapshot gets deleted, while the qemu-img command still continues.... [root@ov301 sysctl.d]# ps -ef | grep qemu-img root 13504 13501 0 14:24 pts/1 00:00:00 su -p -c qemu-img convert -T none -O qcow2 '/rhev/data-center/mnt/blockSD/fa33df49-b09d-4f86-9719-ede649542c21/images/59a4a324-4c99-4ff5-abb1-e9bbac83292a/0420ef47-0ad0-4cf9-babd-d89383f7536b' '/dev/loop0' vdsm vdsm 13505 13504 3 14:24 ? 00:01:26 qemu-img convert -T none -O qcow2 /rhev/data-center/mnt/blockSD/fa33df49-b09d-4f86-9719-ede649542c21/images/59a4a324-4c99-4ff5-abb1-e9bbac83292a/0420ef47-0ad0-4cf9-babd-d89383f7536b /dev/loop0 root 17587 24530 0 15:05 pts/0 00:00:00 grep --color=auto qemu-img [root@ov301 sysctl.d]# [root@ov301 sysctl.d]# du -sh /save_ova/base/dump/myvm2.ova.tmp 24G /save_ova/base/dump/myvm2.ova.tmp [root@ov301 sysctl.d]# ll /save_ova/base/dump/myvm2.ova.tmp -rw-------. 1 root root 32217446400 Jul 19 15:14 /save_ova/base/dump/myvm2.ova.tmp [root@ov301 sysctl.d]# and then continues until image copy completes, but at this time the job has already aborted and so the completion of the ova composition doesn't go ahead... and I remain with the ova.tmp file... How to extend timeout? Thanks in advance, Gianluca

4 11

Hosted Engine stuck in Firmware
by Vinícius Ferrão 30 Aug '20

30 Aug '20

Hello, I’ve an strange issue with oVirt 4.4.1 The hosted engine is stuck in the UEFI firmware trying to “never” boot. I think this happened when I changed the default VM mode for the cluster inside the datacenter. There’s a way to fix this without redeploying the engine?

3 3

deprecating export domain?
by Charles Kozler 30 Aug '20

30 Aug '20

Hello, I recently read on this list from a redhat member that export domain is either being deprecated or looking at being deprecated To that end, can you share details? Can you share any notes/postings/bz's that document this? I would imagine something like this would be discussed in larger audience This seems like a somewhat significant change to make and I am curious where this is scheduled? Currently, a lot of my backups rely explicitly on an export domain for online snapshots, so I'd like to plan accordingly Thanks!

11 21

shutdown virtual machine did not display in the list when using virsh list --all and virsh list --state-shutoff
by Kyre 30 Aug '20

30 Aug '20

Hello, I am using ovirt 4.3.8. I want to use the virsh command to boot the shutdown virtual machine, but when using virsh list --all and virsh list --state-shutoff, the shutdown virtual machine did not display in the list. What is the cause of this, and how can I display the shutdown virtual machine. virsh # list --all Please enter your authentication name: root Please enter your password:  Id    Name                           State ----------------------------------------------------  4     win10E2                  running virsh # list --state-shutoff  Id    Name                           State ----------------------------------------------------

4 3

Ovirt Node 4.4.2 Engine Deployment - Notification Settings
by David White 30 Aug '20

30 Aug '20

I finally got oVirt node installed with gluster on a single node. So that's great progress! Once that step was complete... I noticed that the Engine Deployment wizard asks for SMTP settings for where to send notifications. I was kind of surprised that it doesn't allow one to enter any credentials. It looks like this requires an unauthenticated local relay. I don't like that. :) See attached screenshot. Has there been any talk about adding this into the wizard deployment? Sent with ProtonMail Secure Email.

2 1

i/o wait and slow system
by info＠dsdm.ch 29 Aug '20

29 Aug '20

Hello, I'm running a home setup with 3 nodes and 2 SATA SSDs per node. As storage I'm running glusterfs and 40GBit/s links. Software Version:4.3.9.4-1.el7 I've a lot of I/O Wait on the nodes (20%) and on the VMs (50%). gluster volume top vmstore write-perf bs 2014 count 1024 | grep Through Throughput 635.54 MBps time 0.0032 secs Throughput 614.89 MBps time 0.0034 secs Throughput 622.31 MBps time 0.0033 secs Throughput 643.07 MBps time 0.0032 secs Throughput 621.75 MBps time 0.0033 secs Throughput 609.26 MBps time 0.0034 secs gluster volume top vmstore read-perf bs 2014 count 1024 | grep Through Throughput 1274.62 MBps time 0.0016 secs Throughput 1320.32 MBps time 0.0016 secs Throughput 1203.93 MBps time 0.0017 secs Throughput 1293.81 MBps time 0.0016 secs Throughput 1213.14 MBps time 0.0017 secs Throughput 1193.48 MBps time 0.0017 secs Volume Name: vmstore Type: Distributed-Replicate Volume ID: 195e2a05-9667-4b8b-b0b7-82294631de50 Status: Started Snapshot Count: 0 Number of Bricks: 2 x 3 = 6 Transport-type: tcp Bricks: Brick1: 10.9.9.101:/gluster_bricks/vmstore/vmstore Brick2: 10.9.9.102:/gluster_bricks/vmstore/vmstore Brick3: 10.9.9.103:/gluster_bricks/vmstore/vmstore Brick4: 10.9.9.101:/gluster_bricks/S4CYNF0M219849L/S4CYNF0M219849L Brick5: 10.9.9.102:/gluster_bricks/S4CYNF0M219836L/S4CYNF0M219836L Brick6: 10.9.9.103:/gluster_bricks/S4CYNF0M219801Y/S4CYNF0M219801Y Options Reconfigured: performance.client-io-threads: on nfs.disable: on transport.address-family: inet performance.strict-o-direct: on performance.quick-read: off performance.read-ahead: off performance.io-cache: off performance.low-prio-threads: 32 network.remote-dio: off cluster.eager-lock: enable cluster.quorum-type: auto cluster.server-quorum-type: server cluster.data-self-heal-algorithm: full cluster.locking-scheme: granular cluster.shd-max-threads: 8 cluster.shd-wait-qlength: 10000 features.shard: on user.cifs: off cluster.choose-local: off client.event-threads: 4 server.event-threads: 4 network.ping-timeout: 30 storage.owner-uid: 36 storage.owner-gid: 36 cluster.granular-entry-heal: enable Please help me to analyse the root cause. Many thanks Metz

4 14

Missing model_FLAGS on specific host
by Vinícius Ferrão 28 Aug '20

28 Aug '20

Hi, I’ve an strange issue in one of my hosts, it’s missing a lot of CPU flags that oVirt seems to require: [root@c4140 ~]# vdsm-client Host getCapabilities | egrep "cpuFlags|cpuModel" "cpuFlags": "ssse3,mca,ept,pdpe1gb,vmx,clwb,smep,msr,acpi,pge,sse4_2,nopl,cqm_mbm_total,cx16,avx512vl,aperfmperf,xsaves,3dnowprefetch,nonstop_tsc,cmov,mce,intel_pt,avx512f,fpu,pku,tsc,sdbg,erms,pse36,md_clear,apic,sse,pcid,clflushopt,xtopology,pts,monitor,vpid,cpuid,hle,mba,ss,cqm,avx2,ibpb,xgetbv1,flush_l1d,mmx,epb,pti,fxsr,dca,nx,syscall,stibp,mtrr,cx8,sse2,avx,sep,intel_ppin,lm,tm,bts,adx,bmi1,smx,popcnt,pclmulqdq,lahf_lm,mpx,rdseed,cqm_llc,avx512cd,cdp_l3,f16c,invpcid,fsgsbase,cpuid_fault,tm2,smap,dts,pse,xsave,sse4_1,constant_tsc,pat,tsc_deadline_timer,vnmi,avx512dq,dtes64,xsaveopt,ida,pdcm,tpr_shadow,pln,de,x2apic,avx512bw,pae,rdrand,clflush,rdtscp,art,cqm_mbm_local,pebs,ssbd,movbe,pbe,tsc_adjust,vme,ht,est,bmi2,cat_l3,dtherm,ospke,rdt_a,aes,ibrs,rep_good,fma,xtpr,ds_cpl,abm,xsavec,invpcid_single,flexpriority,cqm_occup_llc,pni,rtm,arat,arch_perfmon", "cpuModel": "Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz", In a properly working host it have flags like those ones: model_Westmere-IBRS,model_kvm32,model_core2duo,model_Opteron_G1,model_Broadwell,model_qemu64,model_Broadwell-noTSX,model_Nehalem-IBRS,model_Haswell-IBRS,model_pentium2,model_Broadwell-IBRS,model_Haswell-noTSX,model_Haswell,model_Haswell-noTSX-IBRS,model_Conroe,model_pentium,model_n270,model_Nehalem,model_IvyBridge-IBRS,model_kvm64,model_SandyBridge,model_pentium3,model_Broadwell-noTSX-IBRS,model_qemu32,model_486,model_IvyBridge,model_SandyBridge-IBRS,model_Westmere,model_Penryn,model_Opteron_G2,model_coreduo", But in this machine it’s totally missing. I know this model_ flags are an oVirt thing, since they aren’t default on the CPUs. The host machine is a Dell C4140 compute node, the firmware is fully updated, so I’ve done the basic to figure out what’s happening. Thanks,

1 1

ovirt 4.4 self-hosted deployment questions
by Michael Thomas 28 Aug '20

28 Aug '20

I have not been able to find answers to a couple of questions in the self-hosted engine documentation[1]. * When installing a new Enterprise Linux host for ovirt, what are the network requirements? Specifically, am I supposed to set up the ovirtmgmt bridge myself on new hosts, or am I supposed to let that be handled by the engine when I add the new host to the engine? * In the 'New Host' dialog on the engine management page, does the Hostname/IP that I enter have to be the host's name on the ovirtmgmt LAN? If so, then it seems to me that I need to configure the ovirtmgmt bridge myself on new hosts. * Does the engine need to be able to route outside of the cluster (eg to the WAN), or is it allowed to restrict the engine's routing to the local cluster? * In the 'New Host' dialog on the engine management page, what is the meaning of 'Choose hosted engine deployment action'? From the way it is phrased, it sounds like this will create a second engine in my cluster, which doesn't make sense. Or does this mean that the new host will be able to run the Engine VM in a HA manner? In my current test deployment I have 3 subnets in my cluster. Network WAN is the WAN. Network CLUSTER is for communication between cluster compute nodes, storage servers, and management servers. Network OVIRT is for ovirt management and VM migration between hosts. My first self-hosted engine host is connected to networks CLUSTER and OVIRT. The engine VM is only connected to network OVIRT through a bridge on the host, but has a gateway that lets it route traffic to network CLUSTER (but not network WAN). Is this an appropriate network setup for ovirt, or should there be no distinction between the CLUSTER and OVIRT networks? --Mike [1]https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_eng…

2 1

Gluster Volume Type Distributed
by Dominique Deschênes 28 Aug '20

28 Aug '20

Hi Everyone, I would like to use Distrbuted Volume type but the volume type is Gray out. I can only use the replicate type. It's normal ? 3 ovirt Servers 4.4.1-2020080418 Can I configure a replicate volume for the engine domain and Distributed for the data domain? Thank you Dominique Deschênes Ingénieur chargé de projets, Responsable TI 816, boulevard Guimond, Longueuil J4G 1T5 450 670-8383 x105 450 670-2259

4 3

Failed to connect to the hypervisor
by Eugène Ngontang 28 Aug '20

28 Aug '20

Hi, I'm facing a strange issue with ovirt host. I can't list nodes status running virsh, vdsdm seems bad. I can't even delete the hosted engine, nor ping it, but I can still access my infra vm inside it[image: 😉] My outputs : > [root@moe ~]# /usr/sbin/ovirt-hosted-engine-cleanup > This will de-configure the host to run ovirt-hosted-engine-setup from > scratch. > Caution, this operation should be used with care. > Are you sure you want to proceed? [y/n] > y > -=== Destroy hosted-engine VM ===- > You must run deploy first > setlocale: No such file or directory > error: failed to connect to the hypervisor > error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No > such file or directory > -=== Stop HA services ===- > -=== Shutdown sanlock ===- > shutdown force 1 wait 0 > shutdown done -111 > -=== Disconnecting the hosted-engine storage domain ===- > You must run deploy first > -=== De-configure VDSM networks ===- > ovirtmgmt > ovirtmgmt > A previously configured management bridge has been found on the system, > this will try to de-configure it. Under certain circumstances you can loose > network connection. > Caution, this operation should be used with care. > Are you sure you want to proceed? [y/n] > y > -=== Stop other services ===- > -=== De-configure external daemons ===- > -=== Removing configuration files ===- > ? /etc/init/libvirtd.conf already missing > ? /etc/libvirt/nwfilter/vdsm-no-mac-spoofing.xml already missing > ? /etc/ovirt-hosted-engine/answers.conf already missing > ? /etc/ovirt-hosted-engine/hosted-engine.conf already missing > ? /etc/vdsm/vdsm.conf already missing > ? /etc/pki/vdsm/*/*.pem already missing > ? /etc/pki/CA/cacert.pem already missing > ? /etc/pki/libvirt/*.pem already missing > ? /etc/pki/libvirt/private/*.pem already missing > ? /etc/pki/ovirt-vmconsole/*.pem already missing > ? /var/cache/libvirt/* already missing > ? /var/run/ovirt-hosted-engine-ha/* already missing > [root@moe ~]# ping 192.168.33.143 > PING 192.168.33.143 (192.168.33.143) 56(84) bytes of data. > 64 bytes from 192.168.33.143: icmp_seq=1 ttl=64 time=0.132 ms > 64 bytes from 192.168.33.143: icmp_seq=2 ttl=64 time=0.082 ms > 64 bytes from 192.168.33.143: icmp_seq=3 ttl=64 time=0.072 ms > 64 bytes from 192.168.33.143: icmp_seq=4 ttl=64 time=0.083 ms > 64 bytes from 192.168.33.143: icmp_seq=5 ttl=64 time=0.075 ms > 64 bytes from 192.168.33.143: icmp_seq=6 ttl=64 time=0.082 ms > ^C > --- 192.168.33.143 ping statistics --- > 6 packets transmitted, 6 received, 0% packet loss, time 4999ms > rtt min/avg/max/mdev = 0.072/0.087/0.132/0.022 ms > [root@moe ~]# nodectl check > Status: WARN > Bootloader ... OK > Layer boot entries ... OK > Valid boot entries ... OK > Mount points ... OK > Separate /var ... OK > Discard is used ... OK > Basic storage ... OK > Initialized VG ... OK > Initialized Thin Pool ... OK > Initialized LVs ... OK > Thin storage ... OK > Checking available space in thinpool ... OK > Checking thinpool auto-extend ... OK > vdsmd ... BAD > [root@moe ~]# virsh -r list > setlocale: No such file or directory > error: failed to connect to the hypervisor > error: Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': No > such file or directory > [root@moe ~]# Have you guys ever faced this issue? How can I access VM inside my virtual data center while the VM Manager is broken? Any solution to work around this please? Regards, Eugène NG -- LesCDN <http://lescdn.com> engontang(a)lescdn.com ------------------------------------------------------------ *Aux hommes il faut un chef, et au* * chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te voit on te juge!*

1 0

Compatibilty issue
by carl langlois 28 Aug '20

28 Aug '20

Hi, I have upgraded ovirt to 4.3 and now I have some vm that I can start because of the cluster compatibility version. Those VM where in save state when I updated the cluster compatibility version. Now they are in a down state but if i try to run it I get this message. Cannot run VM. The Custom Compatibility Version of VM vmfpgatest (4.2) is not supported in Data Center compatibility version 4.3. any suggestions? Regards Carl

1 0

TroubleshootingoVirt Node deploy FQDN not reachable
by David White 27 Aug '20

27 Aug '20

In a recent thread, Roberto mentioned seeing the error message "FQDN Not Reachable" when trying to deploy oVirt Node 4.4.1, but was able to get past that error when using ovirt-node-ng-installer-4.4.2-2020080612.el8.iso. I experienced the same problems on oVirt Node install 4.4.1, so I tried the latest release of 4.4.2. When that failed, I went back and installed from the exact same image as Roberto said worked on the 4.4.2 branch: ovirt-node-ng-installer-4.4.2-2020080612.el8.iso Unfortunately, that's still not working for me - so that tells me I'm probably doing something wrong. Given the following facts: [root@dev1-centos ~]# hostname dev1-centos.office.barredowlweb.com [root@dev1-centos ~]# host dev1-centos.office.barredowlweb.com dev1-centos.office.barredowlweb.com has address 192.168.2.96 I am trying to install oVirt using the Hyperconverged Gluster Wizard for a Single Node. In the "Host1" box, I enter the full hostname: dev1-centos.office.barredowlweb.com And that's when I get the FQDN error message. Am I missing something here? Sent with ProtonMail Secure Email.

4 5

Is the Hosted Engine setup finished + Can't connect vdsm storage
by Bielej SRE 27 Aug '20

27 Aug '20

Hi, We have 6 node oVirt setup with Compatibility version 4.3 running on CentOS 7.6.1810 Recently We have found out some very interesting log entries on a few of our nodes. /var/log/ovirt-hosted-engine-ha/broker.log: MainThread::INFO::2020-08-27 12:51:50,279::storage_backends::345::ovirt_hosted_engine_ha.lib.storage_backends::(connect) Connecting the storage MainThread::INFO::2020-08-27 12:51:50,280::storage_server::349::ovirt_hosted_engine_ha.lib.storage_server.StorageServer::(connect_storage_server) Connecting storage server MainThread::warning::2020-08-27 12:51:50,284::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: 'NoneType' object has no attribute 'startswith' /var/log/messages Aug 27 12:52:11 ildeco25 vdsm[6909]: ERROR failed to retrieve Hosted Engine HA score '[Errno 2] No such file or directory'Is the Hosted Engine setup finished? We have inherited that setup from the previous team but I'm fairly certain the the Hosted Engine setup is finished. Also, this line is not present on all hosts. Should We worry about ovirt-ha-broker service not running on some hosts? host24 Active: inactive (dead) host25 Active: failed (Result: start-limit) since Thu 2020-08-27 12:56:13 CEST; 2s ago host26 Active: active (running) since Sun 2020-08-23 22:55:01 CEST; 3 days ago host27 Active: inactive (dead) host28 Active: failed (Result: start-limit) since Thu 2020-08-27 12:56:18 CEST; 4s ago host29 Active: inactive (dead) Currently the hosted engine VM is running on host26. I'd be very grateful for any help. Kind regards, Michal Bielejewski

2 1

Impossible to install Windows VMs on 4.4.1
by fgarat＠gmail.com 27 Aug '20

27 Aug '20

Hi, I'm having problem after I upgraded to 4.4.1 with Windows machines. The installation sees no disk. Even IDE disk doesn't get detected and installation won't move forward no matter what driver i use for the disk. Any one else having this issue?. Regards, Facundo

3 4

Host has no default route
by Wesley Stewart 27 Aug '20

27 Aug '20

I am trying to add a host to a single host cluster. Everything has gone pretty well so far, except when the host gets to the end of the installation process, I see an exclamation mark indicating "Host has no default route". The installation "finishes" and the host goes into a non-responsive state. I am not really sure where to check. I get a: host *name* installation has failed. Network error during communication with host. Running 4.3.6 Thanks!

2 1

[ANN] oVirt 4.4.2 Fifth Release Candidate is now available for testing
by Lev Veyde 27 Aug '20

27 Aug '20

oVirt 4.4.2 Fifth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.2 Fifth Release Candidate for testing, as of August 27th, 2020. This update is the second in a series of stabilization updates to the 4.4 series. 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.2 release highlights: http://www.ovirt.org/release/4.4.2/ * 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.2/ [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>

3 3

LDAP/AD issue
by kim.kargaard＠noroff.no 26 Aug '20

26 Aug '20

Hi all, We have had our ovirt instance connected to our internal AD for users to log into the VM portal for the last year, linked to studentdomene.noroff.no. This has been working without any problems. We had it set up and the DNS server had a forward record to the DC's. All good. Then, of course, the institution decided to introduce student emails and they decided to add the domain stud.noroff.no for student emails and made this the primary domain in the AD. The problem is that when this is changed, students can no longer log into the engine. I have of course changed the ldap settings and added a forward record on the DNS to the new domain. However, it seems that the domain is studentdomene.noroff.no, but with an added UPN suffix with stud.noroff.no When students try to log in, with the config changes, they get this error in the browser: server_error: An error occurred while attempting to query DNS in order to retrieve SRV records with name '_ldap._tcp.stud.noroff.no': NameNotFoundException(DNS name not found [response code 3]), ldapSDKVersion=4.0.7, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58 Any ideas on how to solve this issue? My config looks like this: sudo cat /etc/ovirt-engine/aaa/Students.properties [sudo] password for noroffadmin: include = <ad.properties> vars.domain = studentdomene.noroff.no vars.user = CN=ovirt auth,CN=Users,DC=stud,DC=noroff,DC=no vars.password = PASSWORD pool.default.auth.simple.bindDN = ${global:vars.user} pool.default.auth.simple.password = ${global:vars.password} pool.default.serverset.type = srvrecord pool.default.serverset.srvrecord.domain = ${global:vars.domain} my forward on the DNS server looks like this: sudo cat /etc/named/named.conf.local [sudo] password for noroffadmin: zone "platform.noroff.no"{ type master; file "/etc/named/zones/db.platform.noroff.no"; # zone file path }; zone "stud.noroff.no" { type forward; forward only; forwarders { 172.24.111.20; 172.27.111.20; 172.21.111.20; 172.16.111.20; }; }; zone "studentdomene.noroff.no" { type forward; forward only; forwarders { 172.24.111.20; 172.27.111.20; 172.21.111.20; 172.16.111.20; }; }; zone "122.16.172.in-addr.arpa" { type master; file "/etc/named/zones/db.122.16.172"; # 172.16.122.0/24 subnet }; Any pointers would be greatly appreciated :) Kim

2 1

oVirt SHE smart-automated backup
by Vrgotic, Marko 26 Aug '20

26 Aug '20

Dear oVirt, For a while now I have been running backup of oVirt engine via ansible. And that works just fine. However, its still recommended, in SHE HA environment, especially for Restore purpose to have one of HA nodes in Maintenance mode, clean from Virtual load. Has anyone so far been able to automate oVirt engine backup in following or similar way: 1. Register on which HA node is SHE atm 2. Pick the other HA node to go into maintenance mode – in order to have one of HA nodes without virtual load 3. Verify it’s in maintenance mode 4. Execute engine-backup 5. Remove the maintenance mode of the node from step 2 Even if you are half way through, I would be happy to get involved and contribute. Kindly awaiting your reply. ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo 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.

2 4

oVirt HCI 4.4.1 DR cannot import target volume after disaster
by wodel youchi 25 Aug '20

25 Aug '20

Hi, I have installed two HCI platforms. Then I set up the disaster-recovery configuration On source platform I did : # gluster volume set all cluster.enable-shared-storage enable # gluster system:: execute gsec_create # gluster volume geo-replication *source* gnodesen2-01.example.com::dest create push-pem # gluster volume geo-replication *source* gnodesen2-01.example.com::dest config use_meta_volume true On target platform I did : # gluster volume set *dest* features.shard enable I then realized these two tests : *1 - Sync data using the schedule_georep.py* a - Use the : "python3 /usr/share/glusterfs/scripts/schedule_georep.py source gnodesen2-01.example.com dest " command to sync data between the volumes b - After the sync is complete, execute "gluster volume dest set features.read-only off" c - Execute *import* (not create) *dest* volume on the target platform manually through the Admin-UI, Result : The domain could not be added and I get this error on vdsm log : " 2020-08-24 10:18:05,644+0100 ERROR (jsonrpc/5) [storage.HSM] Unexpected error (hsm:2843) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 456, in getVersion version = self.getMetaParam(DMDK_VERSION) File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 452, in getMetaParam return self._metadata[key] File "/usr/lib/python3.6/site-packages/vdsm/storage/persistent.py", line 114, in __getitem__ return dec(self._dict[key]) File "/usr/lib/python3.6/site-packages/vdsm/storage/persistent.py", line 225, in __getitem__ return self._metadata[key] KeyError: 'VERSION' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 2829, in getStorageDomainsList dom = sdCache.produce(sdUUID=sdUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 115, in produce domain.getRealDomain() File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 51, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 139, in _realProduce domain = self._findDomain(sdUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/sdc.py", line 156, in _findDomain return findMethod(sdUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/glusterSD.py", line 62, in findDomain return GlusterStorageDomain(GlusterStorageDomain.findDomainPath(sdUUID)) File "/usr/lib/python3.6/site-packages/vdsm/storage/fileSD.py", line 385, in __init__ manifest = self.manifestClass(domainPath) File "/usr/lib/python3.6/site-packages/vdsm/storage/fileSD.py", line 162, in __init__ sd.StorageDomainManifest.__init__(self, sdUUID, domaindir, metadata) File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 352, in __init__ version = self.getVersion() * File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 458, in getVersion raise se.MetaDataKeyNotFoundError("key={}".format(DMDK_VERSION))vdsm.storage.exception.MetaDataKeyNotFoundError: Meta Data key not found error: ('key=VERSION',)* 2020-08-24 10:18:05,644+0100 INFO (jsonrpc/5) [vdsm.api] FINISH getStorageDomainsList return={'domlist': []} from=::ffff:10.80.101.27,48282, flow_id=5209d576-ee09-4de3-bc46-0c186c6ad52a, task_id=bc93aaae-5449-4d0d-9884-f47ea542a963 (api:54) 2020-08-24 10:18:05,645+0100 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call Host.getStorageDomains succeeded in 3.01 seconds (__init__:312) 2020-08-24 10:18:05,754+0100 INFO (jsonrpc/4) [vdsm.api] START disconnectStorageServer(domType=7, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'password': '********', 'vfs_type': 'glusterfs', 'port': '', 'mnt_options': 'backup-volfile-servers=10.90.101.23:10.90.101.25', 'iqn': '', 'connection': '10.90.101.21:/dest', 'ipv6_enabled': 'false', 'id': 'cc24df41-19b0-41ed-ae85-e091e40cc612', 'user': '', 'tpgt': '1'}], options=None) from=::ffff:10.80.101.27,48282, flow_id=5fcaf7d7-d3b6-4430-b5f9-28e6bd95656a, task_id=73654a43-c86b-4250-95d7-3e3399e5bc72 (api:48) 2020-08-24 10:18:05,754+0100 INFO (jsonrpc/4) [storage.Mount] unmounting /rhev/data-center/mnt/glusterSD/10.90.101.21:_dest (mount:215) " *Note :* I had to modify the line 105 from /usr/share/glusterfs/scripts/schedule_georep.py to be able to use it with python3 : - ey = "_".join([func.func_name] + list(args)) + key = "_".join([func.__name__] + list(args)) *2 - Sync data using the adminUI :* a - Create a schedule on the adminUI and wait until the sync is complete. b - Switch off read-only on target volume : gluster volume set dest features.read-only off (on the target volume) c - Execute ansible failover scripts : ansible-playbook dr-rhv-failover.yml --tags="fail_over" command (on the ansible machine) Result : 020-08-24 15:51:58,874+0100 INFO (jsonrpc/0) [IOProcessClient] (3a5d378b-8043-4072-9c58-e838343d6028) Starting client (init:308) 2020-08-24 15:51:58,886+0100 INFO (ioprocess/140212) [IOProcess] (3a5d378b-8043-4072-9c58-e838343d6028) Starting ioprocess (init:434) 2020-08-24 15:51:58,888+0100 INFO (jsonrpc/0)** [vdsm.api] FINISH createStorageDomain error=Storage domain is not empty - requires cleaning: ('gnodesen2-01.example.com:/dest',) from=::ffff:10.80.101.27,45118, flow_id=765c5009, task_id=ed3a34f9-5e81-40f4-a592-78e585c1f937 (api:52) 2020-08-24 15:51:58,888+0100 ERROR (jsonrpc/0) [storage.TaskManager.Task] (Task='ed3a34f9-5e81-40f4-a592-78e585c1f937') 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-121>", line 2, in createStorageDomain 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 2644, in createStorageDomain max_hosts=max_hosts) File "/usr/lib/python3.6/site-packages/vdsm/storage/nfsSD.py", line 95, in create version) **File "/usr/lib/python3.6/site-packages/vdsm/storage/nfsSD.py", line 60, in _preCreateValidation *raise se.StorageDomainNotEmpty(typeSpecificArg)vdsm.storage.exception.StorageDomainNotEmpty: Storage domain is not empty - requires cleaning: ('gnodesen2-01.example.com:/dest',)2020-08-24 15:51:58,888+0100 INFO (jsonrpc/0) [storage.TaskManager.Task] (Task='ed3a34f9-5e81-40f4-a592-78e585c1f937') aborting: Task is aborted: "value=Storage domain is not empty - requires cleaning: ('gnodesen2-01.example.com:/dest',) abortedcode=361" (task:1190)* 2020-08-24 15:51:58,888+0100 ERROR (jsonrpc/0) [storage.Dispatcher] FINISH createStorageDomain error=Storage domain is not empty - requires cleaning: ('gnodesen2-01.example.com:/dest',) (dispatcher:83) 2020-08-24 15:51:58,889+0100 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC* call StorageDomain.create failed *(error 361) in 0.20 seconds (init:312) 2020-08-24 15:51:58,934+0100 INFO (jsonrpc/2) [vdsm.api] START disconnectStorageServer(domType=7, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'password': '****', 'vfs_type': 'glusterfs', 'port': '', 'iqn': '', 'connection': 'gnodesen2-01.example.com:/dest', 'ipv6_enabled': 'false', 'id': 'd104177f-f391-45bc-a8a7-905da90d4e7d', 'user': '', 'tpgt': '1'}], options=None) from=::ffff:10.80.101.27,45118, flow_id=f8c31837-fd32-48f2-bed9-6138ea4c6bb0, task_id=badf6391-06cd-4e11-ade5-95dd10b86af5 (api:48) 2020-08-24 15:51:58,934+0100 INFO (jsonrpc/2) [storage.Mount] unmounting /rhev/data-center/mnt/glusterSD/gnodesen2-01.example.com:_dest (mount:215) Any ideas? Regards.

1 0

oVirt node 4.4.1 deploy FQDN not reachable
by Roberto Nunin 25 Aug '20

25 Aug '20

Hi all I have an issue while trying to deploy hyperconverged solution on three ovirt node boxes. ISO used is ovirt-node-ng-installer-4.4.1-2020072310.el8.iso. When from cockpit I choose gluster deployment, I have a form where I can insert both gluster fqdn names and public fqdn names (that is what I need, due to distinct network cards & networks) If I insert right names, that are resolved by nodes, I receive, anyway, FQDN is not reachable below Host1 entries. As already stated, these names are certainly resolved by DNS used. Any hints about ? -- Roberto Nunin

3 5

Actual oVirt install questions
by David White 25 Aug '20

25 Aug '20

:) Ok, after all of the questions I've pestered you guys with, I'm actually getting started. Thank you all for your help. A few of questions right off the bat. For this install, I'm installing the latest (4.4.2) onto CentOS 8. 1) What's the difference between the `ovirt-hosted-engine-setup` command and the `engine-setup` command? I ran both of them, and it seems like they do the exact same thing. 2) For either of the commands above, I'm able to get as far as the step where it asks about the storage: Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs] It's clear to me that using this install method, the storage should be setup first / independently of the installer. So ok, I'll try the Cockpit install, since the documentation says that's the preferred method anyway. (I'm just a sucker for the command line, doing it myself, and understanding everything that I'm doing. I like to avoid GUIs if I can help it. LOL). So I logged into the Cockpit Dashboard at {ip-address}:9090, clicked on 'Virtualization' then clicked on Hosted Engine. Here, I clicked on Hyperconvered, and since I'm just installing to a single host right now, I clicked on Run Gluster Wizard for Single Node. So here's my 3rd question. 3) I can't get past the first step of this wizard. It is asking for the FQDN of the host (Host1). - The documentation indicates that this is NOT the base OS, but I've tried that - I've also tried the IP address that I intend to use for the manager (i.e. what I envision is akin to the vCenter IP address for a vSphere environment -- correct?) In both cases, the wizard won't let me proceed, and keeps saying "Host is not added to known_hosts" What am I missing, here? I'm familiar with the known_hosts file... but that's the VM / manager that I'm trying to create, I thought? Why does the wizard continue to give me that error message? Sent with ProtonMail Secure Email.

4 13

Guest agent ubuntu 20.04
by carl langlois 24 Aug '20

24 Aug '20

Hi, This may not be the right place to ask but any of you is using Ubuntu 20.04 guest. I have noticed that the guest agent is not present in the repo.. Regards Carl

4 4

Is oVirt suited for supporting long-lived VMs than OpenStack?
by yam yam 24 Aug '20

24 Aug '20

Hi guys, I'm wondering why people say oVirt is better suited for traditional workloads like long-lived VMs than OpenStack. does oVirt have some additional features for it? Of course, VMs in OpenStack might be intentionally killed according to resource pressure if auto-scaling is used. but otherwise, I guess OpenStack has enough to run long-lived VMs. thanks.

3 6

Incremental VM backups
by Kevin Doyle 24 Aug '20

24 Aug '20

Hi I am looking at ways to backup VM's, ideally that support incremental backups. I have found a couple of python scripts that snapshot a VM and back it up but not incremental. The question is what do you use to backup the VM's ? (both linux and windows) Thanks Kevin

5 6

[ANN] oVirt 4.4.2 Fourth Release Candidate is now available for testing
by Lev Veyde 23 Aug '20

23 Aug '20

oVirt 4.4.2 Fourth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.2 Fourth Release Candidate for testing, as of August 20th, 2020. This update is the second in a series of stabilization updates to the 4.4 series. 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.2 release highlights: http://www.ovirt.org/release/4.4.2/ * 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.2/ [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>

2 1

VMware import : older SSL version problems
by Philip Brown 23 Aug '20

23 Aug '20

using ovirt 4.4.1 to attempt to import from VMware, I have a problem with older SSL ciphers: libvirt.libvirtError: internal error: curl_easy_perform() returned an error: SSL connect error (35) : error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol where can I tell it "shut up and take the data"? I found on the web a generic openssl reference that supposedly I should be able to edit /etc/pki/tls/openssl.cnf and add MinProtocol=TLSv1.0 CipherString = DEFAULT@SECLEVEL=1 but that didnt help. its still complaining about the SSL protocol. -- Philip Brown| Sr. Linux System Administrator | Medata, Inc. 5 Peters Canyon Rd Suite 250 Irvine CA 92606 Office 714.918.1310| Fax 714.918.1325 pbrown(a)medata.com| www.medata.com

2 1

ovirt-imageio : can't upload / download
by Michael Jones 23 Aug '20

23 Aug '20

Hi, I have image upload/download working on some older ovirt servers where it still has the split daemon/proxy... on one newer one this feature is not working; software in use: CentOS 8 ovirt-engine-4.4.1.10-1.el8.noarch ovirt-imageio-client-2.0.9-1.el8.x86_64 ovirt-imageio-daemon-2.0.9-1.el8.x86_64 ovirt-imageio-common-2.0.9-1.el8.x86_64 the ui test button allowed me to work out 50-vdsm.conf was setting the wrong remote port... (was 54322, changed to 54323) updated remote with; [remote] host = 0.0.0.0 port = 54323 the test now passes, but on upload or download it still fails. Next i changed the control to be unix socket instead of tcp port 54324 (vdsm was giving an error: Image daemon is unsupported); I looked up the error line in the vdsm code, and found it was looking for unix socket: DAEMON_SOCK=/run/ovirt-imageio/sock switching to sock seemed to resolve all errors in the vdsm log; --- content of the imageio log; no errors as far as i can see: 2020-08-18 12:49:56,109 INFO (MainThread) [server] Starting (pid=2696562, version=2.0.9) 2020-08-18 12:49:56,109 DEBUG (MainThread) [services] Creating remote.service on port 54323 2020-08-18 12:49:56,111 DEBUG (MainThread) [http] Prefer IPv4: False 2020-08-18 12:49:56,111 DEBUG (MainThread) [http] Available network interfaces: [(<AddressFamily.AF_INET: 2>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('0.0.0.0', 54323))] 2020-08-18 12:49:56,111 DEBUG (MainThread) [http] Creating server socket with family=AddressFamily.AF_INET and type=SocketKind.SOCK_STREAM 2020-08-18 12:49:56,111 DEBUG (MainThread) [services] Securing server (cafile=/etc/pki/vdsm/certs/cacert.pem, certfile=/etc/pki/vdsm/certs/vdsmcert.pem, keyfile=/etc/pki/vdsm/keys/vdsmkey.pem) 2020-08-18 12:49:56,113 INFO (MainThread) [services] remote.service listening on ('0.0.0.0', 54323) 2020-08-18 12:49:56,113 DEBUG (MainThread) [services] Creating local.service on socket '\x00/org/ovirt/imageio' 2020-08-18 12:49:56,113 INFO (MainThread) [services] local.service listening on '\x00/org/ovirt/imageio' 2020-08-18 12:49:56,113 DEBUG (MainThread) [services] Creating control.service on socket '/run/ovirt-imageio/sock' 2020-08-18 12:49:56,113 DEBUG (MainThread) [uhttp] Removing socket '/run/ovirt-imageio/sock' 2020-08-18 12:49:56,113 INFO (MainThread) [services] control.service listening on '/run/ovirt-imageio/sock' 2020-08-18 12:49:56,115 DEBUG (MainThread) [server] Changing ownership of /run/ovirt-imageio to 988:984 2020-08-18 12:49:56,115 DEBUG (MainThread) [server] Changing ownership of /var/log/ovirt-imageio/daemon.log to 988:984 2020-08-18 12:49:56,115 DEBUG (MainThread) [server] Dropping root privileges, running as 988:984 2020-08-18 12:49:56,116 DEBUG (MainThread) [services] Starting remote.service 2020-08-18 12:49:56,116 DEBUG (remote.service) [services] remote.service started 2020-08-18 12:49:56,116 DEBUG (MainThread) [services] Starting local.service 2020-08-18 12:49:56,117 DEBUG (local.service) [services] local.service started 2020-08-18 12:49:56,117 DEBUG (MainThread) [services] Starting control.service 2020-08-18 12:49:56,117 DEBUG (control.service) [services] control.service started 2020-08-18 12:49:56,117 INFO (MainThread) [server] Ready for requests 2020-08-18 12:51:34,602 INFO (Thread-1) [http] OPEN client=local 2020-08-18 12:51:34,603 INFO (Thread-1) [tickets] [local] ADD ticket={'dirty': False, 'ops': ['read'], 'filename': 'debian-10.3.0-amd64-netinst.iso.raw', 'size': 351272960, 'sparse': True, 'transfer_id': 'ec7b329e-3ef1-448d-ac73-1e5e1b4c0ef9', 'uuid': '17db8f9f-3280-4e7c-8fbf-e5326e1f98be', 'timeout': 300, 'url': 'file:///rhev/data-center/mnt/_var_local_ovirt_local__data/7ee98037-126b-4c79-b921-a9ff4272fa91/images/315af697-a064-4c2c-bdf6-8144a8218526/8e709a79-4da0-4d91-803e-d6ec12ec84c3'} 2020-08-18 12:51:34,603 DEBUG (Thread-1) [http] Empty request line, client disconnected 2020-08-18 12:51:34,603 INFO (Thread-1) [http] CLOSE client=local [connection 1 ops, 0.000842 s] [dispatch 1 ops, 0.000305 s] --- vdsm log for transfer id: ec7b329e-3ef1-448d-ac73-1e5e1b4c0ef9 no errors as far as i can see... 2020-08-18 12:51:34,602+0000 INFO (jsonrpc/5) [vdsm.api] START add_image_ticket(ticket={'dirty': False, 'ops': ['read'], 'filename': 'debian-10.3.0-amd64-netinst.iso.raw', 'size': 351272960, 'sparse': True, 'transfer_id': 'ec7b329e-3ef1-448d-ac73-1e5e1b4c0ef9', 'uuid': '17db8f9f-3280-4e7c-8fbf-e5326e1f98be', 'timeout': 300, 'url': 'file:///rhev/data-center/mnt/_var_local_ovirt_local__data/7ee98037-126b-4c79-b921-a9ff4272fa91/images/315af697-a064-4c2c-bdf6-8144a8218526/8e709a79-4da0-4d91-803e-d6ec12ec84c3'}) from=::ffff:37.187.146.167,58882, flow_id=19204d8c-ffe6-4c45-81fe-96e07097d519, task_id=441bf5ea-1e93-4b5b-aeae-f0e52b43cf62 (api:48) 2020-08-18 12:51:34,603+0000 INFO (jsonrpc/5) [vdsm.api] FINISH add_image_ticket return=None from=::ffff:37.187.146.167,58882, flow_id=19204d8c-ffe6-4c45-81fe-96e07097d519, task_id=441bf5ea-1e93-4b5b-aeae-f0e52b43cf62 (api:54) 2020-08-18 12:51:34,603+0000 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call Host.add_image_ticket succeeded in 0.00 seconds (__init__:312) --- engine log: urn [status=Status [code=0, message=Done]], log id: 7ac2f68b 2020-08-18 12:51:34,604Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-6) [19204d8c-ffe6-4c45-81fe-96e07097d519] Started transfer session with ticket id 17db8f9f-328 0-4e7c-8fbf-e5326e1f98be, timeout 300 seconds 2020-08-18 12:51:34,604Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-6) [19204d8c-ffe6-4c45-81fe-96e07097d519] Adding image ticket to ovirt-imageio-proxy, id 17db8 f9f-3280-4e7c-8fbf-e5326e1f98be 2020-08-18 12:51:34,604Z ERROR [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-6) [19204d8c-ffe6-4c45-81fe-96e07097d519] Failed to add image ticket to ovirt-imageio-proxy: C onnection refused (Connection refused): java.lang.RuntimeException: Connection refused (Connection refused) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.ImageioClient.getConnection(ImageioClient.java:114) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.ImageioClient.putTicket(ImageioClient.java:65) is there a way for me to validate where engine thinks the proxy is? the test button passed after changing remote port to 54323... any help much appreciated. Kind Regards, Michael Jones

3 14

Max running ansible-playbook
by Tommaso - Shellrent 21 Aug '20

21 Aug '20

Hi to all. on our angine we always see max 2 ansible-playbook running on the same time. How can we ingrease this value? Regards. -- -- Shellrent - Il primo hosting italiano Security First *Tommaso De Marchi* /COO - Chief Operating Officer/ Shellrent Srl Via dell'Edilizia, 19 - 36100 Vicenza Tel. 0444321155 <tel:+390444321155> | Fax 04441492177

2 3

HCI Cluster Configuration
by Clint Boggio 20 Aug '20

20 Aug '20

Ovirt 4.3.9 HCI Gluster 3 Dell 730XD Managed Engine When I finished the "hosted engine deploy" I failed to add the gluster storage according to the documentation and i'd like to get that back on track. 1. I ticked the check box in the cluster configuration to "enable gluster service", all of my current gluster storage domains went "red triangle" on me and the hosts also went "red triangle" so I quickly changed it back and all went back to normal. Do I need to check that box to make the "Use Managed Gluster Volume" check box and drop down menu show my HCI gluster volumes that exist on the three nodes ? Do I need to put the storage domain(s) in maintenance mode to change them from unmanaged to managed ? Will the system honor the VM(s) that live in my "engine" and "vmstore" gluster volumes which are currently in use in the system if/when I change them from unmanaged to managed,or will the system wipe them and hose my managed engine and VMs ? Thank you for your help !

1 0

Re: Help remove snapshot
by Shani Leviim 20 Aug '20

20 Aug '20

Hi Magnus, Sounds like you triggered this one https://bugzilla.redhat.com/show_bug.cgi?id=1555116. The error message you've got was meant to avoid removing a snapshot from a broken chain. On the Active VM snapshot -> Disks, is there any disk with Illegal status? Deleting the whole snapshot can be done from the DB: *delete from snapshots where snapshot_id = '.....';* Although it's recommended to understand the root cause for that one. Can you please share your engine.log? *Regards,* *Shani Leviim* On Mon, Aug 17, 2020 at 1:37 PM Magnus Isaksson <magnus(a)vmar.se> wrote: > Hi! > > I would need some help removing a snapshot that looks like this. > How do i remove it manually or fix snapshot definition? > ----------------- > Error while executing action: > > TUN_SALDC01: > > - The requested snapshot has an invalid parent, either fix the > snapshot definition or remove it manually to complete the process. > > ----------------- > And when i look at the disk on tha tnapshot it show as this: > > > And general info: > > _______________________________________________ > 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/5QEBPZPUHDGS5… >

3 3

Re-creating ISO Storage Domain after Manager Rebuild
by bob.franzke＠mdaemon.com 19 Aug '20

19 Aug '20

Hi All, Late last year I had a disk issue with my Ovirt Manager Server that required I rebuild it and restored from backups. While this worked mostly, one thing that did not get put back correctly was the physical storage location of an ISO domain on the manager server. I believe this was previously set up as an NFS share being hosted on the Manager Server itself. The physical disk path and filesystem were not re-created on the manager server's local disk. So after the restore, the ISO domain shows up in the Ovirt Admin portal but shows the as down, and inactive. If I go into the domain, the 'Manage Domain' and 'Remove' buttons are not available. The only option I have for this is 'Destroy'. I right now have no ability to do things like boot a VM from a CD and am assuming its because the ISO domain that the images for this would be stored on is not available. How can I recreate this ISO domains to be able to upload ISO images that VM machines can boot from.The original path on the manager server was /gluster: sdc 8:32 0 278.9G 0 disk ├─sdc1 8:33 0 1G 0 part /boot └─sdc2 8:34 0 277.9G 0 part ├─centos_mydesktop-root 253:0 0 50G 0 lvm / ├─centos_mydesktop-swap 253:1 0 23.6G 0 lvm [SWAP] ├─centos_mydesktop-home 253:2 0 25G 0 lvm /home └─centos_mydesktop-gluster 253:3 0 179.3G 0 lvm /gluster The current layout is now: â””â”€sda3 8:3 0 277.7G 0 part â”œâ”€centos-root 253:0 0 50G 0 lvm / â”œâ”€centos-swap 253:1 0 4G 0 lvm [SWAP] â””â”€centos-home 253:2 0 223.7G 0 lvm /home Can I just create a new filesystem here, destroy the old ISO domain, and add a new one using the new path? I am a total Ovirt Noob so would appreciate any help here. Thanks. Bob

5 5

Problem with "ceph-common" pkg for oVirt Node 4.4.1
by m.andreev＠2500baden.eu 19 Aug '20

19 Aug '20

Hi! I have a problem with install ceph-common package(needed for cinderlib Managed Block Storage) in oVirt Node 4.4.1 - oVirt doc say: "$ yum install -y ceph-common" but no Repo with ceph-common ver 12.2.7 for CentOS8 - official CentOS has only "ceph-common-10.2.5-4.el7.x86_64.rpm" and CEPH has only ceph-common ver. 14.2 for EL8 How can I install ceph-common ver. 12.2.7? BR Mike

3 2

Upgrade Memory of oVirt Nodes
by souvaliotimaria＠mail.com 19 Aug '20

19 Aug '20

Hello everyone, I have an oVirt 4.3.2.5 hyperconverged 3 node production environment and we want to add some RAM to it. Can I upgrade the RAM without my users noticing any disruptions and keep the VMs running? The way I thought I should do it was to migrate any running VMs to the other nodes, then set one node in maintenance mode, shut it down, place the new memory, bring it back up, remove it from maintenance mode and see how the installation reacts and repeat for the other two nodes. Is this correct or should I follow another way? Will there be a problem during the time when the nodes will not be identical in their resources? Thank you for your time, Souvalioti Maria

4 5

OVirt hosted engine setup dnf config
by Raphael Höser 19 Aug '20

19 Aug '20

Hi all, I'm currently installing OVirt 4.4 on CentOS 8 in an hosted engine setup and it fails during ovirt-hosted-engine-setup. Because of our corporate proxy, some changes to the dnf.conf is needed (namely proxy_auth_method=basic) and the config is working fine when running dnf commands the normal way. Proxy configuration is provided via http_proxy, https_proxy and ftp_proxy env vars. The setup fails during a DNF call with status code 407 (proxy auth required). Is there another way to provide that config or any other way to resolve this? My googling didn't help me yet. On the same machine I had a running OVirt 4.3 on CentOS 7 running as a test and now wanted to upgrade (after a complete wipe). Thanks for your help, Raphael content of /etc/dnf/dnf.conf: [main] gpgcheck=1 installonly_limit=3 clean_requirements_on_remove=True best=True skip_if_unavailable=False proxy_auth_method=basic timeout=120 minrate=90 Log of ovirt-hosted-engine-setup: [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup During customization use CTRL-D to abort. Continuing will configure this host for serving as hypervisor and will create a local VM with a running engine. The locally running engine will be used to configure a new storage domain and create a VM there. At the end the disk of the local VM will be moved to the shared storage. Are you sure you want to continue? (Yes, No)[Yes]: Configuration files: Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20200818091958-tozsht.log Version: otopi-1.9.2 (otopi-1.9.2-1.el8) [ INFO ] DNF Downloading 1 files, 0.00KB [ INFO ] DNF Downloaded CentOS-8 - AppStream [ INFO ] DNF Errors during downloading metadata for repository 'AppStream': - Status code: 407 for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=$i… (IP: 10.201.210.68) - Status code: 407 for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=$i… (IP: 10.201.210.67) [ ERROR ] DNF Failed to download metadata for repo 'AppStream': Cannot prepare internal mirrorlist: Status code: 407 for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=$i… (IP: 10.201.210.67) [ ERROR ] Failed to execute stage 'Environment setup': Failed to download metadata for repo 'AppStream': Cannot prepare internal mirrorlist: Status code: 407 for http://mirrorlist.centos.org/?release=8&arch=x86_64&repo=AppStream&infra=$i… (IP: 10.201.210.67) [ INFO ] Stage: Clean up [Some more cleanup]

3 8

Re: Help remove snapshot
by Shani Leviim 19 Aug '20

19 Aug '20

Hi Magnus, You can find the VM's snapshot by sending a REST API request http://localhost:8080/ovirt-engine/api/vms/<vm-id>/snapshots/ You can also find the VM's snapshots (and view their parameters) by using SQL: select * from snapshots where vm_id = '<vm-id>'; You can also delete the relevant snapshot by specifying the snapshot's description: *delete from snapshots where description = '.....';* *Regards,* *Shani Leviim* On Tue, Aug 18, 2020 at 7:50 PM Magnus Isaksson <magnus(a)vmar.se> wrote: > Hi Shani > > Thanks for the help. > > What i can see it does not display any illegal statuses. > > I am a bit unsure how to delete it from the DB, how do i find the > snapshot_id? > > Cheers > Magnus > > ------------------------------ > *From:* Shani Leviim <sleviim(a)redhat.com> > *Sent:* 17 August 2020 13:45 > *To:* Magnus Isaksson <magnus(a)vmar.se> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Help remove snapshot > > Hi Magnus, > Sounds like you triggered this one > https://bugzilla.redhat.com/show_bug.cgi?id=1555116. > The error message you've got was meant to avoid removing a snapshot from a > broken chain. > > On the Active VM snapshot -> Disks, is there any disk with Illegal status? > > Deleting the whole snapshot can be done from the DB: > *delete from snapshots where snapshot_id = '.....';* > > Although it's recommended to understand the root cause for that one. > > Can you please share your engine.log? > > > *Regards, * > > *Shani Leviim * > > > On Mon, Aug 17, 2020 at 1:37 PM Magnus Isaksson <magnus(a)vmar.se> wrote: > > Hi! > > I would need some help removing a snapshot that looks like this. > How do i remove it manually or fix snapshot definition? > ----------------- > Error while executing action: > > TUN_SALDC01: > > - The requested snapshot has an invalid parent, either fix the > snapshot definition or remove it manually to complete the process. > > ----------------- > And when i look at the disk on tha tnapshot it show as this: > > > And general info: > > _______________________________________________ > 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/5QEBPZPUHDGS5… > >

1 0

HA Storage options
by David White 19 Aug '20

19 Aug '20

Hi, I started an email thread a couple months ago, and felt like I got some great feedback and suggestions on how to best setup an oVirt cluster. Thanks for your responses thus far.My goal is to take a total of 3-4 servers that I can use for both the storage and the virtualization, and I want both to be highly available. You guys told me about oVirt Hyperconverged with Gluster, and that seemed like a great option. However, I'm concerned that this may not actually be the best approach. I've spoken with multiple people at Red Hat who I have a relationship with (outside of the context of the project I'm working on here), and all of them have indicated to me that Gluster is being deprecated, and that most of the engineering focus these days is on Ceph. I was also told by a Solutions Architect who has extensive experience with RHV that the hyperconverged clusters he used to build would always give him problems. Does oVirt support DRBD or Ceph storage? From what I can find, I think that the answer to both of those is, sadly, no. So now I'm thinking about switching gears, and going with iSCSI instead. But I'm still trying to think about the best way to replicate the storage, and possibly use multipathing so that it will be HA for the VMs that rely on it. Has anyone else experienced problems with the Gluster hyperconverged solution? Am I overthinking this whole thing, and am I being too paranoid? Is it possible to setup some sort of software-RAID with multiple iSCSI targets? As an aside, I now have a machine that I was planning to begin doing some testing and practicing with. Previous to my conversations with the folks at Red Hat, I was planning on doing some initial testing and config with this server before purchasing another 2-3 servers to build the hyperconverged cluster. Sent with ProtonMail Secure Email.

4 3

Cannot access Engine VM
by Steven Bach 18 Aug '20

18 Aug '20

Hello All, I installed Ovirt node 4.4.1.5 from the ovirt ISO, IP 192.168.1.53/24 I setup the self hosted engine by logging into the web interface, configured it for 192.168.1.55/24 IP on the default generated bridge interface and setup a FQDN that is resolvable via DNS. Setup NFS storage, and all seems good. The Engine VM is running, but I cannot access it at all outside the node. SSH'd in the node I can ping the engine, anything else on that same subnet cannot SSH or even ping it (Again, DNS is resolving correctly to the IP Address). I am able to SSH into the engine from the node. While SSH'd into the Engine from the node, I can only ping the Node and nothing beyond that, not able to install ovirt repo, nothing. Any ideas are greatly appreciated, thank you, -- Steven Bach sbach(a)bachnetworks.com

2 1

Re: Help with problem in oVirt 4.4.
by Nir Soffer 18 Aug '20

18 Aug '20

On Tue, Aug 18, 2020 at 6:07 AM Rodrigo Mauriz <rmauriz(a)gmail.com> wrote: Hi Rodrigo, I'm moving the discussion to ovirt users list, which is the right place to discuss this: https://lists.ovirt.org/archives/list/users%40ovirt.org/ > When I try to upload an ISO file by: > > Storage -> Storage Domains -> Disks > I get an error: > "Connection to ovirt-imageio-proxy service failed. Make sure service is installed, configured, and ovirt-engine certificate is registered as valid CA in browser." > > Review and note that the services that perform this task were not installed in the ovirt-engine: > • ovirt-imageio-proxy This package does not exist and not needed in ovirt 4.4 > • ovirt-imageio-daemon > • ovirt-imageio-common These packages are needed, and installed when you instal ovirt-engine. The ovirt-imageio service is configured automatically when you run engine-setup. > Example: > #systemctl status ovirt-imageio-proxy (not installed) > > I tried to install it but it throws it an error: > > #yum install ovirt-imageio-proxy engine-setup > > Updating Subscription Management repositories. > Unable to read consumer identity > This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. > Last metadata expiration check: 0:41:46 Aug on Fri 07 Aug 2020 10:20:42 AM -04. > No match for argument: ovirt-imageio-proxy > No match for argument: engine-setup > Error: Unable to find a match: ovirt-imageio-proxy engine-setup This is correct, ovirt-imageio-proxy is not needed and does not exist. > The same, for the engine-iso-uploader I think the iso uploader was deprecated a long time ago, and it is not needed to upload images. > I asked a person who works at Red Hat and they told me that this apps (services) are not released yet. Uploading images from the UI was available in ovirt 4.4.0, but is fully functional since ovirt 4.4.1. We know about hone issue - if you replaced apache certificates with 3rd party certificates, uploading via ovirt-imageio service on engine host (as a proxy) will not work: https://bugzilla.redhat.com/1866745 https://bugzilla.redhat.com/1862107 If you are using engine built certificates, upload and download should work. We may have more info about the failure in engine log. Please share the log showing the time when you tried to upload an image. Nir

1 0

Glusterfs version
by suporte＠logicworks.pt 17 Aug '20

17 Aug '20

Hello, What is the compatibility gluster version to work with oVirt 4.4.1 ? Thanks -- Jose Ferradeira http://www.logicworks.pt

2 1

Help remove snapshot
by Magnus Isaksson 17 Aug '20

17 Aug '20

Hi! I would need some help removing a snapshot that looks like this. How do i remove it manually or fix snapshot definition? ----------------- Error while executing action: TUN_SALDC01: * The requested snapshot has an invalid parent, either fix the snapshot definition or remove it manually to complete the process. ----------------- And when i look at the disk on tha tnapshot it show as this: [cid:98462a7f-dbb6-447e-925a-5b170883d7c7] And general info: [cid:9264e2e0-459f-4b54-aba7-08b3bf1f4068]

1 0

How to diable dhcp in ovirt network
by Adam Xu 17 Aug '20

17 Aug '20

Hi everyone Recently, when I install okd on ovirt. The installation process was failed because the vm automatically acquired an IP address from DHCP before the installer assigned it. Our DHCP is enabled by a layer 3 switch, I tried to diable dhcp using network filter. but there is no entry related to blocking the DHCP feature. Is there any way for ovirt to disable DHCP? -- Adam Xu

2 1

Help needed - Not able to find Windows Guest agent in 4.4.1.10-1.el8 Hosted Engine
by dhanaraj.ramesh＠yahoo.com 17 Aug '20

17 Aug '20

Hi Team, unable to locate Windows guest agant iso in 4.4.1.10-1.el8 Hosted Engine version. please share us where can i get the iso? there is no /usr/share/oVirt-guest-tools-iso/oVirt-tools-setup.iso available in 4.4.1 HE

3 2

Migration not working
by Juan Pablo Lorier 17 Aug '20

17 Aug '20

Hi, I'm having issues with migration to some hosts. I have a 4 node cluster and I tried updating to see if it fixes but it's still failing. The reason is nos clear in the engine log. 2020-08-14 09:45:32,322-03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-429) [364e7777] EVENT_ID: VM_MIGRATION_START_SYSTEM_INITIAT ED(67), Migration initiated by system (VM: medialist2-videoteca, Source: virt2.tnu.com.uy, Destination: virt3.tnu.com.uy, Reason: ). 2020-08-14 09:45:32,336-03 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-429) [535a8bdb] Lock Acquired to object 'EngineLock:{exclusiveLocks='[aac7468 5-c969-4761-923f-043400176edf=VM]', sharedLocks=''}' 2020-08-14 09:45:32,355-03 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-429) [535a8bdb] Running command: MigrateVmToServerCommand internal: true. Ent ities affected : ID: aac74685-c969-4761-923f-043400176edf Type: VMAction group MIGRATE_VM with role type USER 2020-08-14 09:45:32,383-03 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-429) [535a8bdb] START, MigrateVDSCommand( MigrateVDSCommandParameters:{hostId= '634f3f64-8945-470c-b31c-b8d4c73109e6', vmId='aac74685-c969-4761-923f-043400176edf', srcHost='virt2.tnu.com.uy', dstVdsId='f9e441a0-a4e6-4548-8c6f-83a958120f02', dstHost='virt4. tnu.com.uy:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', consoleAddress='null', maxBandwidth= '125', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action= {name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, pa rams=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='172.16.100.45'}), log id: 1db80717 2020-08-14 09:45:32,385-03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-429) [535a8bdb] START, MigrateBrokerVDSCommand(HostName = virt 2.tnu.com.uy, MigrateVDSCommandParameters:{hostId='634f3f64-8945-470c-b31c-b8d4c73109e6', vmId='aac74685-c969-4761-923f-043400176edf', srcHost='virt2.tnu.com.uy', dstVdsId='f9e4 41a0-a4e6-4548-8c6f-83a958120f02', dstHost='virt4.tnu.com.uy:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompre ssed='false', consoleAddress='null', maxBandwidth='125', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDow ntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, para ms=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='172.1 6.100.45'}), log id: 4085b503 2020-08-14 09:45:32,433-03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-429) [535a8bdb] FINISH, MigrateBrokerVDSCommand, return: , log id: 4085b503 2020-08-14 09:45:32,437-03 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-429) [535a8bdb] FINISH, MigrateVDSCommand, return: MigratingFrom, log id: 1db8 0717 2020-08-14 09:45:32,446-03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-429) [535a8bdb] EVENT_ID: VM_MIGRATION_START_SYSTEM_INITIAT ED(67), Migration initiated by system (VM: reverse_proxy, Source: virt2.tnu.com.uy, Destination: virt4.tnu.com.uy, Reason: ). 2020-08-14 09:45:32,462-03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-429) [535a8bdb] EVENT_ID: USER_VDS_MAINTENANCE_WITHOUT_REASON(620), Host virt2.tnu.com.uy was switched to Maintenance mode by jplorier(a)tnu.com.uy. 2020-08-14 09:45:32,681-03 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-14) [7667d149-886e-406b-9cd6-9b7472fa9944] Command 'MaintenanceNumberOfVdss' id: 'db97a747-115b-4f01-aa3d-6277080e6a44' child commands '[]' executions were completed, status 'SUCCEEDED' 2020-08-14 09:45:33,024-03 INFO [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedThreadFactory-engineScheduled-Thread-62) [] Received first domain report for host virt2.tnu.com.uy 2020-08-14 09:45:33,686-03 INFO [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-88) [7667d149-886e-406b-9cd6-9b7472fa9944] Ending command 'org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand' successfully. 2020-08-14 09:45:35,137-03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [] VM 'fd854ebe-144f-455f-bf0c-48167d7aae9f'(medialist2-videoteca) moved from 'MigratingFrom' --> 'Up' 2020-08-14 09:45:35,137-03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [] Adding VM 'fd854ebe-144f-455f-bf0c-48167d7aae9f'(medialist2-videoteca) to re-run list 2020-08-14 09:45:35,144-03 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [] Rerun VM 'fd854ebe-144f-455f-bf0c-48167d7aae9f'. Called from VDS 'virt2.tnu.com.uy' *In the host running the vm, I see no error related to the migration, only about Engine VM which seems to be working fine otherwise:* 2020-08-14 09:06:23,337-0400 ERROR (jsonrpc/3) [root] failed to retrieve Hosted Engine HA score '[Errno 2] No such file or directory'Is the Hosted Engine setup finished? (api:19 *VDSM version in node:* vdsm.x86_64 4.30.46-1.el7 @ovirt-4.3 All nodes are up to date. Thanks

3 3

oVirt nested on oVirt works, when you enable MAC spoofing on host VMs
by thomas＠hoberg.net 13 Aug '20

13 Aug '20

Howto: Create a new network profile that doesn't have the MAC spoofing filter included. In my case I used one without any filters, you may want to be more careful. Background: I had tried the nested approach with the default settings and found that the hosted-engine setup worked just find to the point where it was running as a nested VM on the install node, but that it failed to tie in the other gluster nodes or to communicate to the outside: There was something wrong with the network, but no obivous failures. I tried using other, simpler "client hypervisors" (it's all KVM anyway) VirtualBox and 'native' KVM and the symptoms were the same: The VMs ran just fine, but the network didn't connect. And then I remembered that obviously a Hypervisor need to override the MAC for each client VM if you want full network access and I had come across "no-mac-spoofing" often enough it somehow stayed on my mind... and finally it clicked. Anyhow, validing full functionality now and the main interest in this is the ability to do a full simulation/testing of oVirt 4.3->4.4 upgrades on 3-node HCI setups, which I'd rather not do on the live physical system. Of course, it's also quite cool!

1 0

Support for Shared SAS storage
by Vinícius Ferrão 13 Aug '20

13 Aug '20

Hello, I’ve two compute nodes with SAS Direct Attached sharing the same disks. Looking at the supported types I can’t see this on the documentation: https://www.ovirt.org/documentation/admin-guide/chap-Storage.html There’s is local storage on this documentation, but my case is two machines, both using SAS, connected to the same machines. It’s the VRTX hardware from Dell. Is there any support for this? It should be just like Fibre Channel and iSCSI, but with SAS instead. Thanks,

7 11

[ANN] oVirt 4.4.2 Third Release Candidate is now available for testing
by Lev Veyde 13 Aug '20

13 Aug '20

oVirt 4.4.2 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.2 Third Release Candidate for testing, as of August 13th, 2020. This update is the second in a series of stabilization updates to the 4.4 series. 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.2 release highlights: http://www.ovirt.org/release/4.4.2/ * 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.2/ [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

Request for feedback about "Overview of Networking in oVirt"
by Dominik Holler 12 Aug '20

12 Aug '20

Hello, there is a new documentation "Overview of Networking in oVirt" available in https://www.ovirt.org/documentation/networking-overview/ Please let me know if you have any questions, comments, suggestions, or any kind of critics about this text. If you want to improve, you could also create directly a Pull Request on https://github.com/ovirt/ovirt-site . Thanks Dominik

3 3

Is the udev settling issue more wide spread? Getting failed 'qemu-img -convert' also while copying disks between data and vmstore domains
by thomas＠hoberg.net 12 Aug '20

12 Aug '20

While trying to diagnose an issue with a set of VMs that get stopped for I/O problems at startup, I try to deal with the fact that their boot disks cause this issue, no matter where I connect them. They might have been the first disks I ever tried to sparsify and I was afraid that might have messed them up. The images are for a nested oVirt deployment and they worked just fine, before I shut down those VMs... So I first tried to hook them as secondary disks to another VM to have a look, but that just cause the other VM to stop at boot. Also tried downloading, exporting, and plain copying the disks to no avail, OVA exports on the entire VM fail again (fix is in!). So to make sure copying disks between volumes *generally* work, I tried copying a disk from a working (but stopped) VM from 'vmstore' to 'data' on my 3nHCI farm, but that failed, too! Plenty of space all around, but all disks are using thin/sparse/VDO on SSD underneath. Before I open a bug, I'd like to have some feedback if this is a standard QA test, this is happening to you etc. Still on oVirt 4.3.11 with pack_ova.py patched to wait for the udev settle, This is from the engine.log on the hosted-engine: 2020-08-12 00:04:15,870+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM gem2 command HSMGetAllTasksStatusesVDS failed: low level Image copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'raw', u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_vmstore/9d1b8774-c5dc-46a8-bfa2-6a6db5851195/images/aca27b96-7215-476f-b793-fb0396543a2e/311f853c-e9cc-4b9e-8a00-5885ec7adf14', '-O', 'raw', u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_data/32129b5f-d47c-495b-a282-7eae1079257e/images/f6a08d2a-4ddb-42da-88e6-4f92a38b9c95/e0d00d46-61a1-4d8c-8cb4-2e5f1683d7f5'] failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading sector 131072: Transport endpoint is not connected\\nqemu-img: error while reading sector 135168: Transport endpoint is not connected\\nqemu-img: error while reading sector 139264: Transport endpoint is not connected\\nqemu-img: error while reading sector 143360: Transport endpoint is not connected\\nqemu-img: error while reading sector 147456: Transport endpoint is not connected\\nqemu-img: error while reading sector 151552: Transport endpoint is not connected\\n')",) and this is from the vdsm.log on the gem2 node: Error: Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'raw', u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_vmstore/9d1b8774-c5dc-46a8-bfa2-6a6db5851195/images/aca27b96-7215-476f-b793-fb0396543a2e/311f853c-e9cc-4b9e-8a00-5885ec7adf14', '-O', 'raw', u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_data/32129b5f-d47c-495b-a282-7eae1079257e/images/f6a08d2a-4ddb-42da-88e6-4f92a38b9c95/e0d00d46-61a1-4d8c-8cb4-2e5f1683d7f5'] failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading sector 131072: Transport endpoint is not connected\nqemu-img: error while reading sector 135168: Transport endpoint is not connected\nqemu-img: error while reading sector 139264: Transport endpoint is not connected\nqemu-img: error while reading sector 143360: Transport endpoint is not connected\nqemu-img: error while reading sector 147456: Transport endpoint is not connected\nqemu-img: error while reading sector 151552: Transport endpoint is not connected\n') 2020-08-12 00:03:15,428+0200 ERROR (tasks/7) [storage.Image] Unexpected error (image:849) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/image.py", line 837, in copyCollapsed raise se.CopyImageError(str(e)) CopyImageError: low level Image copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'raw', u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_vmstore/9d1b8774-c5dc-46a8-bfa2-6a6db5851195/images/aca27b96-7215-476f-b793-fb0396543a2e/311f853c-e9cc-4b9e-8a00-5885ec7adf14', '-O', 'raw', u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_data/32129b5f-d47c-495b-a282-7eae1079257e/images/f6a08d2a-4ddb-42da-88e6-4f92a38b9c95/e0d00d46-61a1-4d8c-8cb4-2e5f1683d7f5'] failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading sector 131072: Transport endpoint is not connected\\nqemu-img: error while reading sector 135168: Transport endpoint is not connected\\nqemu-img: error while reading sector 139264: Transport endpoint is not connected\\nqemu-img: error while reading sector 143360: Transport endpoint is not connected\\nqemu-img: error while reading sector 147456: Transport endpoint is not connected\\nqemu-img: error while reading sector 151552: T ransport endpoint is not connected\\n')",) 2020-08-12 00:03:15,429+0200 ERROR (tasks/7) [storage.TaskManager.Task] (Task='6399d533-e96a-412d-b0c3-0548e24d658d') 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 "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 336, in run return self.cmd(*self.argslist, **self.argsdict) File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1633, in copyImage postZero, force, discard) File "/usr/lib/python2.7/site-packages/vdsm/storage/image.py", line 837, in copyCollapsed raise se.CopyImageError(str(e)) CopyImageError: low level Image copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'raw', u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_vmstore/9d1b8774-c5dc-46a8-bfa2-6a6db5851195/images/aca27b96-7215-476f-b793-fb0396543a2e/311f853c-e9cc-4b9e-8a00-5885ec7adf14', '-O', 'raw', u'/rhev/data-center/mnt/glusterSD/192.168.0.91:_data/32129b5f-d47c-495b-a282-7eae1079257e/images/f6a08d2a-4ddb-42da-88e6-4f92a38b9c95/e0d00d46-61a1-4d8c-8cb4-2e5f1683d7f5'] failed with rc=1 out='' err=bytearray(b'qemu-img: error while reading sector 131072: Transport endpoint is not connected\\nqemu-img: error while reading sector 135168: Transport endpoint is not connected\\nqemu-img: error while reading sector 139264: Transport endpoint is not connected\\nqemu-img: error while reading sector 143360: Transport endpoint is not connected\\nqemu-img: error while reading sector 147456: Transport endpoint is not connected\\nqemu-img: error while reading sector 151552: T ransport endpoint is not connected\\n')",)

3 4

uprade from 4.3 to 4.4
by suporte＠logicworks.pt 12 Aug '20

12 Aug '20

Hello, is possible to upgrade from ovirt 4.3 to 4.4 ? Thanks -- Jose Ferradeira http://www.logicworks.pt

2 2

oVirt 4.4.0 Release is now generally available
by Sandro Bonazzola 12 Aug '20

12 Aug '20

oVirt 4.4.0 Release is now generally available The oVirt Project is excited to announce the general availability of the oVirt 4.4.0 Release, as of May 20th, 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 Some of the features included in the oVirt 4.4.0 release require content that will be available in CentOS Linux 8.2 but cannot be tested on RHEL 8.2 yet due to some incompatibility in the openvswitch package that is shipped in CentOS Virt SIG, which requires rebuilding openvswitch on top of CentOS 8.2. The cluster switch type OVS is not implemented for CentOS 8 hosts. Please note that oVirt 4.4 only supports clusters and datacenters with compatibility version 4.2 and above. If clusters or datacenters 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, 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 users mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Installation instructions For the engine: either use the oVirt appliance or install CentOS Linux 8 minimal by following these steps: - Install the CentOS Linux 8 image from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps postgresql:12 - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8 from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8…, selecting the minimal installation. - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm - dnf update (reboot if needed) - Attach the host to the engine and let it be deployed. Update instructionsUpdate from oVirt 4.4 Release Candidate On the engine side and on CentOS hosts, you’ll need to switch from ovirt44-pre to ovirt44 repositories. In order to do so, you need to: 1. dnf remove ovirt-release44-pre 2. rm -f /etc/yum.repos.d/ovirt-4.4-pre-dependencies.repo 3. rm -f /etc/yum.repos.d/ovirt-4.4-pre.repo 4. dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm 5. dnf update On the engine side you’ll need to run engine-setup only if you were not already on the latest release candidate. On oVirt Node, you’ll need to upgrade with: 1. Move node to maintenance 2. dnf install https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/noarch/ovirt-node-ng-imag… 3. Reboot 4. Activate the host Update from oVirt 4.3 oVirt 4.4 is available only for CentOS 8. In-place upgrades from previous installations, based on CentOS 7, are not possible. For the engine, use backup, and restore that into a new engine. Nodes will need to be reinstalled. A 4.4 engine can still manage existing 4.3 hosts, but you can’t add new ones. For a standalone engine, please refer to upgrade procedure at https://ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3 If needed, run ovirt-engine-rename (see engine rename tool documentation at https://www.ovirt.org/documentation/admin-guide/chap-Utilities.html ) When upgrading hosts: You need to upgrade one host at a time. 1. Turn host to maintenance. Virtual machines on that host should migrate automatically to a different host. 2. Remove it from the engine 3. Re-install it with el8 or oVirt Node as per installation instructions 4. Re-add the host to the engine Please note that you may see some issues live migrating VMs from el7 to el8. If you hit such a case, please turn off the vm on el7 host and get it started on the new el8 host in order to be able to move the next el7 host to maintenance. What’s new in oVirt 4.4.0 Release? - Hypervisors based on CentOS Linux 8 (rebuilt from award winning RHEL8), for both oVirt Node and standalone CentOS Linux hosts. - Easier network management and configuration flexibility with NetworkManager. - VMs based on a more modern Q35 chipset with legacy SeaBIOS and UEFI firmware. - Support for direct passthrough of local host disks to VMs. - Live migration improvements for High Performance guests. - New Windows guest tools installer based on WiX framework now moved to VirtioWin project. - Dropped support for cluster level prior to 4.2. - Dropped API/SDK v3 support deprecated in past versions. - 4K block disk support only for file-based storage. iSCSI/FC storage do not support 4K disks yet. - You can export a VM to a data domain. - You can edit floating disks. - Ansible Runner (ansible-runner) is integrated within the engine, enabling more detailed monitoring of playbooks executed from the engine. - Adding and reinstalling hosts is now completely based on Ansible, replacing ovirt-host-deploy, which is not used anymore. - The OpenStack Neutron Agent cannot be configured by oVirt anymore, it should be configured by TripleO instead. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.1 * CentOS Linux (or similar) 8.1 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.1 * CentOS Linux (or similar) 8.1 * oVirt Node 4.4 based on CentOS Linux 8.1 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. If you manage more than one oVirt instance, OKD or RDO we also recommend to try ManageIQ <http://manageiq.org/>. In such a case, please be sure to take the qc2 image and not the ova image. 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.0 release highlights: http://www.ovirt.org/release/4.4.0/ * 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.0/ [2] http://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/> [image: |Our code is open_] <https://www.redhat.com/en/our-code-is-open> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

11 35

Reverting to Snapshot
by Christian Reiss 12 Aug '20

12 Aug '20

Hey folks, this, I hope, is a trivial question. But I really can't find the button for it. If you take a snapshot of any vm - how do you revert to that snapshot, discarding all changes after? I see options to clone, delete, take snapshot, preview... but revert? Really in the true sense of "discard all changes, go back to this snapshot state". What am I not seeing here? :) -- with kind regards, mit freundlichen Gruessen, Christian Reiss

2 2

oVirt Node 4.1.1 Hosted Engine Deployment Fibre Channel No LUNS found
by hkexdong＠yahoo.com.hk 12 Aug '20

12 Aug '20

I've an external RAID subsystem connect to the host by SAS cable (SFF-8644). I follow the instructions of the RAID card manufacture. Include the driver during host installation. And I can see the created RAID volumes (LUNs) available in "Installation Destination". Although I choose to install the engine in host local disk. The installation success and I proceed to hosted engine deployment by Cockpit. And now I stuck at part 4 Storage. I believe "Storage Type" select "Fibre Channel" is correct even I'm not using fibre cable. As NFS and iSCSI are utilize network. I confirm there are 2 RAID volume (LUN0 & LUN1) created in the external RAID subsystem. Why oVirt cannot discover them. What could be wrong :(

3 6

Hosted Engine Deployment stuck at 3. Prepare VM
by hkexdong＠yahoo.com.hk 12 Aug '20

12 Aug '20

oVirt Node version is 4.4.1. This version can successful deploy before. But after I compile the RAID driver. It now stuck at Prepare VM. The last message is "[ INFO ] TASK [ovirt.hosted_engine_setup : Install ovirt-engine-appliance rpm]" According to the instructions from RAID controller manufacture. I'd install the "kernel-headers-xxx.rpm" and "kernel-devel-xxx.rpm" which extracted from official CentOS 8.2.2004 ISO. Also include a bunch of packages for compile driver (e.g. gcc, make, zlib-devel, etc.) I think those packages ruined the deployment. But I still want to know it actually stuck at which part and the reason. Is there any way to check the deployment log?

5 4

ovirt4.4 and ldap auth with starttls
by Jiří Sléžka 11 Aug '20

11 Aug '20

Hello, better start new thread... it looks like tls1.0 is not supported anymore in ovirt-engine-extension-aaa-ldap I just migrated engine from 4.3 to 4.4 and cannot use my ldap profile because server_error: The connection reader was unable to successfully complete TLS negotiation: SSLHandshakeException(The server selected protocol version TLS10 is not accepted by client preferences [TLS12]), ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb but when I try to force tls 1.0 by setting ... pool.default.ssl.startTLS = true pool.default.ssl.startTLSProtocol = TLSv1 ... I got server_error: The connection reader was unable to successfully complete TLS negotiation: SSLHandshakeException(No appropriate protocol (protocol is disabled or cipher suites are inappropriate)), ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb I can't switch to something better on server side, is it possible to allow weak ciphers/protocols on client side? Thanks in advance, Jiri

2 2

ovirt4.4.1 engine Deployment failure
by xilazz＠126.com 11 Aug '20

11 Aug '20

Hello, everyone I am using these versions for my test : - ovirt-engine-appliance-4.4-20200723102445.1.el8.x86_64.rpm - ovirt-node-ng-installer-4.4.1-2020072310.el8.iso But I'm always prompted when I'm hosting a cubide-engine deploy :The error was: error while evaluating conditional ((otopi_host_net.ansible_facts.otopi_host_net | length == 0)).The specific hints are:fatal: [localhost]: FAILED! => {"msg": "The conditional check '(otopi_host_net.ansible_facts.otopi_host_net | length == 0)' failed. The error was: error while evaluating conditional ((otopi_host_net.ansible_facts.otopi_host_net | length == 0)): 'list object' has no attribute 'ansible_facts'\n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/filter_team_devices.yml': line 29, column 13, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n- debug: var=otopi_host_net\n ^ here\n\nThere appears to be both 'k=v' shorthand syntax and YAML in this task. Only one syntax may be used.\n"} [ ERROR ] Failed to execute stage 'Environment customization': Failed executing ansible-playbook The test machine node has four network CARDS, but I haven't configured the team. I don't know why, it has been suffering for several days.I don't know if you've ever been in a situation like this, other than installing a lower version.

2 1

migrating standalone engine to selfhosted and upgrade from 4.3 to 4.4 in one step
by Jiří Sléžka 11 Aug '20

11 Aug '20

Hello, I have 4 host cluster managed with standalone engine in version 4.3 and I would like to migrate this standalone engine to 4.4 as hosted engine. I have two new hosts which I would like to use as base for new HE cluster. (new hosts are Intel based, old ones are AMD Opteron based - new cluster will have 4.4 compatibility, old one have to stay at 4.2 compatibility level). I red this https://www.ovirt.org/documentation/migrating_from_a_standalone_manager_to_… but the question is: Can I migrate and upgrade in one step? Have anybody did that already? If it is not possible what is a suggested approach? Thanks for help Jiri

2 4

hosted-engine upgrade from 4.3 to 4.4 fails with "Cannot edit VM."
by d＠sekretev.ru 10 Aug '20

10 Aug '20

Hi! hosted-engine --deploy --restore-from-file=ovirt_engine_full.arch fails with [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Cannot edit VM. A VM running the engine ("hosted engine") cannot be set to highly available as it has its own HA mechanism.]". HTTP response code is 409. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Cannot edit VM. A VM running the engine (\"hosted engine\") cannot be set to highly available as it has its own HA mechanism.]\". HTTP response code is 409."} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook Can anybody help with this error? May be someone has access to this page https://access.redhat.com/solutions/5303571?

3 3

It is possible to export a vm bigger as 5 TB?
by miguel.garcia＠toshibagcs.com 10 Aug '20

10 Aug '20

We have a vm with many virtual drives and need to backup as ova file. Since this demands a lot of space I had mounted an nfs directory in the host but get next message after try to export ova: Error whle executing action: Cannot export VM. Invalid target folder: /mnt/shared2 on Host. You may refer to the engine.log file for further details. Looking at the engine.log file got this mesage: 2020-07-03 11:42:37,268-04 INFO [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-1929) [e357a397-3dc3-4566-900f-6e0e0cb39030] Lock Acquired to object 'EngineLock:{exclusiveLocks='[0b65c67d-98ae-435a-9c0a-2d9f0856a98b=VM]', sharedLocks=''}' 2020-07-03 11:42:37,275-04 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (default task-1929) [e357a397-3dc3-4566-900f-6e0e0cb39030] Executing Ansible command: /usr/bin/ansible-playbook --ssh-common-args=-F /var/lib/ovirt-engine/.ssh/config -v --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa --inventory=/tmp/ansible-inventory2275650137225503626 --extra-vars=target_directory="/nt/shared2" --extra-vars=validate_only="True" /usr/share/ovirt-engine/playbooks/ovirt-ova-export.yml [Logfile: /var/log/ovirt-engine/ova/ovirt-export-ova-validate-ansible-20200703114237-172.16.99.13-e357a397-3dc3-4566-900f-6e0e0cb39030.log] 2020-07-03 11:42:39,554-04 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (default task-1929) [e357a397-3dc3-4566-900f-6e0e0cb39030] Ansible playbook command has exited with value: 2 2020-07-03 11:42:39,555-04 WARN [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-1929) [e357a397-3dc3-4566-900f-6e0e0cb39030] Validation of action 'ExportVmToOva' failed for user Miguel.Garcia. Reasons: VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName hyp11.infra,$directory /nt/shared2 2020-07-03 11:42:39,556-04 INFO [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-1929) [e357a397-3dc3-4566-900f-6e0e0cb39030] Lock freed to object 'EngineLock:{exclusiveLocks='[0b65c67d-98ae-435a-9c0a-2d9f0856a98b=VM]', sharedLocks=''}' 2020-07-03 11:44:53,021-04 INFO [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-1937) [ba070d4b-5f76-4fd7-adc0-53e0f96e6635] Lock Acquired to object 'EngineLock:{exclusiveLocks='[0b65c67d-98ae-435a-9c0a-2d9f0856a98b=VM]', sharedLocks=''}' 2020-07-03 11:44:53,027-04 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (default task-1937) [ba070d4b-5f76-4fd7-adc0-53e0f96e6635] Executing Ansible command: /usr/bin/ansible-playbook --ssh-common-args=-F /var/lib/ovirt-engine/.ssh/config -v --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa --inventory=/tmp/ansible-inventory3629946116235444875 --extra-vars=target_directory="/mnt/shared2" --extra-vars=validate_only="True" /usr/share/ovirt-engine/playbooks/ovirt-ova-export.yml [Logfile: /var/log/ovirt-engine/ova/ovirt-export-ova-validate-ansible-20200703114453-172.16.99.13-ba070d4b-5f76-4fd7-adc0-53e0f96e6635.log] 2020-07-03 11:44:55,538-04 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (default task-1937) [ba070d4b-5f76-4fd7-adc0-53e0f96e6635] Ansible playbook command has exited with value: 2 2020-07-03 11:44:55,538-04 WARN [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-1937) [ba070d4b-5f76-4fd7-adc0-53e0f96e6635] Validation of action 'ExportVmToOva' failed for user Miguel.Garcia. Reasons: VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName hyp11.infra,$directory /mnt/shared2 2020-07-03 11:44:55,539-04 INFO [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-1937) [ba070d4b-5f76-4fd7-adc0-53e0f96e6635] Lock freed to object 'EngineLock:{exclusiveLocks='[0b65c67d-98ae-435a-9c0a-2d9f0856a98b=VM]', sharedLocks=''}' 2020-07-03 11:45:17,391-04 INFO [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-11) [6d510f0c] Lock Acquired to object 'EngineLock:{exclusiveLocks='[f762fb4b-57c1-40d0-bf3f-be4c83f16f44=PROVIDER]', sharedLocks=''}' I had tried to addthe nfs partition as a Storage Domain data type but that didn't help either. The mount persmission is as follow: drwxr-xr-x. 3 vdsm kvm 50 Jul 3 11:47 /mnt/shared2 Any idea how can export this vm?

4 5

OVA export creates empty and unusable images
by thomas＠hoberg.net 10 Aug '20

10 Aug '20

I've tested this now in three distinct farms with CentOS7.8 and the latest oVirt 4.3 release: OVA export files only contain an XML header and then lots of zeros where the disk images should be. Where an 'ls -l <vmname>.ova' shows a file about the size of the disk, 'du -h <vmname>.ova' shows mere kilobytes, 'strings <vmname>.ova' dumps the XML and then nothing but repeating zeros until the end of the file. Exporting existing VMs from a CentOS/RHEL 7 farm and importing them after a rebuild on CentOS/RHEL 8 would seem like a safe migration strategy, except when OVA export isn't working. Please treat with priority!

4 17

oVirt Hyperconverged question
by Benedetto Vassallo 10 Aug '20

10 Aug '20

Hi all, I am planning to build a 3 nodes hyperconverged system with oVirt, but I have a question. After having the system up and running with 3 nodes (compute and storage), if I need some extra compute power can I add some other "compute" (with no storage) nodes as glusterfs clients to enhance the total compute power of the cluster and using the actual storage? Thank you and Best Regards. -- Benedetto Vassallo Responsabile U.O. Sviluppo e manutenzione dei sistemi Sistema Informativo di Ateneo Università degli studi di Palermo Phone: +3909123860056 Fax: +3909123860880

3 3

Deep dive - oVirt metrics with DWH and Grafana
by Sandro Bonazzola 10 Aug '20

10 Aug '20

The oVirt project is pleased to invite you to ShirlyRadco's deep dive session on oVirt metrics with DWH and Grafana in tomorrow, August 10th 2020, premiere on YouTube at https://www.youtube.com/watch?v=8_JMIlJJ8yc&feature=youtu.be Regards, -- 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

Thin Provisioned to Preallocated
by Jorge Visentini 10 Aug '20

10 Aug '20

Hi oVirt land. Can I convert the disks of Thin Provision to Preallocated? Best Regards. -- Att, Jorge Visentini +55 55 98432-9868

5 5

Do distinct export domains share a name space? Can't export a VM, because it already exists in an unattached export domain...
by thomas＠hoberg.net 10 Aug '20

10 Aug '20

After OVA export/import was a) recommended against b) not working with the current 4.3 on CentOS 7, I am trying to make sure I keep working copies of critical VMs before I test if the OVA export now works properly, with the Redhat fix from 4.4. applied to 4.3. Long story short, I have an export domain "export", primarily attached to a 3 node HCI gluster-cluster and another domain "exportMono", primarily attached to a single node HCI gluster-cluster. Yes I use an export domain for backup, because, ...well there is no easy and working alternative out of the box, or did I overlook something? But of course, I also use an export domain for shipping between farms, so evidently I swap export domains like good old PDP-11 disk cartridges.... or at least I'd like to. I started by exporting VM "tdc" from the 1nHCI to exportMono, reattached that to 3nHCI for am import. Import worked everything fine, transfer succeed. So I detach exportMono, which belongs to the 1nHCI cluster. Next I do the OVA export on 1nHCI, but I need to get the working and reconfigured VM "tdc" out of the way on 3nHCI, so I dump it into the "export" export domain belonging to 3nHCI, because I understand I can't run two copies of the same VM on a single cluster. Turns out I can' export it, because even if the export domain is now a different one and definitely doesn't contain "tdc" at all, oVirt complains that the volume ID that belongs to "tdc" already exists in the export domain.... So what's the theory here behind export domains? And what's the state of their support in oVirt 4.4? I understand that distinct farms can't share an export domain, because they have no way of coordinating properly. Of course I tried to use one single NFS mount for both farms but the second farm properly detected the presense of another and required a distinct path. But from the evidence before me, oVirt doesn't support or like the existance of more than one export domain, either: Something that deserves a note or explanation. I understand they are deprecated in 4.3 already, but since they are also the only way to manage valuable VM images moving around, that currently works with the GUI on oVirt 4.3 it would be nice to have these questions answered.

3 3

4.4 HCI Install Failure - Missing /etc/pki/CA/cacert.pem
by Stephen Panicho 09 Aug '20

09 Aug '20

Hi all! I'm using Cockpit to perform an HCI install, and it fails at the hosted engine deploy. Libvirtd can't restart because of a missing /etc/pki/CA/cacert.pem file. The log (tasks seemingly from /usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/initial_clean.yml): [ INFO ] TASK [ovirt.hosted_engine_setup : Stop libvirt service] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Drop vdsm config statements] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restore initial abrt config files] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restart abrtd service] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Drop libvirt sasl2 configuration by vdsm] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Stop and disable services] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Restore initial libvirt default network configuration] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Start libvirt] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to start service libvirtd: Job for libvirtd.service failed because the control process exited with error code.\nSee \"systemctl status libvirtd.service\" and \"journalctl -xe\" for details.\n"} journalctl -u libvirtd: May 22 04:33:25 node1 libvirtd[26392]: libvirt version: 5.6.0, package: 10.el8 (CBS <cbs(a)centos.org>, 2020-02-27-01:09:46, ) May 22 04:33:25 node1 libvirtd[26392]: hostname: node1 May 22 04:33:25 node1 libvirtd[26392]: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory May 22 04:33:25 node1 systemd[1]: libvirtd.service: Main process exited, code=exited, status=6/NOTCONFIGURED May 22 04:33:25 node1 systemd[1]: libvirtd.service: Failed with result 'exit-code'. May 22 04:33:25 node1 systemd[1]: Failed to start Virtualization daemon. From a fresh CentOS 8.1 minimal install, I've installed the following: - The 4.4 repo - cockpit - ovirt-cockpit-dashboard - vdsm-gluster (providing glusterfs-server and allowing the Gluster Wizard to complete) - gluster-ansible-roles (only on the bootstrap host) I'm not exactly sure what that initial bit of the playbook does. Comparing the bootstrap node with another that has yet to be touched, both /etc/libvirt/libvirtd.conf and /etc/sysconfig/libvirtd are the same on both hosts. Yet the bootstrap host can no longer start libvirtd while the other host can. Neither host has the /etc/pki/CA/cacert.pem file. Please let me know if I can provide any more information. Thanks!

9 15

Why OVA imports failed (the other reason...)
by thomas＠hoberg.net 07 Aug '20

07 Aug '20

Empty disks from exports that went wrong didn't help. But that's fixed now, even if I can't fully validate the OVA exports on VMware and VirtualBox. The export/import target for the *.ova files is an SSD hosted xfs file system on a pure compute Xeon D oVirt node, exported and automounted to the 3nHCI cluster, also all SSD but J5005 Atoms. As I import the OVA file, I chose the Xeon-D as the import node and the *local path* on that host for the import. Cockpit checks the OVA file, detects the machine inside, lets me select and chose it for import, potentially overriding some parameters, lets me choose the target storage volume, sets up the job... and then fails, rather siliently and with very little in terms of error reporting ("connection closed") is the best I got. Now that same process worked just fine on a single node HCI cluster (also J5005 Atom), which had me a bit stunned at first, but gave a hint as to the cause: Parts of the input job, most likely an qemu-img job, isn't run via the machine you selected in the first step and unless the path is global (e.g. external NFS), it fails. If someone from the oVirt team could check and validate or disprove this theory, that could be documented and/or added as a check to avoid people falling into the same trap. While I was testing this using a global automount path, my cluster failed me (creating and deleting VMs a bit too quickly?) and I had to struggle for a while to have it recover. While those transient ailures are truly frightening, oVirt's ability to recover from these scenarios is quite simply awsome. I guess it's really mostly miscommunication and not real failures and oVirt has lots of logic to rectify that.

1 1

Has anyone ever had success importing an OVA VM exported from oVirt to VirtualBox or VMware? On Windows?
by thomas＠hoberg.net 07 Aug '20

07 Aug '20

After applying the OVA export patch, that ensured disk content was actually written ino the OVA image, I have been able to transfer *.ova VMs between two oVirt clusters. There are still problems that I will report once I have fully tested what's going on, but in the mean-time for all those, who want to be able to move VMs not only in the direction of oVirt (seems well tested), but also the other way (e.g. local desktop use, or even a vSphere farm) an OVA export could be a life saver--if it worked. I have tried importing oVirt exported VMs (which correctly imported and ran on a second oVirt host) both on VMware workstation 15.5.6 and VirtualBox 6.1.12 running on a Windows 2019 host without success. I've also tried untaring the *.ova into the component *.ovf + image file, but the issue seems to be with the XML description which has both imports fail pretty much instantly, before they even read the disk image file. From what I can tell, the XML created by qemu-img looks just fine, the error messages emitted by both products are very sparse and seem misleading. E.g. VirtualBox complains "Empty element ResourceType under Item element, line 1.", while I see all <Item> well constructed with a ResourceType in every one of them. VMware Workstation is completely useless in terms of log-file-diagnostics: It reports an invalid value for the "populatedSize" for the "Disk", but doesn't log that to the ovftool.log. I am pretty sure the error is in the inconsistent interpretation of this section, where the AllocationUnits, capacity and populatedSize leave some room for misinterpretation: -<DiskSection> <Info>List of Virtual Disks</Info> <Disk ovf:cinder_volume_type="" ovf:disk_storage_type="IMAGE" ovf:description="Auto-generated for Export To OVA" ovf:wipe-after-delete="false" ovf:disk-description="" ovf:disk-alias="oeight_Disk1" ovf:pass-discard="true" ovf:boot="true" ovf:disk-interface="VirtIO_SCSI" ovf:volume-type="Sparse" ovf:volume-format="RAW" ovf:format="http://www.vmware.com/specifications/vmdk.html#sparse" ovf:fileRef="974ad04f-d9bb-4881-aad2-c1d5404200ef" ovf:parentRef="" ovf:populatedSize="536953094144" ovf:capacityAllocationUnits="byte * 2^30" ovf:capacity="500" ovf:diskId="02b8d976-7e42-44e7-8e24-06f974f1c3ea"/> </DiskSection> I am trying to import the *.ova files on a Windows host and the sparsity get typically lost on the scp file transfer, too. Yes, this most likely isn't an oVirt bug, qemu-img is maintained elsewhere and the problem to me looks more on the receiver side. But have you tried it? Can you imagine it being important, too?

2 2

Re: PATCH method not allowed in imageio
by Nir Soffer 07 Aug '20

07 Aug '20

On Fri, Aug 7, 2020, 15:52 Łukasz Kołaciński <l.kolacinski(a)storware.eu> wrote: > Hello, > Thank you for previous answers. I don't have problems with checkpoints > anymore. > > I am trying to send PATCH request to imageio but it seems like I don't > have write access. In the documentation I saw that it must be a RAW format. > I think I am missing something else. > > OPTIONS Request: > { > "features": [ > "extents" > ], > "max_readers": 8, > "max_writers": 8 > } > Allow: OPTIONS,GET > > PATCH Request: > *You are not allowed to access this resource: Ticket > 485493df-b07a-495c-8aa3-824aad45b4ab forbids write* > > I created transfer using java sdk: > ImageTransfer imageTransfer = > connection.getImageTransfersSvc().addForDisk().imageTransfer( > imageTransfer() > .direction(direction) > Is this a backup? You cannot write to disks during backup. .disk(disk) > .backup(backup) > .inactivityTimeout(120) > .format(DiskFormat.RAW)) > .send().imageTransfer(); > Can you explain what are you trying to do? > It's similar to python examples. > > Best 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.* > >

1 0

PATCH method not allowed in imageio
by Łukasz Kołaciński 07 Aug '20

07 Aug '20

Hello, Thank you for previous answers. I don't have problems with checkpoints anymore. I am trying to send PATCH request to imageio but it seems like I don't have write access. In the documentation I saw that it must be a RAW format. I think I am missing something else. OPTIONS Request: { "features": [ "extents" ], "max_readers": 8, "max_writers": 8 } Allow: OPTIONS,GET PATCH Request: You are not allowed to access this resource: Ticket 485493df-b07a-495c-8aa3-824aad45b4ab forbids write I created transfer using java sdk: ImageTransfer imageTransfer = connection.getImageTransfersSvc().addForDisk().imageTransfer( imageTransfer() .direction(direction) .disk(disk) .backup(backup) .inactivityTimeout(120) .format(DiskFormat.RAW)) .send().imageTransfer(); It's similar to python examples. Best Regards Łukasz Kołaciński Junior Java Developer e-mail: l.kolacinski(a)storware.eu<mailto:l.kolacinski@storware.eu> <mailto:m.helbert@storware.eu> [STORWARE]<http://www.storware.eu/> ul. Leszno 8/44 01-192 Warszawa www.storware.eu <https://www.storware.eu/> [facebook]<https://www.facebook.com/storware> [twitter]<https://twitter.com/storware> [linkedin]<https://www.linkedin.com/company/storware> [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.

1 0

Deploy host engine error: The task includes an option with an undefined variable
by Angel R. Gonzalez 07 Aug '20

07 Aug '20

Hi all! I'm deploying a host engine in a host node with a 8x Intel(R) Xeon(R) CPU E5410 @ 2.33GHz. The deploy proccess show the next message > [INFO]TASK [ovirt.hosted_engine_setup : Convert CPU model name] > [ERROR]fatal: [localhost]: FAILED! => {"msg": "The task includes an > option with an undefined variable. The error was: 'dict object' has no > attribute ''\n\nThe error appears to be in > '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml': > line 105, column 15, but may\nbe elsewhere in the file depending on > the exact syntax problem.\n\nThe offending line appears to be:\n\n - > debug: var=server_cpu_dict\n ^ here\n\nThere appears to be both 'k=v' > shorthand syntax and YAML in this task. Only one syntax may be used.\n"} The ansible deploy script in his 105 line show: > - name: Parse server CPU list > set_fact: > server_cpu_dict: "{{ server_cpu_dict | > combine({item.split(':')[1]: item.split(':')[3]}) }}" > with_items: >- > {{ > server_cpu_list.json['values']['system_option_value'][0]['value'].split('; > ')|list|difference(['']) }} > - debug: var=server_cpu_dict I don´t know ansible and i don't how to resolve this issue. Any idea? Thanks in advance, Ángel González.

4 4

Unassigned hosts
by Nardus Geldenhuys 07 Aug '20

07 Aug '20

Hi oVirt land Hope you are well. Got a bit of an issue, actually a big issue. We had some sort of dip of some sort. All the VM's is still running, but some of the hosts is show "Unassigned" or "NonResponsive". So all the hosts was showing UP and was fine before our dip. So I did increase vdsHeartbeatInSecond to 240, no luck. I still get a timeout on the engine lock even thou I can connect to that host from the engine using nc to test to port 54321. I also did restart vdsmd and also rebooted the host with no luck. nc -v someserver 54321 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 172.40.2.172:54321. 2020-08-05 20:20:34,256+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-70) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM someserver command Get Host Capabilities failed: Message timeout which can be caused by communication issues Any troubleshoot ideas will be gladly appreciated. Regards Nar

4 14

Re: [ovirt-devel] Error during deployment of self hosted engine oVirt 4.4
by Michal Skrivanek 07 Aug '20

07 Aug '20

> On 6 Aug 2020, at 00:41, i iordanov <iiordanov(a)gmail.com> wrote: > > Hi Michal, > > I dug down enough to see that I could alter the option that specifies the supported CPUs in the database. What would have helped me is a diff of what was removed. Ultimately, I didn't have enough time to dig for the diff, but if you know where it can be found it may be of use for other people that need to use a Penryn based server. Hi, the diff is right there, the option value for 4.2 cluster still has it. so you just need that piece (penryn definition) to copy&paste into the 4.4 entry(i think the numbers are then duplicated, but it shouldn’t really matter, cpu name is the "key”) Thanks, michal > > I was able to swap two systems at my place and get a Nehalem one to use with oVirt, but if I get a chance I may try to revert to the older one since it's a bit more convenient for me to use. I would certainly try updating the DB if I could get the diff where you guys removed the line from the DB seed files. > > Cheers and thanks! > iordan > > On Tue, Aug 4, 2020 at 4:46 AM Michal Skrivanek <michal.skrivanek(a)redhat.com <mailto:michal.skrivanek@redhat.com>> wrote: > > >> On 4 Aug 2020, at 06:10, i iordanov <iiordanov(a)gmail.com <mailto:iiordanov@gmail.com>> wrote: >> >> It seems the issue stems from cpu type being empty. >> >> 'cpu': {'architecture': 'undefined', 'type': ''} >> >> 2020-08-03 23:31:39,888-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 cluster_facts: {'changed': False, 'ansible_facts': {'ovirt_clusters': [{'href': '/ovirt-engine/api/clusters/0eb77d38-d5fe-11ea-8808-00163e42a94a', 'comment': '', 'description': 'The default server cluster', 'id': '0eb77d38-d5fe-11ea-8808-00163e42a94a', 'name': 'Default', 'affinity_groups': [], 'ballooning_enabled': True, 'bios_type': 'cluster_default', 'cpu': {'architecture': 'undefined', 'type': ''}, 'cpu_profiles': [], 'data_center': {'href': '/ovirt-engine/api/datacenters/0ea3b60e-d5fe-11ea-a87c-00163e42a94a', 'id': '0ea3b60e-d5fe-11ea-a87c-00163e42a94a'}, 'enabled_features': [], 'error_handling': {'on_error': 'migrate'}, 'external_network_providers': [], 'fencing_policy': {'enabled': True, 'skip_if_connectivity_broken': {'enabled': False, 'threshold': 50}, 'skip_if_gluster_bricks_up': False, 'skip_if_gluster_quorum_not_met': False, 'skip_if_sd_active': {'enabled': False}}, 'firewall_type': 'firewalld', 'gluster_hooks': [], 'gluster_service': False, 'gluster_volumes': [], 'ha_reservation': False, 'ksm': {'enabled': True, 'merge_across_nodes': True}, 'log_max_memory_used_threshold': 95, 'log_max_memory_used_threshold_type': 'percentage', 'mac_pool': {'href': '/ovirt-engine/api/macpools/58ca604b-017d-0374-0220-00000000014e', 'id': '58ca604b-017d-0374-0220-00000000014e'}, 'memory_policy': {'over_commit': {'percent': 100}, 'transparent_huge_pages': {'enabled': True}}, 'migration': {'auto_converge': 'inherit', 'bandwidth': {'assignment_method': 'auto'}, 'compressed': 'inherit', 'encrypted': 'inherit', 'policy': {'id': '80554327-0569-496b-bdeb-fcbbf52b827b'}}, 'network_filters': [], 'networks': [], 'permissions': [], 'required_rng_sources': ['urandom'], 'scheduling_policy': {'href': '/ovirt-engine/api/schedulingpolicies/b4ed2332-a7ac-4d5f-9596-99a439cb2812', 'id': 'b4ed2332-a7ac-4d5f-9596-99a439cb2812'}, 'switch_type': 'legacy', 'threads_as_cores': False, 'trusted_service': False, 'tunnel_migration': False, 'version': {'major': 4, 'minor': 4}, 'virt_service': True, 'vnc_encryption': False}]}, 'deprecations': [{'msg': "The 'ovirt_cluster_facts' module has been renamed to 'ovirt_cluster_info', and the renamed one no longer returns ansible_facts", 'version': '2.13'}], 'failed': False} >> >> Perhaps this Penryn series CPU is too old for this oVirt installation... > > Yes, we dropped Penryn from supported CPU list i 4.3. You could probably stil make it run but it would need messing with engine’s db, adding back Nehalem entry to ServerCPUList(e.g. from 4.2 cluster version line) and resume the deployment somehow. > >> >> iordan >> >> On Mon, Aug 3, 2020 at 11:54 PM i iordanov <iiordanov(a)gmail.com <mailto:iiordanov@gmail.com>> wrote: >> Hi guys, >> >> I am trying to install oVirt 4.4 for testing of the aSPICE and Opaque Android clients and tried to follow this slightly outdated doc: >> >> https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engin… <https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engin…> >> >> to deploy an all-in-one self-hosted engine using the command-line. >> >> I started with a clean CentOS 8 installation, set up an NFS server and tested that mounts work from the local host and other hosts, opened all ports with firewalld to my LAN and localhost (but left firewalld enabled). >> >> During the run of >> hosted-engine --deploy >> I got the following error: >> >> 2020-08-03 23:31:51,426-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 TASK [ovirt.hosted_engine_setup : debug] >> 2020-08-03 23:31:51,827-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 server_cpu_dict: {'Intel Nehalem Family': 'Nehalem', 'Secure Intel Nehalem Family': 'Nehalem,+sp >> ec-ctrl,+ssbd,+md-clear', 'Intel Westmere Family': 'Westmere', 'Secure Intel Westmere Family': 'Westmere,+pcid,+spec-ctrl,+ssbd,+md-clear', 'Intel SandyBridge Family': 'SandyBridge', 'Secure Intel SandyBridge Fa >> mily': 'SandyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear', 'Intel IvyBridge Family': 'IvyBridge', 'Secure Intel IvyBridge Family': 'IvyBridge,+pcid,+spec-ctrl,+ssbd,+md-clear', 'Intel Haswell Family': 'Haswell-noTSX >> ', 'Secure Intel Haswell Family': 'Haswell-noTSX,+spec-ctrl,+ssbd,+md-clear', 'Intel Broadwell Family': 'Broadwell-noTSX', 'Secure Intel Broadwell Family': 'Broadwell-noTSX,+spec-ctrl,+ssbd,+md-clear', 'Intel Sk >> ylake Client Family': 'Skylake-Client,-hle,-rtm', 'Secure Intel Skylake Client Family': 'Skylake-Client,+spec-ctrl,+ssbd,+md-clear,-hle,-rtm', 'Intel Skylake Server Family': 'Skylake-Server,-hle,-rtm', 'Secure I >> ntel Skylake Server Family': 'Skylake-Server,+spec-ctrl,+ssbd,+md-clear,-hle,-rtm', 'Intel Cascadelake Server Family': 'Cascadelake-Server,-hle,-rtm,+arch-capabilities', 'Secure Intel Cascadelake Server Family': >> 'Cascadelake-Server,+md-clear,+mds-no,-hle,-rtm,+tsx-ctrl,+arch-capabilities', 'AMD Opteron G4': 'Opteron_G4', 'AMD Opteron G5': 'Opteron_G5', 'AMD EPYC': 'EPYC', 'Secure AMD EPYC': 'EPYC,+ibpb,+virt-ssbd', 'IB >> M POWER8': 'POWER8', 'IBM POWER9': 'POWER9', 'IBM z114, z196': 'z196-base', 'IBM zBC12, zEC12': 'zEC12-base', 'IBM z13s, z13': 'z13-base', 'IBM z14': 'z14-base'} >> 2020-08-03 23:31:52,128-0400 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 TASK [ovirt.hosted_engine_setup : Convert CPU model name] >> 2020-08-03 23:31:52,530-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 {'msg': "The task includes an option with an undefined variable. The error was: 'dict object' ha >> s no attribute ''\n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml': line 105, column 15, but may\nbe elsewhere in th >> e file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n - debug: var=server_cpu_dict\n ^ here\n\nThere appears to be both 'k=v' shorthand syntax and YAML in this task >> . Only one syntax may be used.\n", '_ansible_no_log': False} >> 2020-08-03 23:31:52,630-0400 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:107 fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable. >> The error was: 'dict object' has no attribute ''\n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml': line 105, column >> 15, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n - debug: var=server_cpu_dict\n ^ here\n\nThere appears to be both 'k=v' shortha >> nd syntax and YAML in this task. Only one syntax may be used.\n"} >> 2020-08-03 23:31:52,931-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 PLAY RECAP [localhost] : ok: 35 changed: 5 unreachable: 0 skipped: 5 failed: 1 >> 2020-08-03 23:31:53,032-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:215 ansible-playbook rc: 2 >> 2020-08-03 23:31:53,032-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:222 ansible-playbook stdout: >> 2020-08-03 23:31:53,032-0400 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:225 ansible-playbook stderr: >> 2020-08-03 23:31:53,033-0400 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/target_vm.py", line 238, 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')) >> RuntimeError: Failed executing ansible-playbook >> 2020-08-03 23:31:53,034-0400 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Closing up': Failed executing ansible-playbook >> >> On line 105 of the Ansible config file indicated, there is the following task: >> - debug: var=server_cpu_dict >> >> However, here is a bit more of the file: >> - name: Parse server CPU list >> set_fact: >> server_cpu_dict: "{{ server_cpu_dict | combine({item.split(':')[1]: item.split(':')[3]}) }}" >> with_items: >- >> {{ server_cpu_list.json['values']['system_option_value'][0]['value'].split('; ')|list|difference(['']) }} >> - debug: var=server_cpu_dict >> - name: Convert CPU model name >> set_fact: >> cluster_cpu_model: "{{ server_cpu_dict[cluster_cpu.type] }}" >> - debug: var=cluster_cpu_model >> - name: Parse emulated_machine >> set_fact: >> emulated_machine: >> emulated_machine_list.json['values']['system_option_value'][0]['value'].replace( >> '[','').replace(']','').split(', ')|first >> >> Exact version of the package that contains the file in question: >> >> ovirt-ansible-hosted-engine-setup-1.1.7-1.el8.noarch >> >> Many thanks for your attention! Please cc me when you reply, as I may not be monitoring the mailing list actively. Happy to provide any other information. >> >> In case it's relevant, the CPU of the machine: >> >> # cat /proc/cpuinfo >> processor : 0 >> vendor_id : GenuineIntel >> cpu family : 6 >> model : 23 >> model name : Intel(R) Xeon(R) CPU X5460 @ 3.16GHz >> stepping : 6 >> microcode : 0x60f >> cpu MHz : 2703.129 >> cache size : 6144 KB >> physical id : 0 >> siblings : 4 >> core id : 0 >> cpu cores : 4 >> apicid : 0 >> initial apicid : 0 >> fpu : yes >> fpu_exception : yes >> cpuid level : 10 >> wp : yes >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm pti tpr_shadow vnmi flexpriority dtherm >> bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit >> bogomips : 6318.15 >> clflush size : 64 >> cache_alignment : 64 >> address sizes : 38 bits physical, 48 bits virtual >> power management: >> >> Sincerely, >> iordan >> >> -- >> The conscious mind has only one thread of execution. >> >> >> -- >> The conscious mind has only one thread of execution. >> _______________________________________________ >> Devel mailing list -- devel(a)ovirt.org <mailto:devel@ovirt.org> >> To unsubscribe send an email to devel-leave(a)ovirt.org <mailto:devel-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/devel@ovirt.org/message/4CUXHTZTTAW6Y… <https://lists.ovirt.org/archives/list/devel@ovirt.org/message/4CUXHTZTTAW6Y…> > > > -- > The conscious mind has only one thread of execution.

1 0

oVirt 4.4.1 HCI single server deployment failed nested-kvm
by wodel youchi 07 Aug '20

07 Aug '20

Hi, I am using these versions for my test : - ovirt-engine-appliance-4.4-20200723102445.1.el8.x86_64.rpm - ovirt-node-ng-installer-4.4.1-2020072310.el8.iso A single HCI server using nested KVM. The gluster part works now without error, but when I click the hosted-engine deployment button I get : *System data could not be retrieved!* *No valid network interface has been found * * If you are using Bonds or VLANs Use the following naming conventions: * - VLAN interfaces: physical_device.VLAN_ID (for example, eth0.23, eth1.128, enp3s0.50) - Bond interfaces: bond*number* (for example, bond0, bond1) - VLANs on bond interfaces: bond*number*.VLAN_ID (for example, bond0.50, bond1.128) * Supported bond modes: active-backup, balance-xor, broadcast, 802.3ad * Networking teaming is not supported and will cause errors From this log file I get : cat ovirt-hosted-engine-setup-ansible-get_network_interfaces-xxxxxxxx.log 2020-07-29 15:27:09,246+0100 DEBUG var changed: host "localhost" var "otopi_host_net" type "<class 'list'>" value: "[ "enp1s0", "enp2s0" ]" 2020-07-29 15:27:09,246+0100 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-eng ine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': 'Filter unsupported interface types', 'task_duration ': 0} 2020-07-29 15:27:09,246+0100 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe804bc5940> kwargs 2020-07-29 15:27:09,514+0100 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-ho sted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.hosted_engine_setup : debug'} 2020-07-29 15:27:09,515+0100 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : debug kwargs is_conditional:False 2020-07-29 15:27:09,515+0100 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : debug kwargs 2020-07-29 15:27:09,792+0100 INFO ansible ok {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-eng ine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost', 'ansible_task': '', 'task_duration': 0} 2020-07-29 15:27:09,793+0100 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe804cb45f8> kwargs 2020-07-29 15:27:10,059+0100 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-ho sted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.hosted_engine_setup : Failed if only teaming devices are availible '} 2020-07-29 15:27:10,059+0100 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Failed if only teaming devices are availible kwargs is_conditional:False 2020-07-29 15:27:10,060+0100 DEBUG ansible on_any args localhostTASK: ovirt.hosted_engine_setup : Failed if only teaming devices are a vailible kwargs 2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var "ansible_play_hosts" type "<class 'list'>" value: "[]" 2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var "ansible_play_batch" type "<class 'list'>" value: "[]" 2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var "play_hosts" type "<class 'list'>" value: "[]" 2020-07-29 15:27:10,376+0100 ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": false, "msg": "The conditional check *'(otopi_host_net.ansible_facts.otopi_host_net | length == 0)' failed. The error was: error while evaluating conditional ((otopi_host_net.ansible_facts.otopi_host_net | length == 0)): 'list object' has no attribute 'ansible_facts'\n\nThe error appears to be in '/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/filter_team_devices.yml': line 29, column 13, * but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n- debug: var=otopi_ho st_net\n ^ here\n\nThere appears to be both 'k=v' shorthand syntax and YAML in this task. Only one syntax may be used.\n" }, "ansible_task": "Failed if only teaming devices are availible", "ansible_type": "task", "status": "FAILED", "task_duration": 0 } 2020-07-29 15:27:10,377+0100 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fe804c175c0> kwargs ignor e_errors:None 2020-07-29 15:27:10,378+0100 INFO ansible stats { "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_playbook_duration": "00:15 Minutes", "ansible_result": "type: <class 'dict'>\nstr: {'localhost': {'ok': 16, 'failures': 1, 'unreachable': 0, 'changed': 1, 'skipped': 2 , 'rescued': 0, 'ignored': 0}}", "ansible_type": "finish", "status": "FAILED" } 2020-07-29 15:27:10,378+0100 INFO SUMMARY: Duration Task Name -------- -------- [ < 1 sec ] Execute just a specific set of steps [ 00:02 ] Force facts gathering [ 00:01 ] Get all active network interfaces [ < 1 sec ] Filter bonds with bad naming [ < 1 sec ] Generate output list [ 00:01 ] Collect interface types [ < 1 sec ] Get list of Team devices [ < 1 sec ] Filter unsupported interface types [ FAILED ] Failed if only teaming devices are availible 2020-07-29 15:27:10,378+0100 DEBUG ansible on_any args <ansible.executor.stats.AggregateStats object at 0x7fe8074bce80> kwargs Regards.

6 8

Setting Up oVirt + NFS Storage Issues
by Arden Shackelford 07 Aug '20

07 Aug '20

Hello! Been looking to get setup with oVirt for a few weeks and had a chance the past week or so to attempt getting it all setup. Ended up doing a bit of troubleshooting but finally got to the point where the Cockpit setup prompts for me setting up the storage piece, for which I've opted for NFS (path of least resistance for now). However, I constantly run into this issue (pulled from the administration portal events page): VDSM asgard.shackfam.net command CreateStorageDomainVDS failed: Could not initialize cluster lock: () This specifically shows up in the following task for the Ansible piece: [ovirt.hosted_engine_setup : Add NFS storage domain] When I browse the NFS share, I do see a file structure being created, which kind of confuses me based on the error provide in the Administration portal. Any suggestions on what would be best steps forward at this point? For reference, here's my setup: 1x oVirt Node 1x NFS server (storage01: NFS shares mainly managed by ZFS)

3 5

4.2.8 and yum update
by carl langlois 06 Aug '20

06 Aug '20

Hi all, I am in the process of upgrading our cluster to 4.3. But first i need to update everything to 4.2.8 and update the os to the latest 7.x. I was able to update the self-hosted engine to the latest 4.2.8 and centos 7.8. But when i tried to update the host yum update got broken gluster packages. The current host that i'm trying to update is on 7.5. If i look at the release note i can see that ovirt 4.2.8 needs 7.6. Not sure how to resolve this. Any suggestions?. Carl

2 6

[ANN] oVirt 4.4.2 Second Release Candidate is now available for testing
by Lev Veyde 06 Aug '20

06 Aug '20

oVirt 4.4.2 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.2 Second Release Candidate for testing, as of August 6th, 2020. This update is the second in a series of stabilization updates to the 4.4 series. 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 the engine: either use appliance or: - Install CentOS Linux 8.2 minimal from: https://mirrors.edge.kernel.org/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004… - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps postgresql:12 - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8.2 from https://mirrors.edge.kernel.org/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004… ; select minimal installation - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - Attach the host to the engine and let it be deployed. 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.2 release highlights: http://www.ovirt.org/release/4.4.2/ * 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.2/ [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: VDSM can't see StoragePool
by Nardus Geldenhuys 06 Aug '20

06 Aug '20

Hi Hope you are well. Did you find a solution for this? Think we have the same type of issue. Regards Nar

1 0

useful workaround for catch-22 situation with nic drivers and Windows
by i iordanov 06 Aug '20

06 Aug '20

Hello, I just wanted to post a nice workaround I came up with in case it helps anybody. The reason I needed it is that in oVirt 4.4, it appears I am unable to change the nic1 type when creating VMs (maybe that's a bug?) and I necessarily end up with the default nic1 type which needs a virtio driver in Windows which is obviously not present on a clean install. Also, since there is no networking, it can't be downloaded. I did think of mounting a USB stick via remote-viewer, but something is wonky there too - the USB device selection menu item is grayed out, and no, it's not permissions. So what i did was to create an .iso file with spice-guest-tools-latest.exe in it and copy the resulting iso file to the ISO domain. Then, I was easily able to attach the ISO to the Windows machine in question and install spice-guest-tools, which made the network adapter work. Quick snippet of how I created the .iso: $ find test test test/spice-guest-tools-latest.exe $ mkisofs -o spice-tools.iso test I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 0 Total directory bytes: 116 Path table size(bytes): 10 Max brk space used 0 5124 extents written (10 MB) Hope it helps somebody :). Cheers! iordan -- The conscious mind has only one thread of execution.

2 1

Resize partition cause oVirt installation failed
by hkexdong＠yahoo.com.hk 06 Aug '20

06 Aug '20

I've 2 x 512GB SSD. Purely for oVirt 4.4.1 (CentOS 8.2) installation. Using auto partitioning will assign 800+ GB to root partition. I think that's too much so manually reduce it to 80 GB. As there are 2 disks. I want to form RAID too. So, I manually change all the partitions from "LVM thin provisioning" to "RAID" (with RAID 1). Eventually, cause the installation failed with a message "There was an error running the kickstart script at line ....." If I don't make any change to the partitions. The installation success. Is this a known issue? oVirt not allow resize partition and using Linux software RAID?

4 5

General Design question for oVirt set up between locations
by Holger Petrick 05 Aug '20

05 Aug '20

Hello, I'm looking to deploy oVirt for a company which has locations in different countries. As I know and also set up in my test environment, the oVirt Engine is the central place to manage different Data Center in a central place. But how to manage a location when the network connection between a Data Center and oVirt Engine is down? Is it possible to set up on each location a hosted engine and connect also the "local" engine / hosts to a "Central" Engine? What is the recommendation to deploy oVirt on multiple location? Thank you. Holger

2 2

Semi off-topic: invalid SPF record for ovirt.org
by Chris Adams 05 Aug '20

05 Aug '20

Not sure where to send this (so sending to the list); the ovirt.org SPF record is invalid: $ dig ovirt.org txt +short "v=spf1 a:mail.ovirt.org a:gerrit.ovirt.org 66.187.233.88 ~all" The bare IP address needs to be "ip4:66.187.233.88" instead. -- Chris Adams <cma(a)cmadams.net>

2 1

Subject: [ANN] Updated oVirt release 4.4.1.5
by Lev Veyde 05 Aug '20

05 Aug '20

The oVirt Team has just released a new version of oVirt Node package that fixes oVirt Hyperconverged deployment related issue: Bug 1862588 <https://bugzilla.redhat.com/show_bug.cgi?id=1862588> - Update to gluster-7.7 with ovirt-ng node 4.4.1 Updated ovirt-node-ng-installer had been built and a new torrent for this ISO is now available at https://resources.ovirt.org/pub/ovirt-4.4/iso/ovirt-node-ng-installer/4.4.1… Relevant changes compared to previous version: - Gluster 7.7: https://docs.gluster.org/en/latest/release-notes/7.7/ - Ansible 2.9.11: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Boot Hole vulnerability in grub2 (CVE-2020-1073) fix: https://blog.centos.org/2020/08/centos-community-newsletter-august-2020-200… -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Unable to start vms in a specific host
by miguel.garcia＠toshibagcs.com 04 Aug '20

04 Aug '20

I had added a couple new hosts in my cluster (hyp16,hyp17) both followed the same procedure but at the moment to start vms all of them goes to hyp16, if I tried to migrate a vm to hyp 17 the migration task fails. Here is the log trying to do migration: 2020-07-22 17:19:12,352-04 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] Running command: MigrateVmToServerCommand internal: false. Entities affected : ID: 24939bc1-5359-4f9d-b742-b32143c02eb1 Type: VMAction group MIGRATE_VM with role type USER 2020-07-22 17:19:12,421-04 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] START, MigrateVDSCommand( MigrateVDSCommandParameters:{hostId='15466e1a-1f44-472c-94fc-84b132ff1c7d', vmId='24939bc1-5359-4f9d-b742-b32143c02eb1', srcHost='172.16.99.12', dstVdsId='3663f46b-61db-4b4c-a6c0-03fedc90edf0', dstHost='172.16.99.19:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', consoleAddress='null', maxBandwidth='625', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=ab ort, params=[]}}]]', dstQemu='172.16.99.19'}), log id: 4f624ae2 2020-07-22 17:19:12,423-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] START, MigrateBrokerVDSCommand(HostName = hyp10.infra, MigrateVDSCommandParameters:{hostId='15466e1a-1f44-472c-94fc-84b132ff1c7d', vmId='24939bc1-5359-4f9d-b742-b32143c02eb1', srcHost='172.16.99.12', dstVdsId='3663f46b-61db-4b4c-a6c0-03fedc90edf0', dstHost='172.16.99.19:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', consoleAddress='null', maxBandwidth='625', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntim e, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='172.16.99.19'}), log id: 7ead484c 2020-07-22 17:19:12,587-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] FINISH, MigrateBrokerVDSCommand, return: , log id: 7ead484c 2020-07-22 17:19:12,589-04 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] FINISH, MigrateVDSCommand, return: MigratingFrom, log id: 4f624ae2 2020-07-22 17:19:12,597-04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-2378) [35ab9442-856d-4540-a463-d72d1211867f] EVENT_ID: VM_MIGRATION_START(62), Migration started (VM: Test, Source: hyp10.infra, Destination: hyp17.infra, User: Miguel.Garcia@). 2020-07-22 17:19:14,050-04 INFO [org.ovirt.engine.core.sso.servlets.OAuthRevokeServlet] (default task-2378) [] User antonio.acosta@ successfully logged out 2020-07-22 17:19:14,069-04 INFO [org.ovirt.engine.core.bll.aaa.TerminateSessionsForTokenCommand] (default task-2380) [27d07a90] Running command: TerminateSessionsForTokenCommand internal: true. 2020-07-22 17:19:14,405-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-12) [] VM '24939bc1-5359-4f9d-b742-b32143c02eb1' was reported as Down on VDS '3663f46b-61db-4b4c-a6c0-03fedc90edf0'(hyp17.infra) 2020-07-22 17:19:14,406-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-12) [] START, DestroyVDSCommand(HostName = hyp17.infra, DestroyVmVDSCommandParameters:{hostId='3663f46b-61db-4b4c-a6c0-03fedc90edf0', vmId='24939bc1-5359-4f9d-b742-b32143c02eb1', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 7d54e8da 2020-07-22 17:19:14,823-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-12) [] Failed to destroy VM '24939bc1-5359-4f9d-b742-b32143c02eb1' because VM does not exist, ignoring 2020-07-22 17:19:14,823-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-12) [] FINISH, DestroyVDSCommand, return: , log id: 7d54e8da 2020-07-22 17:19:14,824-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-12) [] VM '24939bc1-5359-4f9d-b742-b32143c02eb1'(Test) was unexpectedly detected as 'Down' on VDS '3663f46b-61db-4b4c-a6c0-03fedc90edf0'(hyp17.infra) (expected on '15466e1a-1f44-472c-94fc-84b132ff1c7d') 2020-07-22 17:19:14,824-04 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-12) [] Migration of VM 'Test' to host 'hyp17.infra' failed: VM destroyed during the startup. 2020-07-22 17:19:14,824-04 WARN [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (ForkJoinPool-1-worker-3) [] skipping VM '24939bc1-5359-4f9d-b742-b32143c02eb1' from this monitoring cycle - the VM data has changed since fetching the data 2020-07-22 17:19:17,224-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [] VM '24939bc1-5359-4f9d-b742-b32143c02eb1'(Test) moved from 'MigratingFrom' --> 'Up' 2020-07-22 17:19:17,224-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [] Adding VM '24939bc1-5359-4f9d-b742-b32143c02eb1'(Test) to re-run list 2020-07-22 17:19:17,229-04 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [] Rerun VM '24939bc1-5359-4f9d-b742-b32143c02eb1'. Called from VDS 'hyp10.infra' 2020-07-22 17:19:17,310-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-12994) [] START, MigrateStatusVDSCommand(HostName = hyp10.infra, MigrateStatusVDSCommandParameters:{hostId='15466e1a-1f44-472c-94fc-84b132ff1c7d', vmId='24939bc1-5359-4f9d-b742-b32143c02eb1'}), log id: 74cf526d 2020-07-22 17:19:17,533-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-12994) [] FINISH, MigrateStatusVDSCommand, return: , log id: 74cf526d 2020-07-22 17:19:17,587-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-12994) [] EVENT_ID: VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed (VM: Test, Source: hyp10.infra, Destination: hyp17.infra). 2020-07-22 17:19:17,591-04 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (EE-ManagedThreadFactory-engine-Thread-12994) [] Lock freed to object 'EngineLock:{exclusiveLocks='[24939bc1-5359-4f9d-b742-b32143c02eb1=VM]', sharedLocks=''}'

2 2

4.4rc issue with attaching logical network to ib0
by Edward Berger 04 Aug '20

04 Aug '20

I'm trying to add a logical network to an omnipath (which appears as an infinband ib0 under centos kernel driver) and the attempt errors out, under 4.4RC. This used to work under 4.3 on the same hardware. 'Unexpected failure of libnm when running the mainloop: run execution'}, code = -32603 I want to use ib0 for network file systems and VM migrations.

2 3

Windows TimeZone UTC
by Erez Zarum 04 Aug '20

04 Aug '20

The Engine has the TimeZone types compiled, this may be an issue when one wants to configure a Windows Machine to use UTC as a Timezone instead of GMT. Using GMT sets the Windows VM to "London, Dublin" time which may cause issues with daylight saving for some users. There should be an option to supply our own Timezone or the least, make sure it is indeed coordinated with what Windows supports.

4 8

error importing from VMware, and workaround
by Philip Brown 04 Aug '20

04 Aug '20

more details in my saga of problem imports from VMware/vsphere to ovirt (4.4.1 node) I had done a couple successfully, but my next one kept failing. Couldnt figure out why. The only things resembling an error in the import logs, were this: (trimmed a bit) "rpm -e vmware-tools-nox vmware-tools-common" { "message": "libguestfs error: command: error: Failed dependencies:\n\tvmware-tools-nox = 8.3.19 is needed by (installed) vmware-tools-8.3.19-1310361.el6.x86_64", "timestamp": "2020-08-02T21:28:08.797433658+00:00", "type": "error" } I thought to myself.. nah, that couldnt be it. import failed.. because you couldnt REMOVE a package??? that would be dumb. but that was the problem. I started up the old vm, did a yum remove 'vmware-*' reexported from VMware, and then imported... and this time, the import worked. Please fix that behaviour. -- Philip Brown| Sr. Linux System Administrator | Medata, Inc. 5 Peters Canyon Rd Suite 250 Irvine CA 92606 Office 714.918.1310| Fax 714.918.1325 pbrown(a)medata.com| www.medata.com

3 2

oVirt 4.4 Self-Hosted Installation failed
by enmanuelmoreira＠gmail.com 04 Aug '20

04 Aug '20

Hi There! I'm trying to install oVirt self-hosted on Fedora 32 with kvm and the install failed. I got the following message on ovirt console: Host localhost installation failed. Failed to execute Ansible host-deploy role: failed. Please check logs for more details: /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20200727183159-localhost-5de7c489.log. and the log content: [root@localhost ~]# tail -100 /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20200727183159-localhost-5de7c489.log "end" : "2020-07-27 18:35:18.688022", "delta" : "0:00:00.190619", "changed" : true, "invocation" : { "module_args" : { "_raw_params" : "'/usr/bin/openssl'\n'req'\n'-new'\n'-newkey'\n'rsa:2048'\n'-nodes'\n'-subj'\n'/'\n'-keyout'\n'/tmp/ansible.oqj_hat2qemu'\n", "warn" : true, "_uses_shell" : false, "stdin_add_newline" : true, "strip_empty_ends" : true, "argv" : null, "chdir" : null, "executable" : null, "creates" : null, "removes" : null, "stdin" : null } }, "stdout_lines" : [ "-----BEGIN CERTIFICATE REQUEST-----", "MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL++", "QCG8gpsb3isdQFw/noaoOIGxd6zXcoCMdPs2vOP8z7ciPSQPE5r6JxmNTM9tMzCb", "b1sC7ON8PJNaMyRTQ1mVGFoQhQIq54L77GwV27qzVlsjmfM3MCUISVqTGZPWJ/RQ", "QVc03RXDbLYC0UG7C5Y+NRCp7G+67/dLjvzyO4IASZH1rEE7K/PPjSsyJJYaq68X", "XeyckgB7kjQXYZCIexihH3lvMvp7j75wc0RZztEw2bGhhByVsTZCvgouciL/43N7", "h2/8pMZaNbIcx5h8ZIoyWWvYGCe2PaALd94jSLjrgwY6v8lHSt/5S96Ace/C2jt6", "WDwbTfFvthyIosxJRdkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBp0Mj1WO4h", "n27hRFQ5n2hwRpLrbnD/KIkicNR9sFPszAMt6cN84a5jocrSJEcboPnz/Bg1yNlq", "FsN6gVI/RQY7BTmgP5chThe+/vtCJjP71K/+5YKpaBCbtpUIo/dERzHMsVS5O730", "iXjFERxAObnrzllohpahc42+dwxPrd4ZMFrRmA5m55/nN9VgCudHTo8Uzrv+iaN7", "0G3oPW1IJGnycUArYyGPOIXTHMWRKcxF4irPOxXCp3cyWKxrfrO7vrl8LfOvVsJx", "btRN84AUvUsSPzFDVPuAl8xZ9M0P+Ho9uGvSMlQ0xdyfXU/9wFIhf3oFK3Slbo3j", "rXgOHdj+ve1g", "-----END CERTIFICATE REQUEST-----" ], "stderr_lines" : [ "Generating a RSA private key", "....................................................................................................................................................+++++", ".....................................+++++", "writing new private key to '/tmp/ansible.oqj_hat2qemu'", "-----" ], "_ansible_no_log" : false, "failed" : false, "item" : { "changed" : true, "path" : "/tmp/ansible.oqj_hat2qemu", "uid" : 0, "gid" : 0, "owner" : "root", "group" : "root", "mode" : "0600", "state" : "file", "secontext" : "unconfined_u:object_r:user_tmp_t:s0", "size" : 0, "invocation" : { "module_args" : { "state" : "file", "suffix" : "qemu", "prefix" : "ansible.", "path" : null } }, "failed" : false, "item" : { "suffix" : "qemu", "pending_file" : "libvirt-migrate/server-key.pending.pem", "req_dir" : "requests-qemu" }, "ansible_loop_var" : "item" }, "ansible_loop_var" : "item", "_ansible_item_label" : { "changed" : true, "path" : "/tmp/ansible.oqj_hat2qemu", "uid" : 0, "gid" : 0, "owner" : "root", "group" : "root", "mode" : "0600", "state" : "file", "secontext" : "unconfined_u:object_r:user_tmp_t:s0", "size" : 0, "invocation" : { "module_args" : { "state" : "file", "suffix" : "qemu", "prefix" : "ansible.", "path" : null } }, "failed" : false, "item" : { "suffix" : "qemu", "pending_file" : "libvirt-migrate/server-key.pending.pem", "req_dir" : "requests-qemu" }, "ansible_loop_var" : "item" } } ], "changed" : true, "msg" : "All items completed" }, "start" : "2020-07-27T18:35:18.064749", "end" : "2020-07-27T18:35:18.714265", "duration" : 0.649516, "event_loop" : null, "uuid" : "ce9afcb5-6c75-44a8-a640-5152a8605b52" } } } 2020-07-27 18:35:20 UTC - TASK [ovirt-host-deploy-vdsm-certificates : Copy vdsm and QEMU CSRs] *********** 2020-07-27 18:35:20 UTC - 2020-07-27 18:35:20 UTC - [WARNING]: The loop variable 'item' is already in use. You should set the `loop_var` value in the `loop_control` option for the task to something else to avoid variable collisions and unexpected behavior. 2020-07-27 18:35:20 UTC - failed: [localhost] (item={'cmd': ['/usr/bin/openssl', 'req', '-new', '-newkey', 'rsa:2048', '-nodes', '-subj', '/', '-keyout', '/tmp/ansible.sksg5y_jvdsm'], 'stdout': '-----BEGIN CERTIFICATE REQUEST-----\nMIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMo1\nIRs7qJtcFrVWc56TpJlxh54cPlLxASA/Xdu78vkNz4/eLL6Fyud5/mSloHeLuHat\nJcvwxmLWcWDeNcEWlMR9tJTA6WxCS2rvUXXFNkw9QCUtTB9qrmezujdOTbDP4eqO\n/i0/xn0BO+kizB7SPMt3uyLJKAOCefcUwvmMEwZ25nw8oCqf/gICl/0AGKphuP11\nH1HuK5x8CTxboO2LawccpRUcbBXn5vF4LRsxy/VuK4fPMnxTk52F0DKwZMfnM4i6\npBnl7rI0P9JUDBlt2clYhz5fy4/unZmNYiyYpfkfv+YB66/vsFA/Hsa4DdWkYfE0\n0FBpOR5ANVOMselvFC0CAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQAYQRPcLLqq\nKH9RkEZj/i6WPQWGBUbTmRS2e1uFhRLwVUgaX9yK84m/IS1w7X3JrYuykAh3nGjs\n955U7XqA28nt/VZqB9xXYvmmfhGNFVNphUa/YecBb7OilUlReuRjCugcR6s3JiKM\nVppr6iKxCYzooOiSsMJk7VSSWz2V7k4CGj4vD/1GX/BH9j2J9Xa4uvw0bmZf467q\nKqUhpTw2T/DFg4b+dFjmyjbmjZTLrpfA2xBXGJQMrnHv3v9ca8WlX/zDhZDfEycY\nHIgw9y+I6S0ZTKmzpCMzwpPUOny6StZcPWjKZGCV tLq1slpCHEH9T8++RdX/9Gn8\nyU7Y/+iqZ/Us\n-----END CERTIFICATE REQUEST-----', 'stderr': "Generating a RSA private key\n......+++++\n.............................+++++\nwriting new private key to '/tmp/ansible.sksg5y_jvdsm'\n-----", 'rc': 0, 'start': '2020-07-27 18:35:18.270606', 'end': '2020-07-27 18:35:18.314757', 'delta': '0:00:00.044151', 'changed': True, 'invocation': {'module_args': {'_raw_params': "'/usr/bin/openssl'\n'req'\n'-new'\n'-newkey'\n'rsa:2048'\n'-nodes'\n'-subj'\n'/'\n'-keyout'\n'/tmp/ansible.sksg5y_jvdsm'\n", 'warn': True, '_uses_shell': False, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': ['-----BEGIN CERTIFICATE REQUEST-----', 'MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMo1', 'IRs7qJtcFrVWc56TpJlxh54cPlLxASA/Xdu78vkNz4/eLL6Fyud5/mSloHeLuHat', 'JcvwxmLWcWDeNcEWlMR9tJTA6WxCS2rvUXXFNkw9QCUtTB9qrmezujdOTbDP4eqO', '/i0/xn0BO+kizB7S PMt3uyLJKAOCefcUwvmMEwZ25nw8oCqf/gICl/0AGKphuP11', 'H1HuK5x8CTxboO2LawccpRUcbBXn5vF4LRsxy/VuK4fPMnxTk52F0DKwZMfnM4i6', 'pBnl7rI0P9JUDBlt2clYhz5fy4/unZmNYiyYpfkfv+YB66/vsFA/Hsa4DdWkYfE0', '0FBpOR5ANVOMselvFC0CAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQAYQRPcLLqq', 'KH9RkEZj/i6WPQWGBUbTmRS2e1uFhRLwVUgaX9yK84m/IS1w7X3JrYuykAh3nGjs', '955U7XqA28nt/VZqB9xXYvmmfhGNFVNphUa/YecBb7OilUlReuRjCugcR6s3JiKM', 'Vppr6iKxCYzooOiSsMJk7VSSWz2V7k4CGj4vD/1GX/BH9j2J9Xa4uvw0bmZf467q', 'KqUhpTw2T/DFg4b+dFjmyjbmjZTLrpfA2xBXGJQMrnHv3v9ca8WlX/zDhZDfEycY', 'HIgw9y+I6S0ZTKmzpCMzwpPUOny6StZcPWjKZGCVtLq1slpCHEH9T8++RdX/9Gn8', 'yU7Y/+iqZ/Us', '-----END CERTIFICATE REQUEST-----'], 'stderr_lines': ['Generating a RSA private key', '......+++++', '.............................+++++', "writing new private key to '/tmp/ansible.sksg5y_jvdsm'", '-----'], 'failed': False, 'item': {'changed': True, 'path': '/tmp/ansible.sksg5y_jvdsm', 'uid': 0, 'gid': 0, 'owner': 'root', 'group': 'root', 'mode': '0600', 'state': 'file', 'secontext' : 'unconfined_u:object_r:user_tmp_t:s0', 'size': 0, 'invocation': {'module_args': {'state': 'file', 'suffix': 'vdsm', 'prefix': 'ansible.', 'path': None}}, 'failed': False, 'item': {'suffix': 'vdsm', 'pending_file': 'keys/vdsmkey.pending.pem', 'req_dir': 'requests'}, 'ansible_loop_var': 'item'}, 'ansible_loop_var': 'item'}) => {"ansible_loop_var": "item", "item": {"ansible_loop_var": "item", "changed": true, "cmd": ["/usr/bin/openssl", "req", "-new", "-newkey", "rsa:2048", "-nodes", "-subj", "/", "-keyout", "/tmp/ansible.sksg5y_jvdsm"], "delta": "0:00:00.044151", "end": "2020-07-27 18:35:18.314757", "failed": false, "invocation": {"module_args": {"_raw_params": "'/usr/bin/openssl'\n'req'\n'-new'\n'-newkey'\n'rsa:2048'\n'-nodes'\n'-subj'\n'/'\n'-keyout'\n'/tmp/ansible.sksg5y_jvdsm'\n", "_uses_shell": false, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "stdin_add_newline": true, "strip_empty_ends": true, "warn": true}}, "item": {"an sible_loop_var": "item", "changed": true, "failed": false, "gid": 0, "group": "root", "invocation": {"module_args": {"path": null, "prefix": "ansible.", "state": "file", "suffix": "vdsm"}}, "item": {"pending_file": "keys/vdsmkey.pending.pem", "req_dir": "requests", "suffix": "vdsm"}, "mode": "0600", "owner": "root", "path": "/tmp/ansible.sksg5y_jvdsm", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 0, "state": "file", "uid": 0}, "rc": 0, "start": "2020-07-27 18:35:18.270606", "stderr": "Generating a RSA private key\n......+++++\n.............................+++++\nwriting new private key to '/tmp/ansible.sksg5y_jvdsm'\n-----", "stderr_lines": ["Generating a RSA private key", "......+++++", ".............................+++++", "writing new private key to '/tmp/ansible.sksg5y_jvdsm'", "-----"], "stdout": "-----BEGIN CERTIFICATE REQUEST-----\nMIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMo1\nIRs7qJtcFrVWc56TpJlxh54cPlLxASA/Xdu78vkNz4/eLL6Fyud5/mSloHeLuHat\ nJcvwxmLWcWDeNcEWlMR9tJTA6WxCS2rvUXXFNkw9QCUtTB9qrmezujdOTbDP4eqO\n/i0/xn0BO+kizB7SPMt3uyLJKAOCefcUwvmMEwZ25nw8oCqf/gICl/0AGKphuP11\nH1HuK5x8CTxboO2LawccpRUcbBXn5vF4LRsxy/VuK4fPMnxTk52F0DKwZMfnM4i6\npBnl7rI0P9JUDBlt2clYhz5fy4/unZmNYiyYpfkfv+YB66/vsFA/Hsa4DdWkYfE0\n0FBpOR5ANVOMselvFC0CAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQAYQRPcLLqq\nKH9RkEZj/i6WPQWGBUbTmRS2e1uFhRLwVUgaX9yK84m/IS1w7X3JrYuykAh3nGjs\n955U7XqA28nt/VZqB9xXYvmmfhGNFVNphUa/YecBb7OilUlReuRjCugcR6s3JiKM\nVppr6iKxCYzooOiSsMJk7VSSWz2V7k4CGj4vD/1GX/BH9j2J9Xa4uvw0bmZf467q\nKqUhpTw2T/DFg4b+dFjmyjbmjZTLrpfA2xBXGJQMrnHv3v9ca8WlX/zDhZDfEycY\nHIgw9y+I6S0ZTKmzpCMzwpPUOny6StZcPWjKZGCVtLq1slpCHEH9T8++RdX/9Gn8\nyU7Y/+iqZ/Us\n-----END CERTIFICATE REQUEST-----", "stdout_lines": ["-----BEGIN CERTIFICATE REQUEST-----", "MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMo1", "IRs7qJtcFrVWc56TpJlxh54cPlLxASA/Xdu78vkNz4/eLL6Fyud5/mSloHeLuHat", "JcvwxmLWcWDeNcEWlMR9tJTA6WxCS2rvUXXFNkw9QCUtTB9qrmezujdOTbDP4eqO", "/i0/xn0BO+kizB7SPMt3uyLJK AOCefcUwvmMEwZ25nw8oCqf/gICl/0AGKphuP11", "H1HuK5x8CTxboO2LawccpRUcbBXn5vF4LRsxy/VuK4fPMnxTk52F0DKwZMfnM4i6", "pBnl7rI0P9JUDBlt2clYhz5fy4/unZmNYiyYpfkfv+YB66/vsFA/Hsa4DdWkYfE0", "0FBpOR5ANVOMselvFC0CAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQAYQRPcLLqq", "KH9RkEZj/i6WPQWGBUbTmRS2e1uFhRLwVUgaX9yK84m/IS1w7X3JrYuykAh3nGjs", "955U7XqA28nt/VZqB9xXYvmmfhGNFVNphUa/YecBb7OilUlReuRjCugcR6s3JiKM", "Vppr6iKxCYzooOiSsMJk7VSSWz2V7k4CGj4vD/1GX/BH9j2J9Xa4uvw0bmZf467q", "KqUhpTw2T/DFg4b+dFjmyjbmjZTLrpfA2xBXGJQMrnHv3v9ca8WlX/zDhZDfEycY", "HIgw9y+I6S0ZTKmzpCMzwpPUOny6StZcPWjKZGCVtLq1slpCHEH9T8++RdX/9Gn8", "yU7Y/+iqZ/Us", "-----END CERTIFICATE REQUEST-----"]}, "msg": "Failed to connect to the host via ssh: ovirt@localhost: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).", "unreachable": true} 2020-07-27 18:35:20 UTC - failed: [localhost] (item={'cmd': ['/usr/bin/openssl', 'req', '-new', '-newkey', 'rsa:2048', '-nodes', '-subj', '/', '-keyout', '/tmp/ansible.oqj_hat2qemu'], 'stdout': '-----BEGIN CERTIFICATE REQUEST-----\nMIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL++\nQCG8gpsb3isdQFw/noaoOIGxd6zXcoCMdPs2vOP8z7ciPSQPE5r6JxmNTM9tMzCb\nb1sC7ON8PJNaMyRTQ1mVGFoQhQIq54L77GwV27qzVlsjmfM3MCUISVqTGZPWJ/RQ\nQVc03RXDbLYC0UG7C5Y+NRCp7G+67/dLjvzyO4IASZH1rEE7K/PPjSsyJJYaq68X\nXeyckgB7kjQXYZCIexihH3lvMvp7j75wc0RZztEw2bGhhByVsTZCvgouciL/43N7\nh2/8pMZaNbIcx5h8ZIoyWWvYGCe2PaALd94jSLjrgwY6v8lHSt/5S96Ace/C2jt6\nWDwbTfFvthyIosxJRdkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBp0Mj1WO4h\nn27hRFQ5n2hwRpLrbnD/KIkicNR9sFPszAMt6cN84a5jocrSJEcboPnz/Bg1yNlq\nFsN6gVI/RQY7BTmgP5chThe+/vtCJjP71K/+5YKpaBCbtpUIo/dERzHMsVS5O730\niXjFERxAObnrzllohpahc42+dwxPrd4ZMFrRmA5m55/nN9VgCudHTo8Uzrv+iaN7\n0G3oPW1IJGnycUArYyGPOIXTHMWRKcxF4irPOxXCp3cyWKxrfrO7vrl8LfOvVsJx\nbtRN84AUvUsSPzFDVPuAl8xZ9M0P+Ho9uGvSMlQ0 xdyfXU/9wFIhf3oFK3Slbo3j\nrXgOHdj+ve1g\n-----END CERTIFICATE REQUEST-----', 'stderr': "Generating a RSA private key\n....................................................................................................................................................+++++\n.....................................+++++\nwriting new private key to '/tmp/ansible.oqj_hat2qemu'\n-----", 'rc': 0, 'start': '2020-07-27 18:35:18.497403', 'end': '2020-07-27 18:35:18.688022', 'delta': '0:00:00.190619', 'changed': True, 'invocation': {'module_args': {'_raw_params': "'/usr/bin/openssl'\n'req'\n'-new'\n'-newkey'\n'rsa:2048'\n'-nodes'\n'-subj'\n'/'\n'-keyout'\n'/tmp/ansible.oqj_hat2qemu'\n", 'warn': True, '_uses_shell': False, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': ['-----BEGIN CERTIFICATE REQUEST-----', 'MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL++', 'QC G8gpsb3isdQFw/noaoOIGxd6zXcoCMdPs2vOP8z7ciPSQPE5r6JxmNTM9tMzCb', 'b1sC7ON8PJNaMyRTQ1mVGFoQhQIq54L77GwV27qzVlsjmfM3MCUISVqTGZPWJ/RQ', 'QVc03RXDbLYC0UG7C5Y+NRCp7G+67/dLjvzyO4IASZH1rEE7K/PPjSsyJJYaq68X', 'XeyckgB7kjQXYZCIexihH3lvMvp7j75wc0RZztEw2bGhhByVsTZCvgouciL/43N7', 'h2/8pMZaNbIcx5h8ZIoyWWvYGCe2PaALd94jSLjrgwY6v8lHSt/5S96Ace/C2jt6', 'WDwbTfFvthyIosxJRdkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBp0Mj1WO4h', 'n27hRFQ5n2hwRpLrbnD/KIkicNR9sFPszAMt6cN84a5jocrSJEcboPnz/Bg1yNlq', 'FsN6gVI/RQY7BTmgP5chThe+/vtCJjP71K/+5YKpaBCbtpUIo/dERzHMsVS5O730', 'iXjFERxAObnrzllohpahc42+dwxPrd4ZMFrRmA5m55/nN9VgCudHTo8Uzrv+iaN7', '0G3oPW1IJGnycUArYyGPOIXTHMWRKcxF4irPOxXCp3cyWKxrfrO7vrl8LfOvVsJx', 'btRN84AUvUsSPzFDVPuAl8xZ9M0P+Ho9uGvSMlQ0xdyfXU/9wFIhf3oFK3Slbo3j', 'rXgOHdj+ve1g', '-----END CERTIFICATE REQUEST-----'], 'stderr_lines': ['Generating a RSA private key', '.................................................................................................................................................... +++++', '.....................................+++++', "writing new private key to '/tmp/ansible.oqj_hat2qemu'", '-----'], 'failed': False, 'item': {'changed': True, 'path': '/tmp/ansible.oqj_hat2qemu', 'uid': 0, 'gid': 0, 'owner': 'root', 'group': 'root', 'mode': '0600', 'state': 'file', 'secontext': 'unconfined_u:object_r:user_tmp_t:s0', 'size': 0, 'invocation': {'module_args': {'state': 'file', 'suffix': 'qemu', 'prefix': 'ansible.', 'path': None}}, 'failed': False, 'item': {'suffix': 'qemu', 'pending_file': 'libvirt-migrate/server-key.pending.pem', 'req_dir': 'requests-qemu'}, 'ansible_loop_var': 'item'}, 'ansible_loop_var': 'item'}) => {"ansible_loop_var": "item", "item": {"ansible_loop_var": "item", "changed": true, "cmd": ["/usr/bin/openssl", "req", "-new", "-newkey", "rsa:2048", "-nodes", "-subj", "/", "-keyout", "/tmp/ansible.oqj_hat2qemu"], "delta": "0:00:00.190619", "end": "2020-07-27 18:35:18.688022", "failed": false, "invocation": {"module_args": {"_raw_params": "'/usr/b in/openssl'\n'req'\n'-new'\n'-newkey'\n'rsa:2048'\n'-nodes'\n'-subj'\n'/'\n'-keyout'\n'/tmp/ansible.oqj_hat2qemu'\n", "_uses_shell": false, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "stdin_add_newline": true, "strip_empty_ends": true, "warn": true}}, "item": {"ansible_loop_var": "item", "changed": true, "failed": false, "gid": 0, "group": "root", "invocation": {"module_args": {"path": null, "prefix": "ansible.", "state": "file", "suffix": "qemu"}}, "item": {"pending_file": "libvirt-migrate/server-key.pending.pem", "req_dir": "requests-qemu", "suffix": "qemu"}, "mode": "0600", "owner": "root", "path": "/tmp/ansible.oqj_hat2qemu", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 0, "state": "file", "uid": 0}, "rc": 0, "start": "2020-07-27 18:35:18.497403", "stderr": "Generating a RSA private key\n............................................................................................................................ ........................+++++\n.....................................+++++\nwriting new private key to '/tmp/ansible.oqj_hat2qemu'\n-----", "stderr_lines": ["Generating a RSA private key", "....................................................................................................................................................+++++", ".....................................+++++", "writing new private key to '/tmp/ansible.oqj_hat2qemu'", "-----"], "stdout": "-----BEGIN CERTIFICATE REQUEST-----\nMIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL++\nQCG8gpsb3isdQFw/noaoOIGxd6zXcoCMdPs2vOP8z7ciPSQPE5r6JxmNTM9tMzCb\nb1sC7ON8PJNaMyRTQ1mVGFoQhQIq54L77GwV27qzVlsjmfM3MCUISVqTGZPWJ/RQ\nQVc03RXDbLYC0UG7C5Y+NRCp7G+67/dLjvzyO4IASZH1rEE7K/PPjSsyJJYaq68X\nXeyckgB7kjQXYZCIexihH3lvMvp7j75wc0RZztEw2bGhhByVsTZCvgouciL/43N7\nh2/8pMZaNbIcx5h8ZIoyWWvYGCe2PaALd94jSLjrgwY6v8lHSt/5S96Ace/C2jt6\nWDwbTfFvthyIosxJRdkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBp0Mj1WO4h\nn27hRFQ5n2hwRpLrbnD/KIkicNR9 sFPszAMt6cN84a5jocrSJEcboPnz/Bg1yNlq\nFsN6gVI/RQY7BTmgP5chThe+/vtCJjP71K/+5YKpaBCbtpUIo/dERzHMsVS5O730\niXjFERxAObnrzllohpahc42+dwxPrd4ZMFrRmA5m55/nN9VgCudHTo8Uzrv+iaN7\n0G3oPW1IJGnycUArYyGPOIXTHMWRKcxF4irPOxXCp3cyWKxrfrO7vrl8LfOvVsJx\nbtRN84AUvUsSPzFDVPuAl8xZ9M0P+Ho9uGvSMlQ0xdyfXU/9wFIhf3oFK3Slbo3j\nrXgOHdj+ve1g\n-----END CERTIFICATE REQUEST-----", "stdout_lines": ["-----BEGIN CERTIFICATE REQUEST-----", "MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL++", "QCG8gpsb3isdQFw/noaoOIGxd6zXcoCMdPs2vOP8z7ciPSQPE5r6JxmNTM9tMzCb", "b1sC7ON8PJNaMyRTQ1mVGFoQhQIq54L77GwV27qzVlsjmfM3MCUISVqTGZPWJ/RQ", "QVc03RXDbLYC0UG7C5Y+NRCp7G+67/dLjvzyO4IASZH1rEE7K/PPjSsyJJYaq68X", "XeyckgB7kjQXYZCIexihH3lvMvp7j75wc0RZztEw2bGhhByVsTZCvgouciL/43N7", "h2/8pMZaNbIcx5h8ZIoyWWvYGCe2PaALd94jSLjrgwY6v8lHSt/5S96Ace/C2jt6", "WDwbTfFvthyIosxJRdkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBp0Mj1WO4h", "n27hRFQ5n2hwRpLrbnD/KIkicNR9sFPszAMt6cN84a5jocrSJEcboPnz/Bg1yNlq", "FsN6gVI/RQY7BTmgP5chThe+/vtCJjP71K/+5YKpaBCb tpUIo/dERzHMsVS5O730", "iXjFERxAObnrzllohpahc42+dwxPrd4ZMFrRmA5m55/nN9VgCudHTo8Uzrv+iaN7", "0G3oPW1IJGnycUArYyGPOIXTHMWRKcxF4irPOxXCp3cyWKxrfrO7vrl8LfOvVsJx", "btRN84AUvUsSPzFDVPuAl8xZ9M0P+Ho9uGvSMlQ0xdyfXU/9wFIhf3oFK3Slbo3j", "rXgOHdj+ve1g", "-----END CERTIFICATE REQUEST-----"]}, "msg": "Failed to connect to the host via ssh: ovirt@localhost: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).", "unreachable": true} 2020-07-27 18:35:20 UTC - fatal: [localhost]: UNREACHABLE! => {"changed": false, "msg": "All items completed", "results": [{"ansible_loop_var": "item", "item": {"ansible_loop_var": "item", "changed": true, "cmd": ["/usr/bin/openssl", "req", "-new", "-newkey", "rsa:2048", "-nodes", "-subj", "/", "-keyout", "/tmp/ansible.sksg5y_jvdsm"], "delta": "0:00:00.044151", "end": "2020-07-27 18:35:18.314757", "failed": false, "invocation": {"module_args": {"_raw_params": "'/usr/bin/openssl'\n'req'\n'-new'\n'-newkey'\n'rsa:2048'\n'-nodes'\n'-subj'\n'/'\n'-keyout'\n'/tmp/ansible.sksg5y_jvdsm'\n", "_uses_shell": false, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "stdin_add_newline": true, "strip_empty_ends": true, "warn": true}}, "item": {"ansible_loop_var": "item", "changed": true, "failed": false, "gid": 0, "group": "root", "invocation": {"module_args": {"path": null, "prefix": "ansible.", "state": "file", "suffix": "vdsm"}}, "item": {"pending _file": "keys/vdsmkey.pending.pem", "req_dir": "requests", "suffix": "vdsm"}, "mode": "0600", "owner": "root", "path": "/tmp/ansible.sksg5y_jvdsm", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 0, "state": "file", "uid": 0}, "rc": 0, "start": "2020-07-27 18:35:18.270606", "stderr": "Generating a RSA private key\n......+++++\n.............................+++++\nwriting new private key to '/tmp/ansible.sksg5y_jvdsm'\n-----", "stderr_lines": ["Generating a RSA private key", "......+++++", ".............................+++++", "writing new private key to '/tmp/ansible.sksg5y_jvdsm'", "-----"], "stdout": "-----BEGIN CERTIFICATE REQUEST-----\nMIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMo1\nIRs7qJtcFrVWc56TpJlxh54cPlLxASA/Xdu78vkNz4/eLL6Fyud5/mSloHeLuHat\nJcvwxmLWcWDeNcEWlMR9tJTA6WxCS2rvUXXFNkw9QCUtTB9qrmezujdOTbDP4eqO\n/i0/xn0BO+kizB7SPMt3uyLJKAOCefcUwvmMEwZ25nw8oCqf/gICl/0AGKphuP11\nH1HuK5x8CTxboO2LawccpRUcbBXn5vF4LRsxy/VuK4fPMnxTk52F0DKwZMfnM4i6\npBnl7rI0 P9JUDBlt2clYhz5fy4/unZmNYiyYpfkfv+YB66/vsFA/Hsa4DdWkYfE0\n0FBpOR5ANVOMselvFC0CAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQAYQRPcLLqq\nKH9RkEZj/i6WPQWGBUbTmRS2e1uFhRLwVUgaX9yK84m/IS1w7X3JrYuykAh3nGjs\n955U7XqA28nt/VZqB9xXYvmmfhGNFVNphUa/YecBb7OilUlReuRjCugcR6s3JiKM\nVppr6iKxCYzooOiSsMJk7VSSWz2V7k4CGj4vD/1GX/BH9j2J9Xa4uvw0bmZf467q\nKqUhpTw2T/DFg4b+dFjmyjbmjZTLrpfA2xBXGJQMrnHv3v9ca8WlX/zDhZDfEycY\nHIgw9y+I6S0ZTKmzpCMzwpPUOny6StZcPWjKZGCVtLq1slpCHEH9T8++RdX/9Gn8\nyU7Y/+iqZ/Us\n-----END CERTIFICATE REQUEST-----", "stdout_lines": ["-----BEGIN CERTIFICATE REQUEST-----", "MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMo1", "IRs7qJtcFrVWc56TpJlxh54cPlLxASA/Xdu78vkNz4/eLL6Fyud5/mSloHeLuHat", "JcvwxmLWcWDeNcEWlMR9tJTA6WxCS2rvUXXFNkw9QCUtTB9qrmezujdOTbDP4eqO", "/i0/xn0BO+kizB7SPMt3uyLJKAOCefcUwvmMEwZ25nw8oCqf/gICl/0AGKphuP11", "H1HuK5x8CTxboO2LawccpRUcbBXn5vF4LRsxy/VuK4fPMnxTk52F0DKwZMfnM4i6", "pBnl7rI0P9JUDBlt2clYhz5fy4/unZmNYiyYpfkfv+YB66/vsFA/Hsa4DdWkYfE0", "0FBpOR5ANVOMselvFC0CAwEAAaAA MA0GCSqGSIb3DQEBCwUAA4IBAQAYQRPcLLqq", "KH9RkEZj/i6WPQWGBUbTmRS2e1uFhRLwVUgaX9yK84m/IS1w7X3JrYuykAh3nGjs", "955U7XqA28nt/VZqB9xXYvmmfhGNFVNphUa/YecBb7OilUlReuRjCugcR6s3JiKM", "Vppr6iKxCYzooOiSsMJk7VSSWz2V7k4CGj4vD/1GX/BH9j2J9Xa4uvw0bmZf467q", "KqUhpTw2T/DFg4b+dFjmyjbmjZTLrpfA2xBXGJQMrnHv3v9ca8WlX/zDhZDfEycY", "HIgw9y+I6S0ZTKmzpCMzwpPUOny6StZcPWjKZGCVtLq1slpCHEH9T8++RdX/9Gn8", "yU7Y/+iqZ/Us", "-----END CERTIFICATE REQUEST-----"]}, "msg": "Failed to connect to the host via ssh: ovirt@localhost: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).", "unreachable": true}, {"ansible_loop_var": "item", "item": {"ansible_loop_var": "item", "changed": true, "cmd": ["/usr/bin/openssl", "req", "-new", "-newkey", "rsa:2048", "-nodes", "-subj", "/", "-keyout", "/tmp/ansible.oqj_hat2qemu"], "delta": "0:00:00.190619", "end": "2020-07-27 18:35:18.688022", "failed": false, "invocation": {"module_args": {"_raw_params": "'/usr/bin/openssl'\n'req'\n'-new'\n'-newkey'\n'rsa:2048'\n'-node s'\n'-subj'\n'/'\n'-keyout'\n'/tmp/ansible.oqj_hat2qemu'\n", "_uses_shell": false, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "stdin_add_newline": true, "strip_empty_ends": true, "warn": true}}, "item": {"ansible_loop_var": "item", "changed": true, "failed": false, "gid": 0, "group": "root", "invocation": {"module_args": {"path": null, "prefix": "ansible.", "state": "file", "suffix": "qemu"}}, "item": {"pending_file": "libvirt-migrate/server-key.pending.pem", "req_dir": "requests-qemu", "suffix": "qemu"}, "mode": "0600", "owner": "root", "path": "/tmp/ansible.oqj_hat2qemu", "secontext": "unconfined_u:object_r:user_tmp_t:s0", "size": 0, "state": "file", "uid": 0}, "rc": 0, "start": "2020-07-27 18:35:18.497403", "stderr": "Generating a RSA private key\n....................................................................................................................................................+++++\n.......................... ...........+++++\nwriting new private key to '/tmp/ansible.oqj_hat2qemu'\n-----", "stderr_lines": ["Generating a RSA private key", "....................................................................................................................................................+++++", ".....................................+++++", "writing new private key to '/tmp/ansible.oqj_hat2qemu'", "-----"], "stdout": "-----BEGIN CERTIFICATE REQUEST-----\nMIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL++\nQCG8gpsb3isdQFw/noaoOIGxd6zXcoCMdPs2vOP8z7ciPSQPE5r6JxmNTM9tMzCb\nb1sC7ON8PJNaMyRTQ1mVGFoQhQIq54L77GwV27qzVlsjmfM3MCUISVqTGZPWJ/RQ\nQVc03RXDbLYC0UG7C5Y+NRCp7G+67/dLjvzyO4IASZH1rEE7K/PPjSsyJJYaq68X\nXeyckgB7kjQXYZCIexihH3lvMvp7j75wc0RZztEw2bGhhByVsTZCvgouciL/43N7\nh2/8pMZaNbIcx5h8ZIoyWWvYGCe2PaALd94jSLjrgwY6v8lHSt/5S96Ace/C2jt6\nWDwbTfFvthyIosxJRdkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBp0Mj1WO4h\nn27hRFQ5n2hwRpLrbnD/KIkicNR9sFPszAMt6cN84a5jocrSJEcboPnz/Bg1yNlq\nFsN6gVI/RQY7BTmgP5c hThe+/vtCJjP71K/+5YKpaBCbtpUIo/dERzHMsVS5O730\niXjFERxAObnrzllohpahc42+dwxPrd4ZMFrRmA5m55/nN9VgCudHTo8Uzrv+iaN7\n0G3oPW1IJGnycUArYyGPOIXTHMWRKcxF4irPOxXCp3cyWKxrfrO7vrl8LfOvVsJx\nbtRN84AUvUsSPzFDVPuAl8xZ9M0P+Ho9uGvSMlQ0xdyfXU/9wFIhf3oFK3Slbo3j\nrXgOHdj+ve1g\n-----END CERTIFICATE REQUEST-----", "stdout_lines": ["-----BEGIN CERTIFICATE REQUEST-----", "MIICRTCCAS0CAQAwADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL++", "QCG8gpsb3isdQFw/noaoOIGxd6zXcoCMdPs2vOP8z7ciPSQPE5r6JxmNTM9tMzCb", "b1sC7ON8PJNaMyRTQ1mVGFoQhQIq54L77GwV27qzVlsjmfM3MCUISVqTGZPWJ/RQ", "QVc03RXDbLYC0UG7C5Y+NRCp7G+67/dLjvzyO4IASZH1rEE7K/PPjSsyJJYaq68X", "XeyckgB7kjQXYZCIexihH3lvMvp7j75wc0RZztEw2bGhhByVsTZCvgouciL/43N7", "h2/8pMZaNbIcx5h8ZIoyWWvYGCe2PaALd94jSLjrgwY6v8lHSt/5S96Ace/C2jt6", "WDwbTfFvthyIosxJRdkCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQBp0Mj1WO4h", "n27hRFQ5n2hwRpLrbnD/KIkicNR9sFPszAMt6cN84a5jocrSJEcboPnz/Bg1yNlq", "FsN6gVI/RQY7BTmgP5chThe+/vtCJjP71K/+5YKpaBCbtpUIo/dERzHMsVS5O730", "iXjFERxAObnrzllohpahc42+dwxPrd4ZM FrRmA5m55/nN9VgCudHTo8Uzrv+iaN7", "0G3oPW1IJGnycUArYyGPOIXTHMWRKcxF4irPOxXCp3cyWKxrfrO7vrl8LfOvVsJx", "btRN84AUvUsSPzFDVPuAl8xZ9M0P+Ho9uGvSMlQ0xdyfXU/9wFIhf3oFK3Slbo3j", "rXgOHdj+ve1g", "-----END CERTIFICATE REQUEST-----"]}, "msg": "Failed to connect to the host via ssh: ovirt@localhost: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).", "unreachable": true}]} 2020-07-27 18:35:20 UTC - PLAY RECAP ********************************************************************* localhost : ok=28 ch I want to install the host and the engine in the same VM (I did before with oVirt 4.3 but it doesn't work anymore) Could you help me please? Cheers.

3 5

where is error log for OVA import
by Philip Brown 01 Aug '20

01 Aug '20

I just tried to import an OVA file. The GUI status mentions that things seem to go along fairly happily.. it mentions that it creates a disk for it.... but then eventually just says "failed to import VM xxxxx into datacenter Default" with zero explanation. Isnt there a log file or something I can check, somewhere, to find out what the problem is? -- Philip Brown| Sr. Linux System Administrator | Medata, Inc. 5 Peters Canyon Rd Suite 250 Irvine CA 92606 Office 714.918.1310| Fax 714.918.1325 pbrown(a)medata.com| www.medata.com

4 6