November 2019 - Users - oVirt List Archives

Unable to install oVirt on RHEL7.5
by SS00514758＠techmahindra.com 15 Jan '26

15 Jan '26

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

8 10

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

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

27 Oct '23

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

5 13

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

17 Jul '23

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

4 6

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

27 Mar '23

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

4 19

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

26 Feb '23

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

3 5

Network Address Change
by Paul.LKW 28 Dec '22

28 Dec '22

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

4 6

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

08 Jun '22

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

5 4

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

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

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

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

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

09 Dec '20

7 14

"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

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

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

Upgrade ovirt from 3.4 to 4.3
by lu.alfonsi＠almaviva.it 19 Jun '20

19 Jun '20

Good morning, i have a difficult enviroment with 20 Hypervisors based on ovirt 3.4.3-1 and i would like to reach the 4.3 version. Which are the best steps to achieve these objective? Thanks in advance Luigi

3 10

Re: Single instance scaleup.
by Strahil 05 Jun '20

05 Jun '20

Hi Leo, As you do not have a distributed volume , you can easily switch to replica 2 arbiter 1 or replica 3 volumes. You can use the following for adding the bricks: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Admi… Best Regards, Strahil NikolivOn May 26, 2019 10:54, Leo David <leoalex(a)gmail.com> wrote: > > Hi Stahil, > Thank you so much for yout input ! > > gluster volume info > > > Volume Name: engine > Type: Distribute > Volume ID: d7449fc2-cc35-4f80-a776-68e4a3dbd7e1 > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 > Transport-type: tcp > Bricks: > Brick1: 192.168.80.191:/gluster_bricks/engine/engine > Options Reconfigured: > nfs.disable: on > transport.address-family: inet > storage.owner-uid: 36 > storage.owner-gid: 36 > features.shard: on > performance.low-prio-threads: 32 > performance.strict-o-direct: off > network.remote-dio: off > network.ping-timeout: 30 > user.cifs: off > performance.quick-read: off > performance.read-ahead: off > performance.io-cache: off > cluster.eager-lock: enable > Volume Name: ssd-samsung > Type: Distribute > Volume ID: 76576cc6-220b-4651-952d-99846178a19e > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 > Transport-type: tcp > Bricks: > Brick1: 192.168.80.191:/gluster_bricks/sdc/data > Options Reconfigured: > cluster.eager-lock: enable > performance.io-cache: off > performance.read-ahead: off > performance.quick-read: off > user.cifs: off > network.ping-timeout: 30 > network.remote-dio: off > performance.strict-o-direct: on > performance.low-prio-threads: 32 > features.shard: on > storage.owner-gid: 36 > storage.owner-uid: 36 > transport.address-family: inet > nfs.disable: on > > The other two hosts will be 192.168.80.192/193 - this is gluster dedicated network over 10GB sfp+ switch. > - host 2 wil have identical harware configuration with host 1 ( each disk is actually a raid0 array ) > - host 3 has: > - 1 ssd for OS > - 1 ssd - for adding to engine volume in a full replica 3 > - 2 ssd's in a raid 1 array to be added as arbiter for the data volume ( ssd-samsung ) > So the plan is to have "engine" scaled in a full replica 3, and "ssd-samsung" scalled in a replica 3 arbitrated. > > > > > On Sun, May 26, 2019 at 10:34 AM Strahil <hunter86_bg(a)yahoo.com> wrote: >> >> Hi Leo, >> >> Gluster is quite smart, but in order to provide any hints , can you provide output of 'gluster volume info <glustervol>'. >> If you have 2 more systems , keep in mind that it is best to mirror the storage on the second replica (2 disks on 1 machine -> 2 disks on the new machine), while for the arbiter this is not neccessary. >> >> What is your network and NICs ? Based on my experience , I can recommend at least 10 gbit/s interfase(s). >> >> Best Regards, >> Strahil Nikolov >> >> On May 26, 2019 07:52, Leo David <leoalex(a)gmail.com> wrote: >>> >>> Hello Everyone, >>> Can someone help me to clarify this ? >>> I have a single-node 4.2.8 installation ( only two gluster storage domains - distributed single drive volumes ). Now I just got two identintical servers and I would like to go for a 3 nodes bundle. >>> Is it possible ( after joining the new nodes to the cluster ) to expand the existing volumes across the new nodes and change them to replica 3 arbitrated ? >>> If so, could you share with me what would it be the procedure ? >>> Thank you very much ! >>> >>> Leo > > > > -- > Best regards, Leo David

4 5

Failed to add storage domain
by thunderlight1＠gmail.com 31 May '20

31 May '20

Hi! I have installed oVirt using the iso ovirt-node-ng-installer-4.3.2-2019031908.el7. I the did run the Host-engine deployment through Cockpit. I got an error when it tries to create the domain storage. It sucessfully mounted the NFS-share on the host. Bellow is the error I got: 2019-04-14 10:40:38,967+0200 INFO ansible skipped {'status': 'SKIPPED', 'ansible_task': u'Check storage domain free space', 'ansible_host': u'localhost', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_type': 'task'} 2019-04-14 10:40:38,967+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fb6918ad9d0> kwargs 2019-04-14 10:40:39,516+0200 INFO ansible task start {'status': 'OK', 'ansible_task': u'ovirt.hosted_engine_setup : Activate storage domain', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_type': 'task'} 2019-04-14 10:40:39,516+0200 DEBUG ansible on_any args TASK: ovirt.hosted_engine_setup : Activate storage domain kwargs is_conditional:False 2019-04-14 10:40:41,923+0200 DEBUG var changed: host "localhost" var "otopi_storage_domain_details" type "<type 'dict'>" value: "{ "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_storage_domain_payload_xSFxOp/__main__.py\", line 664, in main\n storage_domains_module.post_create_check(sd_id)\n File \"/tmp/ansible_ovirt_storage_domain_payload_xSFxOp/__main__.py\", line 526, in post_create_check\n id=storage_domain.id,\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py\", line 3053, in add\n return self._internal_add(storage_domain, headers, query, wait)\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 232, in _internal_add\n return future.wait() if wait else future\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 55, in wait\n return self._code(response)\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 229, in callback\n self._check_fault(response)\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 132, in _check_fault\n self._raise_error(response , body)\n File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 118, in _raise_error\n raise error\nError: Fault reason is \"Operation Failed\". Fault detail is \"[]\". HTTP response code is 400.\n", "failed": true, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[]\". HTTP response code is 400." }" 2019-04-14 10:40:41,924+0200 DEBUG var changed: host "localhost" var "ansible_play_hosts" type "<type 'list'>" value: "[]" 2019-04-14 10:40:41,924+0200 DEBUG var changed: host "localhost" var "play_hosts" type "<type 'list'>" value: "[]" 2019-04-14 10:40:41,924+0200 DEBUG var changed: host "localhost" var "ansible_play_batch" type "<type 'list'>" value: "[]" 2019-04-14 10:40:41,924+0200 ERROR ansible failed {'status': 'FAILED', 'ansible_type': 'task', 'ansible_task': u'Activate storage domain', 'ansible_result': u'type: <type \'dict\'>\nstr: {\'_ansible_parsed\': True, u\'exception\': u\'Traceback (most recent call last):\\n File "/tmp/ansible_ovirt_storage_domain_payload_xSFxOp/__main__.py", line 664, in main\\n storage_domains_module.post_create_check(sd_id)\\n File "/tmp/ansible_ovirt_storage_domain_payload_xSFxOp/__main__.py", line 526', 'task_duration': 2, 'ansible_host': u'localhost', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml'} 2019-04-14 10:40:41,924+0200 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7fb691843190> kwargs ignore_errors:None 2019-04-14 10:40:41,928+0200 INFO ansible stats { "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_playbook_duration": "00:37 Minutes", "ansible_result": "type: <type 'dict'>\nstr: {u'localhost': {'unreachable': 0, 'skipped': 6, 'ok': 23, 'changed': 1, 'failures': 1}}", "ansible_type": "finish", "status": "FAILED" } 2019-04-14 10:40:41,928+0200 INFO SUMMARY: Duration Task Name -------- -------- [ < 1 sec ] Execute just a specific set of steps [ 00:01 ] Force facts gathering [ 00:01 ] Check local VM dir stat [ 00:01 ] Obtain SSO token using username/password credentials [ 00:01 ] Fetch host facts [ < 1 sec ] Fetch cluster ID [ 00:01 ] Fetch cluster facts [ 00:01 ] Fetch Datacenter facts [ < 1 sec ] Fetch Datacenter ID [ < 1 sec ] Fetch Datacenter name [ 00:02 ] Add NFS storage domain [ 00:01 ] Get storage domain details [ 00:01 ] Find the appliance OVF [ 00:01 ] Parse OVF [ < 1 sec ] Get required size [ FAILED ] Activate storage domain 2019-04-14 10:40:41,928+0200 DEBUG ansible on_any args <ansible.executor.stats.AggregateStats object at 0x7fb69404eb90> kwargs Any suggestions on how fix this?

2 2

How to connect to a guest with vGPU ?
by Josep Manel Andrés Moscardó 29 May '20

29 May '20

Hi, I got vGPU through mdev working but I am wondering how I would connect to the client and make use of the GPU. So far I try to access the console through SPICE and at some point in the boot process it switches to GPU and I cannot see anything else. Thanks. -- Josep Manel Andrés Moscardó Systems Engineer, IT Operations EMBL Heidelberg T +49 6221 387-8394

3 4

ovirt-guest-agent for CentOS 8
by Eduardo Mayoral 30 Mar '20

30 Mar '20

Hi, Just like many of you I am testing my first CentOS 8 VMs on top of ovirt. I am not finding the package ovirt-guest-agent.noarch . Closest I can find is qemu-guest-agent.x86_64 After installing and starting it, I do see information reported on the "Guest info" tab. Can anybody confirm if this is indeed the agent we should be using? Is there - or will there be - a more specific package for ovirt guests? Thanks! -- Eduardo Mayoral Jimeno Systems engineer, platform department. Arsys Internet. emayoral(a)arsys.es - +34 941 620 105 - ext 2153

6 7

Re: Hyperconverged setup questions
by Strahil 29 Feb '20

29 Feb '20

Hi Marko, I guess you can use distributed-replicated volumes and oVirt cluster with host triplets. Best Regards, Strahil NikolovOn Oct 10, 2019 15:30, "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com> wrote: > > Dear oVirt, > > > > Is it possible to add oVirt 3Hosts/Gluster hyperconverged cluster to existing oVirt setup? I need this to achieve Local storage performance, but still have pool of Hypevisors available. > > Is it possible to have more than 3Hosts in Hyperconverged setup? > > > > I have currently 1Shared Cluster (NFS based storage, where also SHE is hosted) and 2Local Storage clusters. > > > > oVirt current version running is 4.3.4. > > > > Kindly awaiting your reply. > > > > > > — — — > Met vriendelijke groet / Kind regards, > > Marko Vrgotic > > ActiveVideo > > > >

6 12

Re: Damaged hard disk in volume replica gluster
by Strahil 25 Feb '20

25 Feb '20

As you are replacing an old brick, you have to recreate the old LV and mount it on the same location. Then you can use the gluster's "reset-brick" (i thing ovirt UI has that option too) and all data will be replicated there. You got also the "replace-brick" option if you decided to change the mount location. P.S.: with replica volumes your volume should be still working, in case it has stopped - you have to investigate before proceeding. Best Regards, Strahil NikolovOn Oct 12, 2019 13:12, matteo fedeli <matmilan97(a)gmail.com> wrote: > > Hi, I have in my ovirt HCI a volume that not work properly because one of three hdd fail. I bought a new hdd, I recreate old lvm partitioning and mount point. Now, how can I attach this empty new brick? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/U5XQ4M2K5RBKL…

5 20

terraform integration
by Nathanaël Blanchet 25 Feb '20

25 Feb '20

Hello, I'm interested by installing okd on ovirt with the official openshift installer (https://github.com/openshift/installer) but ovirt is not yet supported. Regarding https://bugzilla.redhat.com/show_bug.cgi?id=1578255 and https://lists.ovirt.org/archives/list/users@ovirt.org/thread/EF7OQUVTY53GV3… , how ovirt 4.3.7 should integrate openshift installer integration with terraform? -- 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

4 36

Vm suddenly paused with error "vm has paused due to unknown storage error"
by Jasper Siero 17 Feb '20

17 Feb '20

Hi all, Since we upgraded our Ovirt nodes to CentOS 7 a vm (not a specific one but never more then one) will sometimes pause suddenly with the error "VM ... has paused due to unknown storage error". It happens now two times in a month. The Ovirt node uses san storage for the vm's running on it. When a specific vm is pausing with an error the other vm's keeps running without problems. The vm runs without problems after unpausing it. Versions: CentOS Linux release 7.1.1503 vdsm-4.14.17-0 libvirt-daemon-1.2.8-16 vdsm.log: VM Channels Listener::DEBUG::2015-10-25 07:43:54,382::vmChannels::95::vds::(_handle_timeouts) Timeout on fileno 78. libvirtEventLoop::INFO::2015-10-25 07:43:56,177::vm::4602::vm.Vm::(_onIOError) vmId=`77f07ae0-cc3e-4ae2-90ec-7fba7b11deeb`::abnormal vm stop device virtio-disk0 error eother libvirtEventLoop::DEBUG::2015-10-25 07:43:56,178::vm::5204::vm.Vm::(_onLibvirtLifecycleEvent) vmId=`77f07ae0-cc3e-4ae2-90ec-7fba7b11deeb`::event Suspended detail 2 opaque None libvirtEventLoop::INFO::2015-10-25 07:43:56,178::vm::4602::vm.Vm::(_onIOError) vmId=`77f07ae0-cc3e-4ae2-90ec-7fba7b11deeb`::abnormal vm stop device virtio-disk0 error eother ........... libvirtEventLoop::INFO::2015-10-25 07:43:56,180::vm::4602::vm.Vm::(_onIOError) vmId=`77f07ae0-cc3e-4ae2-90ec-7fba7b11deeb`::abnormal vm stop device virtio-disk0 error eother specific error part in libvirt vm log: block I/O error in device 'drive-virtio-disk0': Unknown error 32758 (32758) ........... block I/O error in device 'drive-virtio-disk0': Unknown error 32758 (32758) engine.log: 2015-10-25 07:44:48,945 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-40) [a43dcc8] VM diataal-prod-cas1 77f07ae0-cc3e-4ae2-90ec-7fba7b11deeb moved from Up --> Paused 2015-10-25 07:44:49,003 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-40) [a43dcc8] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM diataal-prod-cas1 has paused due to unknown storage error. Has anyone experienced the same problem or knows a way to solve this? Kind regards, Jasper

3 3

Ovirt-engine-ha cannot to see live status of Hosted Engine
by asm＠pioner.kz 01 Feb '20

01 Feb '20

Good day for all. I have some issues with Ovirt 4.2.6. But now the main this of it: I have two Centos 7 Nodes with same config and last Ovirt 4.2.6 with Hostedengine with disk on NFS storage. Also some of virtual machines working good. But, when HostedEngine running on one node (srv02.local) everything is fine. After migrating to another node (srv00.local), i see that agent cannot to check livelinness of HostedEngine. After few minutes HostedEngine going to reboot and after some time i see some situation. After migration to another node (srv00.local) all looks OK. hosted-engine --vm-status commang when HosterEngine on srv00 node: --== Host 1 status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : srv02.local Host ID : 1 Engine status : {"reason": "vm not running on this host", "health": "bad", "vm": "down_unexpected", "detail": "unknown"} Score : 0 stopped : False Local maintenance : False crc32 : ecc7ad2d local_conf_timestamp : 78328 Host timestamp : 78328 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=78328 (Tue Sep 18 12:44:18 2018) host-id=1 score=0 vm_conf_refresh_time=78328 (Tue Sep 18 12:44:18 2018) conf_on_shared_storage=True maintenance=False state=EngineUnexpectedlyDown stopped=False timeout=Fri Jan 2 03:49:58 1970 --== Host 2 status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : srv00.local Host ID : 2 Engine status : {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"} Score : 3400 stopped : False Local maintenance : False crc32 : 1d62b106 local_conf_timestamp : 326288 Host timestamp : 326288 Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=326288 (Tue Sep 18 12:44:21 2018) host-id=2 score=3400 vm_conf_refresh_time=326288 (Tue Sep 18 12:44:21 2018) conf_on_shared_storage=True maintenance=False state=EngineStarting stopped=False Log agent.log from srv00.local: MainThread::INFO::2018-09-18 12:40:51,749::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedE ngine::(consume) VM is powering up.. MainThread::INFO::2018-09-18 12:40:52,052::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 3400) MainThread::INFO::2018-09-18 12:41:01,066::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedE ngine::(consume) VM is powering up.. MainThread::INFO::2018-09-18 12:41:01,374::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 3400) MainThread::INFO::2018-09-18 12:41:11,393::state_machine::169::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(refresh) Global metadata: {'maintenance': False} MainThread::INFO::2018-09-18 12:41:11,393::state_machine::174::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(refresh) Host srv02.local.pioner.kz (id 1): {'conf_on_shared_storage': True, 'extra': 'meta data_parse_version=1\nmetadata_feature_version=1\ntimestamp=78128 (Tue Sep 18 12:40:58 2018)\nhost-id=1\ns core=0\nvm_conf_refresh_time=78128 (Tue Sep 18 12:40:58 2018)\nconf_on_shared_storage=True\nmaintenance=Fa lse\nstate=EngineUnexpectedlyDown\nstopped=False\ntimeout=Fri Jan 2 03:49:58 1970\n', 'hostname': 'srv02. local.pioner.kz', 'alive': True, 'host-id': 1, 'engine-status': {'reason': 'vm not running on this host', 'health': 'bad', 'vm': 'down_unexpected', 'detail': 'unknown'}, 'score': 0, 'stopped': False, 'maintenance ': False, 'crc32': 'e18e3f22', 'local_conf_timestamp': 78128, 'host-ts': 78128} MainThread::INFO::2018-09-18 12:41:11,393::state_machine::177::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(refresh) Local (id 2): {'engine-health': {'reason': 'failed liveliness check', 'health': 'b ad', 'vm': 'up', 'detail': 'Up'}, 'bridge': True, 'mem-free': 12763.0, 'maintenance': False, 'cpu-load': 0 .0364, 'gateway': 1.0, 'storage-domain': True} MainThread::INFO::2018-09-18 12:41:11,393::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedE ngine::(consume) VM is powering up.. MainThread::INFO::2018-09-18 12:41:11,703::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 3400) MainThread::INFO::2018-09-18 12:41:21,716::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedE ngine::(consume) VM is powering up.. MainThread::INFO::2018-09-18 12:41:22,020::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 3400) MainThread::INFO::2018-09-18 12:41:31,033::states::779::ovirt_hosted_engine_ha.agent.hosted_engine.HostedE ngine::(consume) VM is powering up.. MainThread::INFO::2018-09-18 12:41:31,344::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine. HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 3400) As we can see, agent thinking that HostedEngine just in powering up mode. I cannot to do anythink with it. I allready reinstalled many times srv00 node without success. One time i even has to uninstall ovirt* and vdsm* software. Also here one interesting point, after installing just "yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm" on this node i try to install this node from engine web interface with "Deploy" action. But, installation was unsuccesfull, before i didnt install ovirt-hosted-engine-ha on this node. I dont see in documentation that its need bofore installation of new hosts. But this is for information and checking. After installing ovirt-hosted-engine-ha node was installed with HostedEngine support. But the main issue not changed. Thanks in advance for help. BR, Alexandr

3 5

Re: [ANN] oVirt 4.3.7 Third Release Candidate is now available for testing
by Strahil 30 Jan '20

30 Jan '20

I got upgraded to RC3 and now cannot power any VM . Constantly getting I/O error, but checking at gluster level - I can dd from each disk or even create a new one. Removing the HighAvailability doesn't help. I guess I should restore the engine from the gluster snapshot and rollback via 'yum history undo last'. Does anyone else have my issues ? Best Regards, Strahil NikolovOn Nov 13, 2019 15:31, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > > Il giorno mer 13 nov 2019 alle ore 14:25 Sandro Bonazzola <sbonazzo(a)redhat.com> ha scritto: >> >> >> >> Il giorno mer 13 nov 2019 alle ore 13:56 Florian Schmid <fschmid(a)ubimet.com> ha scritto: >>> >>> Hello, >>> >>> I have a question about bugs, which are flagged as [downstream clone - 4.3.7], but are not yet released. >>> >>> I'm talking about this bug: >>> https://bugzilla.redhat.com/show_bug.cgi?id=1749202 >>> >>> I can't see it in 4.3.7 release notes. Will it be included in a further release candidate? This fix is very important I think and I can't upgrade yet because of this bug. >> >> >> >> Looking at the bug, the fix was done with $ git tag --contains 12bd5cb1fe7c95e29b4065fca968913722fe9eaa >> ovirt-engine-4.3.6.6 >> ovirt-engine-4.3.6.7 >> ovirt-engine-4.3.7.0 >> ovirt-engine-4.3.7.1 >> >> So the fix is already included in release oVirt 4.3.6. > > > Sent a fix to 4.3.6 release notes: https://github.com/oVirt/ovirt-site/pull/2143. @Ryan Barry can you please review? > > >> >> >> >> >> >> >>> >>> >>> BR Florian Schmid >>> >>> ________________________________ >>> Von: "Sandro Bonazzola" <sbonazzo(a)redhat.com> >>> An: "users" <users(a)ovirt.org> >>> Gesendet: Mittwoch, 13. November 2019 13:34:59 >>> Betreff: [ovirt-users] [ANN] oVirt 4.3.7 Third Release Candidate is now available for testing >>> >>> The oVirt Project is pleased to announce the availability of the oVirt 4.3.7 Third Release Candidate for testing, as of November 13th, 2019. >>> >>> This update is a release candidate of the seventh in a series of stabilization updates to the 4.3 series. >>> This is pre-release software. This pre-release should not to be used in production. >>> >>> This release is available now on x86_64 architecture for: >>> * Red Hat Enterprise Linux 7.7 or later (but <8) >>> * CentOS Linux (or similar) 7.7 or later (but <8) >>> >>> This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: >>> * Red Hat Enterprise Linux 7.7 or later (but <8) >>> * CentOS Linux (or similar) 7.7 or later (but <8) >>> * oVirt Node 4.3 (available for x86_64 only) has been built consuming CentOS 7.7 Release >>> >>> See the release notes [1] for known issues, new features and bugs fixed. >>> >>> While testing this release candidate please note that oVirt node now includes: >>> - ansible 2.9.0 >>> - GlusterFS 6.6 >>> >>> Notes: >>> - oVirt Appliance is already available >>> - oVirt Node is already available >>> >>> Additional Resources: >>> * Read more about the oVirt 4.3.7 release highlights: http://www.ovirt.org/release/4.3.7/ >>> * 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.3.7/ >>> [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ >>> >>> -- >>> >>> Sandro Bonazzola >>> >>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>> >>> Red Hat EMEA >>> >>> sbonazzo(a)redhat.com >>> >>> Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. >>> >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/24QUREJPZHTSM… >> >> >> >> -- >> >> Sandro Bonazzola >> >> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >> >> Red Hat EMEA >> >> sbonazzo(a)redhat.com >> >> Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. > > > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA > > sbonazzo(a)redhat.com > > Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.

7 20

Low disk space on Storage
by suporte＠logicworks.pt 12 Jan '20

12 Jan '20

Hi, I'm running ovirt Version:4.3.4.3-1.el7 My filesystem disk has 30 GB free space. Cannot start a VM due to an I/O error storage. When tryng to move the disk to another storage domain get this error: Error while executing action: Cannot move Virtual Disk. Low disk space on Storage Domain DATA4. The sum of pre-allocated disk is the total of the storage domain disk. Any idea what can I do to move a disk to other storage domain? Many thanks -- Jose Ferradeira http://www.logicworks.pt

5 5

Hyperconverged setup - storage architecture - scaling
by Leo David 10 Jan '20

10 Jan '20

Hello Everyone, Reading through the document: "Red Hat Hyperconverged Infrastructure for Virtualization 1.5 Automating RHHI for Virtualization deployment" Regarding storage scaling, i see the following statements: *2.7. SCALINGRed Hat Hyperconverged Infrastructure for Virtualization is supported for one node, and for clusters of 3, 6, 9, and 12 nodes.The initial deployment is either 1 or 3 nodes.There are two supported methods of horizontally scaling Red Hat Hyperconverged Infrastructure for Virtualization:* *1 Add new hyperconverged nodes to the cluster, in sets of three, up to the maximum of 12 hyperconverged nodes.* *2 Create new Gluster volumes using new disks on existing hyperconverged nodes.You cannot create a volume that spans more than 3 nodes, or expand an existing volume so that it spans across more than 3 nodes at a time* *2.9.1. Prerequisites for geo-replicationBe aware of the following requirements and limitations when configuring geo-replication:One geo-replicated volume onlyRed Hat Hyperconverged Infrastructure for Virtualization (RHHI for Virtualization) supports only one geo-replicated volume. Red Hat recommends backing up the volume that stores the data of your virtual machines, as this is usually contains the most valuable data.* ------ Also in oVirtEngine UI, when I add a brick to an existing volume i get the following warning: *"Expanding gluster volume in a hyper-converged setup is not recommended as it could lead to degraded performance. To expand storage for cluster, it is advised to add additional gluster volumes." * Those things are raising a couple of questions that maybe for some for you guys are easy to answer, but for me it creates a bit of confusion... I am also referring to RedHat product documentation, because I treat oVirt as production-ready as RHHI is. *1*. Is there any reason for not going to distributed-replicated volumes ( ie: spread one volume across 6,9, or 12 nodes ) ? - ie: is recomanded that in a 9 nodes scenario I should have 3 separated volumes, but how should I deal with the folowing question *2.* If only one geo-replicated volume can be configured, how should I deal with 2nd and 3rd volume replication for disaster recovery *3.* If the limit of hosts per datacenter is 250, then (in theory ) the recomended way in reaching this treshold would be to create 20 separated oVirt logical clusters with 12 nodes per each ( and datacenter managed from one ha-engine ) ? *4.* In present, I have the folowing one 9 nodes cluster , all hosts contributing with 2 disks each to a single replica 3 distributed replicated volume. They where added to the volume in the following order: node1 - disk1 node2 - disk1 ...... node9 - disk1 node1 - disk2 node2 - disk2 ...... node9 - disk2 At the moment, the volume is arbitrated, but I intend to go for full distributed replica 3. Is this a bad setup ? Why ? It oviously brakes the redhat recommended rules... Is there anyone so kind to discuss on these things ? Thank you very much ! Leo -- Best regards, Leo David -- Best regards, Leo David

3 5

AWX and error using ovirt as an inventory source
by Gianluca Cecchi 09 Jan '20

09 Jan '20

Hello, I have awx 9.0.1 and ansible 2.8.5 in container of a CentOS 7.7 server. I'm trying to use oVirt 4.3.6.7-1.el7 as a source of an inventory in awx but I get error when syncing Find at bottom below the error messages. I see that in recent past (around June this year) there were some problems, but they should be solved now, correct? There was also a problem in syncing when some powered off VMs were present in oVirt env, but I think this solved too, correct? Any way to replicate / test from command line of awx container? I try some things but in command line I always get error regarding oVirt inventory script requires ovirt-engine-sdk-python >= 4.0.0 that I think depends on not using correct command line and/or not setting needed env. Thanks in advance, Gianluca 2.536 INFO Updating inventory 4: MYDC_OVIRT 3.011 INFO Reading Ansible inventory source: /var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/plugins/inventory/ovirt4.py 3.013 INFO Using VIRTUAL_ENV: /var/lib/awx/venv/ansible 3.013 INFO Using PATH: /var/lib/awx/venv/ansible/bin:/var/lib/awx/venv/awx/bin:/var/lib/awx/venv/awx/bin:/var/lib/awx/venv/awx/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 3.013 INFO Using PYTHONPATH: /var/lib/awx/venv/ansible/lib/python3.6/site-packages: Traceback (most recent call last): File "/var/lib/awx/venv/awx/bin/awx-manage", line 11, in <module> load_entry_point('awx==9.0.1.0', 'console_scripts', 'awx-manage')() File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/__init__.py", line 158, in manage execute_from_command_line(sys.argv) File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv self.execute(*args, **cmd_options) File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/django/core/management/base.py", line 364, in execute output = self.handle(*args, **options) File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 1153, in handle raise exc File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 1043, in handle venv_path=venv_path, verbosity=self.verbosity).load() File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 214, in load return self.command_to_json(base_args + ['--list']) File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/awx/main/management/commands/inventory_import.py", line 197, in command_to_json self.method, proc.returncode, stdout, stderr)) RuntimeError: ansible-inventory failed (rc=1) with stdout: stderr: ansible-inventory 2.8.5 config file = /etc/ansible/ansible.cfg configured module search path = ['/var/lib/awx/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python3.6/site-packages/ansible executable location = /usr/bin/ansible-inventory python version = 3.6.8 (default, Oct 7 2019, 17:58:22) [GCC 8.2.1 20180905 (Red Hat 8.2.1-3)] Using /etc/ansible/ansible.cfg as config file [WARNING]: * Failed to parse /var/lib/awx/venv/awx/lib64/python3.6/site- packages/awx/plugins/inventory/ovirt4.py with script plugin: Inventory script (/var/lib/awx/venv/awx/lib64/python3.6/site- packages/awx/plugins/inventory/ovirt4.py) had an execution error: File "/usr/lib/python3.6/site-packages/ansible/inventory/manager.py", line 268, in parse_source plugin.parse(self._inventory, self._loader, source, cache=cache) File "/usr/lib/python3.6/site-packages/ansible/plugins/inventory/script.py", line 161, in parse raise AnsibleParserError(to_native(e)) [WARNING]: Unable to parse /var/lib/awx/venv/awx/lib64/python3.6/site- packages/awx/plugins/inventory/ovirt4.py as an inventory source ERROR! No inventory was parsed, please check your configuration and options.

3 23

ovirt hosted-engine on iSCSI offering one target
by wodel youchi 18 Dec '19

18 Dec '19

Hi, We have an oVirt Platforme using the 4.1 version. when the platforme was installed, it was made of : - Two HP Proliant DL380 G9 as hypervisors - One HP MSA1040 for iSCSI - One Synology for NFS - Two switches, one for network/vm traffic, the second for storage traffic. The problem : the hosted-engine domain was created using iSCSI on the HP MSA. The problem is that this disk array does not give the possibility to create different targets, it presents just one target. At that time we create both the hosted-engine and the first data domain using the same target, and we didn't pay attention to the information saying "i*f you are using iSCSI storage, do not use the same iSCSI target for the shared storage domain and data storage domain*". Question : - what problems can be generated by this (mis-)configuration? - Is this a must to do (correct) configuration. Regards.

3 2

Unable to attach ISO domain to Datacenter
by Ivan de Gusmão Apolonio 13 Dec '19

13 Dec '19

I'm having trouble to create a storage ISO Domain and attach it to a Datacenter. It just give me this error message: Error while executing action Attach Storage Domain: Could not obtain lock Also the oVirt's Engine log files show this error message: "setsid: failed to execute /usr/bin/ionice: Permission denied", but I was unable to identify what exactly it's trying to do to get this permission denied. 2019-11-14 16:46:07,779-03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-7388) [86161370-2aaa-4eff-9aab-c184bdf5bb98] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command AttachStorageDomainVDS failed: Cannot obtain lock: u"id=e6b34c42-0ca6-41f4-be3e-3c9b2af1747b, rc=1, out=[], err=['setsid: failed to execute /usr/bin/ionice: Permission denied']" This behavior just happens on ISO Domains, while Data Domains works fine. I have read oVirt documentation and searched everywhere but I was unable to find the solution for this issue. I'm using CentOS 7 with last update of all packages (oVirt version 4.3.6.7). Please help! Thanks, Ivan de Gusmão Apolonio

6 18

Gluster set up fails - Nearly there I think...
by rob.downer＠orbitalsystems.co.uk 11 Dec '19

11 Dec '19

Gluster fails with vdo: ERROR - Device /dev/sdb excluded by a filter.\n", however I have run [root@ovirt1 ~]# vdo create --name=vdo1 --device=/dev/sdb --force Creating VDO vdo1 Starting VDO vdo1 Starting compression on VDO vdo1 VDO instance 1 volume is ready at /dev/mapper/vdo1 [root@ovirt1 ~]# there are no filters in lvm.conf I have run wipefs -a /dev/sdb —force on all hosts before start

5 9

Re: Cannot obtain information from export domain
by Strahil 10 Dec '19

10 Dec '19

Hi can you describe your actions? Usually the export is like this: 1. You make a backup of the VM 2. You migrate the disks to the export storage domain 3. You shut down the VM 4. Set the storage domain in maintenance and then detach it from the oVirt 5. You atttach it to the new oVirt 6. Once the domain is active - click on import VM tab and import all VMs (defining the cluster you want them to be running on) 7. Power up VM and then migrate the disks to the permanent storage. Best Regards, Strahil NikolovOn Nov 26, 2019 19:41, Arthur Rodrigues Stilben <arthur.stilben(a)gmail.com> wrote: > > Hello everyone, > > I'm trying to export a virtual machine, but I'm getting the following error: > > 2019-11-26 16:30:06,250-02 ERROR > [org.ovirt.engine.core.bll.exportimport.GetVmsFromExportDomainQuery] > (default task-22) [b9a0b9d5-2127-4002-9cee-2e3525bccc89] Exception: > org.ovirt.engine.core.common.errors.EngineException: EngineException: > org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException: > IRSGenericException: IRSErrorException: Failed to GetVmsInfoVDS, error = > Storage domain does not exist: > (u'5ac6c35d-0406-4a06-a682-ed8fb2d1933f',), code = 358 (Failed with > error StorageDomainDoesNotExist and code 358) > > 2019-11-26 16:30:06,249-02 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (default task-22) [b9a0b9d5-2127-4002-9cee-2e3525bccc89] EVENT_ID: > IMPORTEXPORT_GET_VMS_INFO_FAILED(200), Correlation ID: null, Call Stack: > null, Custom ID: null, Custom Event ID: -1, Message: Failed to retrieve > VM/Templates information from export domain BackupMV > > The version of the oVirt that I am using is 4.1. > > Att, > > -- > Arthur Rodrigues Stilben > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/Z6FQ45UVQODSR…

2 1

Cannot activate/deactivate storage domain
by Albl, Oliver 04 Dec '19

04 Dec '19

Hi all, I run an oVirt 4.3.6.7-1.el7 installation (50+ hosts, 40+ FC storage domains on two all-flash arrays) and experienced a problem accessing single storage domains. As a result, hosts were taken "not operational" because they could not see all storage domains, SPM started to move around the hosts. oVirt messages start with: 2019-11-04 15:10:22.739+01 | VDSM HOST082 command SpmStatusVDS failed: (-202, 'Sanlock resource read failure', 'IO timeout') 2019-11-04 15:10:22.781+01 | Invalid status on Data Center <name>. Setting Data Center status to Non Responsive (On host HOST82, Error: General Exception). ... 2019-11-04 15:13:58.836+01 | Host HOST017 cannot access the Storage Domain(s) HOST_LUN_204 attached to the Data Center <name>. Setting Host state to Non-Operational. 2019-11-04 15:13:58.85+01 | Host HOST005 cannot access the Storage Domain(s) HOST_LUN_204 attached to the Data Center <name>. Setting Host state to Non-Operational. 2019-11-04 15:13:58.85+01 | Host HOST012 cannot access the Storage Domain(s) HOST_LUN_204 attached to the Data Center <name>. Setting Host state to Non-Operational. 2019-11-04 15:13:58.851+01 | Host HOST002 cannot access the Storage Domain(s) HOST_LUN_204 attached to the Data Center <name>. Setting Host state to Non-Operational. 2019-11-04 15:13:58.851+01 | Host HOST010 cannot access the Storage Domain(s) HOST_LUN_204 attached to the Data Center <name>. Setting Host state to Non-Operational. 2019-11-04 15:13:58.851+01 | Host HOST011 cannot access the Storage Domain(s) HOST_LUN_204 attached to the Data Center <name>. Setting Host state to Non-Operational. 2019-11-04 15:13:58.852+01 | Host HOST004 cannot access the Storage Domain(s) HOST_LUN_204 attached to the Data Center <name>. Setting Host state to Non-Operational. 2019-11-04 15:13:59.011+01 | Host HOST017 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center <UNKNOWN>. Setting Host state to Non-Operational. 2019-11-04 15:13:59.238+01 | Host HOST004 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center <UNKNOWN>. Setting Host state to Non-Operational. 2019-11-04 15:13:59.249+01 | Host HOST005 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center <UNKNOWN>. Setting Host state to Non-Operational. 2019-11-04 15:13:59.255+01 | Host HOST012 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center <UNKNOWN>. Setting Host state to Non-Operational. 2019-11-04 15:13:59.273+01 | Host HOST002 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center <UNKNOWN>. Setting Host state to Non-Operational. 2019-11-04 15:13:59.279+01 | Host HOST010 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center <UNKNOWN>. Setting Host state to Non-Operational. 2019-11-04 15:13:59.386+01 | Host HOST011 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center <UNKNOWN>. Setting Host state to Non-Operational. 2019-11-04 15:15:14.145+01 | Storage domain HOST_LUN_221 experienced a high latency of 9.60953 seconds from host HOST038. This may cause performance and functional issues. Please consult your Storage Administrator. The problem mainly affected two storage domains (on the same array) but I also saw single messages for other storage domains (one the other array as well). Storage domains stayed available to the hosts, all VMs continued to run. When constantly reading from the storage domains (/bin/dd iflag=direct if=<metadata> bs=4096 count=1 of=/dev/null) we got expected 20+ MBytes/s on all but some storage domains. One of them showed "transfer rates" around 200 Bytes/s, but went up to normal performance from time to time. Transfer rate to this domain was different between the hosts. /var/log/messages contain qla2xxx abort messages on almost all hosts. There are no errors on SAN switches or storage array (but vendor is still investigating). I did not see high load on the storage array. The system seemed to stabilize when I stopped all VMs on the affected storage domain and this storage domain became "inactive". Currently, this storage domain still is inactive and we cannot place it in maintenance mode ("Failed to deactivate Storage Domain") nor activate it. OVF Metadata seems to be corrupt as well (failed to update OVF disks <id>, OVF data isn't updated on those OVF stores). The first six 512 byte blocks of /dev/<id>/metadata seem to contain only zeros. Any advice on how to proceed here? Is there a way to recover this storage domain? All the best, Oliver

4 13

Re: Certificate of host is invalid
by Strahil 04 Dec '19

04 Dec '19

Hi , You can try with: 1. Set the host in maintenance 2. From Install dropdown , select 'reinstall' and then configure the necessary info + whether you would like to use the host as Host for the HostedEngine VM. Once the reinstall (of Ovirt software) is OK, the node will be activated automatically. Best Regards, Strahil NikolovOn Nov 27, 2019 18:01, Jon bae <jonbae77(a)gmail.com> wrote: > > Hello everybody, > since last update to 4.3.7 I get this error message: > > Certificate of host host.name is invalid. The certificate doesn't contain valid subject alternative name, please enroll new certificate for the host. > > Have you an idea of how I can fix that? > > Regards > Jonathan

3 3

Disk move succeed but didn't move content
by Juan Pablo Lorier 03 Dec '19

03 Dec '19

Hi, I've a fresh new install of ovirt 4.3 and tried to import an gluster vmstore. I managed to import via NFS the former data domain. The problem is that when I moved the disks of the vms to the new ISCSI data domain, I got a warning that sparse disk type will be converted to qcow2 disks, and after accepting, the disks were moved with no error. The problem is that the disks now figure as <1Gb size instead of the original size and thus, the vms fail to start. Is there any way to recover those disks? I have no backup of the vms :-( Regards

3 4

Current status of Ceph support in oVirt (2019)?
by victorhooi＠yahoo.com 03 Dec '19

03 Dec '19

Hi, I currently have a 3-node HA cluster running Proxmox (with integrated Ceph). oVirt looks pretty neat, however, and I'm excited to check it out. One of the things I love about Proxmox is the integrated Ceph support. I saw on the mailing lists that there is some talk of Ceph support earlier, but it was via OpenStack/Cinder. What exactly does this mean? 1. Does this require you to install OpenStack, or will a vanilla Ceph installation work? 2. Is it possible to deploy Ceph on the same nodes that run oVirt? (i.e. is a 3-node oVirt + Ceph cluster possible?) 3. Is there any monitoring/management of Ceph from within oVirt? (Guessing no?) 4. Are all the normal VM features working yet, or is this planned? 5. Is making Ceph a first-class citizen (like Gluster) on oVirt on the roadmap? Thanks, Victor https://www.reddit.com/r/ovirt/comments/ci38zp/ceph_rbd_support_in_ovirt_fo…

3 3

oVirt nodes not responding
by Tim Herrmann 03 Dec '19

03 Dec '19

Hi everyone, we have an oVirt-Cluster with 5 nodes and 3 of them provide the storage with GlusterFS and replica 3. The cluster is running 87 VMs and has 9TB storage where 4TB is in use. The version of the oVirt-Engine is 4.1.8.2 and GlusterFS is 3.8.15. The servers are running in a HP bladecenter and are connected with 10GBit to each other. Actually we have some problems that all ovirt nodes periodically won't respond in the cluster with the following error messages in the oVirt webinterface: VDSM glustervirt05 command GetGlusterVolumeHealInfoVDS failed: Message timeout which can be caused by communication issues Host glustervirt05 is not responding. It will stay in Connecting state for a grace period of 68 seconds and after that an attempt to fence the host will be issued. Host glustervirt05 does not enforce SELinux. Current status: PERMISSIVE Executing power management status on Host glustervirt05 using Proxy Host glustervirt02 and Fence Agent ilo4:xxx.xxx.xxx.xxx. Manually synced the storage devices from host glustervirt05 Status of host glustervirt05 was set to Up. In the vdsm logfile I can find the following message: 2019-11-26 11:18:22,909+0100 WARN (vdsm.Scheduler) [Executor] Worker blocked: <Worker name=jsonrpc/7 running <Task <JsonRpcTask {'params': {u'volumeName': u'data'}, 'jsonrpc': '2.0', 'method': u'GlusterVolume.healInfo', 'id': u'2e86ed2c- 3e79-42c1-a7e4-c09bfbfc7794'} at 0x7fb938373190> timeout=60, duration=180 at 0x316a6d0> task#=2859802 at 0x1b70dd0> (executor:351) And I figured out, that the gluster heal info command takes very long: [root@glustervirt01 ~]# time gluster volume heal data info Brick glustervirt01:/gluster/data/brick1 Status: Connected Number of entries: 0 Brick glustervirt02:/gluster/data/brick1 Status: Connected Number of entries: 0 Brick glustervirt03:/gluster/data/brick2 Status: Connected Number of entries: 0 real 3m3.626s user 0m0.593s sys 0m0.559s A strange behavier is also that there is one virtual machine (a postgresql database) which stops running unexpectedly every one or two days ... The only thing that has been changed on the vm in the least past was a resize of the disk. VM replication-zabbix is down with error. Exit message: Lost connection with qemu process. And when we add or delete a larger disk with approximately 100GB in glusterfs, the glusterfs cluster freaks out won't respond anymore. This also results in paused VMs ... Has anyone an idea what could cause such problems?

2 1

Overt Networking VM not pinging
by Vijay Sachdeva 02 Dec '19

02 Dec '19

Dear Community, I have installed Ovirt Engine 4.3 and Ovirt Node 4.3. Node got successfully added to engine and setup host network also done. When trying to ping host using “ovirtmgmt” as vNic profile for a VM, it is not even able to ping it’s host or any other machine on that same network. Also added a VLAN network which is passed via same uplink of Node interface where “Ovirtmgmt” is passed, that is also not working. Although this vnet is vnic type is VirtIO and state shows “UNKNOWN”, would this be a problem? Any help would be highly appreciated. Thanks Vijay Sachdeva Senior Manager – Service Delivery IndiQus Technologies O +91 11 4055 1411 | M +91 8826699409 www.indiqus.com

3 7

hyperconverged single node with SSD cache fails gluster creation
by thomas＠hoberg.net 01 Dec '19

01 Dec '19

I am seeing more success than failures at creating single and triple node hyperconverged setups after some weeks of experimentation so I am branching out to additional features: In this case the ability to use SSDs as cache media for hard disks. I tried first with a single node that combined caching and compression and that fails during the creation of LVMs. I tried again without the VDO compression, but actually the results where identical whilst VDO compression but without the LV cache worked ok. I tried various combinations, using less space etc., but the results are always the same and unfortunately rather cryptic (substituted the physical disk label with {disklabel}): TASK [gluster.infra/roles/backend_setup : Extend volume group] ***************** failed: [{hostname}] (item={u'vgname': u'gluster_vg_{disklabel}p1', u'cachethinpoolname': u'gluster_thinpool_gluster_vg_{disklabel}p1', u'cachelvname': u'cachelv_gluster_thinpool_gluster_vg_{disklabel}p1', u'cachedisk': u'/dev/sda4', u'cachemetalvname': u'cache_gluster_thinpool_gluster_vg_{disklabel}p1', u'cachemode': u'writeback', u'cachemetalvsize': u'70G', u'cachelvsize': u'630G'}) => {"ansible_loop_var": "item", "changed": false, "err": " Physical volume \"/dev/mapper/vdo_{disklabel}p1\" still in use\n", "item": {"cachedisk": "/dev/sda4", "cachelvname": "cachelv_gluster_thinpool_gluster_vg_{disklabel}p1", "cachelvsize": "630G", "cachemetalvname": "cache_gluster_thinpool_gluster_vg_{disklabel}p1", "cachemetalvsize": "70G", "cachemode": "writeback", "cachethinpoolname": "gluster_thinpool_gluster_vg_{disklabel}p1", "vgname": "gluster_vg_{disklabel}p1"}, "msg": "Unable to reduce gluster_vg_{disklabel}p1 by /dev/dm-15.", "rc": 5} somewhere within that I see something that points to a race condition ("still in use"). Unfortunately I have not been able to pinpoint the raw logs which are used at that stage and I wasn't able to obtain more info. At this point quite a bit of storage setup is already done, so rolling back for a clean new attempt, can be a bit complicated, with reboots to reconcile the kernel with data on disk. I don't actually believe it's related to single node and I'd be quite happy to move the creation of the SSD cache to a later stage, but in a VDO setup, this looks slightly complex to someone without intimate knowledge of LVS-with-cache-and-perhaps-thin/VDO/Gluster all thrown into one. Needless the feature set (SSD caching & compressed-dedup) sounds terribly attractive but when things don't just work, it's more terrifying.

5 7

Moving HostedEngine
by Joseph Goldman 28 Nov '19

28 Nov '19

Hi List, In one of my installs, I set up the first storage domain (and where the HostedEngine is) on a bigger NFS NAS - since then I have created a Gluster volume that spans the 3 hosts and I'm putting a few VM's in there for higher reliability (as SAN is single point of failure) namely I'd like to put HostedEngine in there so it stays up no matter what and can help report if issues occur (network issue to NAS, NAS dies etc etc) Looking through other posts and documentation, there's no real way to move the HostedEngine storage, is this correct? The solution I've seen is to backup the hosted engine DB, blow it away, and re-deploy it from the .backup file configuring it to the new storage domain in the deploy script - is this the only process? How likely is this to fail? Is it likely that all VM's and settings will be picked straight back up and continue to operate like normal? I dont have a test setup to play around with atm so just trying to gauge confidence in such a solution. Thanks, Joe

3 3

Migrate VM from oVirt to oVirt
by adrianquintero＠gmail.com 28 Nov '19

28 Nov '19

Hello, What would be the procedure to migrate a VM from oVirt to oVirt? Migrate from oVirt 4.2 running on Site A to oVirt 4.3 Site B. thanks!

5 7

Re: HostedEngine Deployment fails on AMD EPYC 7402P 4.3.7
by Strahil 28 Nov '19

28 Nov '19

The HostedEngine does it automatically, but the option that defines the OVF refresh interval is not accurate. Just power it up without that option (cluster in maintenance) and keep it running for a day. On the next day power it off and try to power it up via hosted-engine --vm-start. Best Regards, Strahil NikolovOn Nov 28, 2019 11:54, Ralf Schenk <rs(a)databay.de> wrote: > > Hello, > > I did something like that via "virsh edit HostedEngine". > > But how is the change written back to the shared storage ("hosted_storage" so it stays permanent for HA Engine ? > > I was able to boot up HostedEngine manually via virsh start after removing the required flag from XML (I first added a user to sasldb in /etc/libvirt/passwd.db to be able to log into libvirt). > > Bye > > > Am 28.11.2019 um 05:51 schrieb Strahil: > > Hi Ralf, > When the deployment fail - you can dump the xml from virsh , edit it, undefine the current HostedEngine and define your modified HostedEngine 's xml. > > Once you do that, you can try to start the > VM. > > Good luck. > > Best Regards, > Strahil Nikolov > > On Nov 27, 2019 18:28, Ralf Schenk <rs(a)databay.de> wrote: >> >> Hello, >> >> This week I tried to deploy Hosted Engine on Ovirt-Node-NG 4.3.7 based Host. >> >> At the time the locally deployed Engine ist copied to hosted-storage (in my case NFS) and deployment tries to start the Engine (via ovirt-ha-agent) this fails. >> >> QUEMU Log (/var/log/libvirt/qemu/HostedEngine.log) only shows "2019-11-27 16:17:16.833+0000: shutting down, reason=failed". >> >> Researching the cause is: The built Libvirt VM XML includes the feature "virt-ssbd" as requirement, which is simly not there. >> >> From VM XML: >> >> <cpu mode='custom' match='exact' check='partial'> >> <model fallback='allow'>EPYC</model> >> <topology sockets='16' cores='4' threads='1'/> >> <feature policy='require' name='ibpb'/> >> <feature policy='require' name='virt-ssbd'/> >> >> from cat /proc/cpuinfo: >> >> processor : 47 >> vendor_id : AuthenticAMD >> cpu family : 23 >> model : 49 >> model name : AMD EPYC 7402P 24-Core Processor >> stepping : 0 >> microcode : 0x830101c >> cpu MHz : 2800.000 >> cache size : 512 KB >> physical id : 0 >> siblings : 48 >> core id : 30 >> cpu cores : 24 >> api

1 0

Re: spice connection error
by Strahil 28 Nov '19

28 Nov '19

Check on host 'node3' in the Network configuration if you have a network out of sync or any clues about the error . Best Regards, Strahil NikolovOn Nov 28, 2019 11:44, Kim Kargaard <Kim.Kargaard(a)noroff.no> wrote: > > Hi, > > I am getting the attached error when trying to move the Display from the one network to the other within the cluster. I can't see any place to set an IP for the vnic that I want to set as the display network. > > Any thoughts? > > Kim > > On 28/11/2019, 06:41, "Strahil" <hunter86_bg(a)yahoo.com> wrote: > > As far as I know , the engine plays a role as a proxy during the establishment of the connection. > Check that you can reach both engine and the host from your system. > > For the same reason, I use noVNC - as you just need a single port to the engine in addition to the rest of the settings. > > Best Regards, > Strahil NikolovOn Nov 27, 2019 11:27, kim.kargaard(a)noroff.no wrote: > > > > Hi, > > > > When trying to connect from a remote network on the spice console to a VM, I get the following error: > > > > (remote-viewer:80195): virt-viewer-WARNING **: 11:05:22.322: Channel error: Could not connect to proxy server xx.xx.xx.xx: Socket I/O timed out > > > > I found that the display is set to the management network and not the VM networkn in the cluster logical network. However, when I try to set the other vlan to be the display network, I get the following error: > > > > Error while executing action: Cannot edit Network. IP address has to be set for the NIC that bears a role network. Network: student-vlan100, Nic: p2p1.100 on host node3 violates that rule. > > > > I am not sure what this means. Any ideas? > > > > Kind regards > > > > Kim > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org > > To unsubscribe send an email to users-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/6YEI3I4NCAHQO… > >

1 0

VDSM Errors see below
by rob.downer＠orbitalsystems.co.uk 28 Nov '19

28 Nov '19

I have removed all deployment of the hosted engine by running the following commands. ovirt-hosted-engine-cleanup vdsm-tool configure --force systemctl restart libvirtd systemctl restart vdsm on my hosts I have the following ovirt 1 is the host I ran the hosted engine setup. I have set the Gluster network to use the same subnet and set up forward and reverse DNS for the Gluster port network NIC's I had this working using a separate subnet but thought to try it on the same subnet to avoid any issues that may have occurred while using a separate network subnet. the main Host IP address is still showing in Unamanaged Connections on Ovirt 1 .. is this anything to be concerned about after running the commands above... I have restarted all machines. All come back with these VDSM errors... Node 1 [root@ovirt1 ~]# systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: inactive (dead) since Thu 2019-11-28 13:29:40 UTC; 37min ago Process: 31178 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh --post-stop (code=exited, status=0/SUCCESS) Process: 30721 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1 /dev/null -2 /dev/null /usr/share/vdsm/vdsmd (code=exited, status=0/SUCCESS) Main PID: 30721 (code=exited, status=0/SUCCESS) Nov 26 22:42:49 ovirt1.kvm.private vdsm[30721]: WARN MOM not available, KSM stats will be missing. Nov 26 22:42:49 ovirt1.kvm.private vdsm[30721]: WARN Not ready yet, ignoring event '|virt|VM_status|871ce9d5-417a-4278-8446-28b681760c1b' args={'871ce9d5-417a-4278-8446-28b681760c1b': {'status': 'Poweri... Nov 28 13:28:43 ovirt1.kvm.private vdsm[30721]: WARN File: /var/run/vdsm/trackedInterfaces/eno2 already removed Nov 28 13:29:26 ovirt1.kvm.private vdsm[30721]: WARN File: /var/lib/libvirt/qemu/channels/871ce9d5-417a-4278-8446-28b681760c1b.com.redhat.rhevm.vdsm already removed Nov 28 13:29:26 ovirt1.kvm.private vdsm[30721]: WARN File: /var/lib/libvirt/qemu/channel/target/domain-1-HostedEngineLocal/org.qemu.guest_agent.0 already removed Nov 28 13:29:39 ovirt1.kvm.private vdsm[30721]: WARN MOM not available. Nov 28 13:29:39 ovirt1.kvm.private vdsm[30721]: WARN MOM not available, KSM stats will be missing. Nov 28 13:29:39 ovirt1.kvm.private systemd[1]: Stopping Virtual Desktop Server Manager... Nov 28 13:29:39 ovirt1.kvm.private vdsmd_init_common.sh[31178]: vdsm: Running run_final_hooks Nov 28 13:29:40 ovirt1.kvm.private systemd[1]: Stopped Virtual Desktop Server Manager. Hint: Some lines were ellipsized, use -l to show in full. [root@ovirt1 ~]# 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 NODE 2 [root@ovirt2 ~]# systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-11-28 13:57:30 UTC; 1min 13s ago Process: 3626 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=0/SUCCESS) Main PID: 5418 (vdsmd) Tasks: 38 CGroup: /system.slice/vdsmd.service └─5418 /usr/bin/python2 /usr/share/vdsm/vdsmd Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: libvirt: Network Filter Driver error : Network filter not found: no nwfilter with matching name 'vdsm-no-mac-spoofing' Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: vdsm: Running dummybr Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: vdsm: Running tune_system Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: vdsm: Running test_space Nov 28 13:57:30 ovirt2.kvm.private vdsmd_init_common.sh[3626]: vdsm: Running test_lo Nov 28 13:57:30 ovirt2.kvm.private systemd[1]: Started Virtual Desktop Server Manager. Nov 28 13:57:32 ovirt2.kvm.private vdsm[5418]: WARN File: /var/run/vdsm/trackedInterfaces/eno1 already removed Nov 28 13:57:32 ovirt2.kvm.private vdsm[5418]: WARN File: /var/run/vdsm/trackedInterfaces/eno2 already removed Nov 28 13:57:32 ovirt2.kvm.private vdsm[5418]: WARN MOM not available. Nov 28 13:57:32 ovirt2.kvm.private vdsm[5418]: WARN MOM not available, KSM stats will be missing. [root@ovirt2 ~]# nodectl check Status: OK 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 ... OK [root@ovirt2 ~]# Node 3 [root@ovirt3 ~]# systemctl status vdsmd ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-11-28 13:57:08 UTC; 12min ago Process: 2849 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=0/SUCCESS) Main PID: 3220 (vdsmd) Tasks: 38 CGroup: /system.slice/vdsmd.service └─3220 /usr/bin/python2 /usr/share/vdsm/vdsmd Nov 28 13:57:07 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running nwfilter Nov 28 13:57:07 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running dummybr Nov 28 13:57:08 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running tune_system Nov 28 13:57:08 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running test_space Nov 28 13:57:08 ovirt3.kvm.private vdsmd_init_common.sh[2849]: vdsm: Running test_lo Nov 28 13:57:08 ovirt3.kvm.private systemd[1]: Started Virtual Desktop Server Manager. Nov 28 13:57:09 ovirt3.kvm.private vdsm[3220]: WARN File: /var/run/vdsm/trackedInterfaces/eno1 already removed Nov 28 13:57:09 ovirt3.kvm.private vdsm[3220]: WARN File: /var/run/vdsm/trackedInterfaces/eno2 already removed Nov 28 13:57:09 ovirt3.kvm.private vdsm[3220]: WARN MOM not available. Nov 28 13:57:09 ovirt3.kvm.private vdsm[3220]: WARN MOM not available, KSM stats will be missing. [root@ovirt3 ~]# nodectl check Status: OK 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 ... OK [root@ovirt3 ~]#

1 0

Re: HostedEngine Deployment fails on AMD EPYC 7402P 4.3.7
by Strahil 28 Nov '19

28 Nov '19

Hi Ralf, When the deployment fail - you can dump the xml from virsh , edit it, undefine the current HostedEngine and define your modified HostedEngine 's xml. Once you do that, you can try to start the VM. Good luck. Best Regards, Strahil NikolovOn Nov 27, 2019 18:28, Ralf Schenk <rs(a)databay.de> wrote: > > Hello, > > This week I tried to deploy Hosted Engine on Ovirt-Node-NG 4.3.7 based Host. > > At the time the locally deployed Engine ist copied to hosted-storage (in my case NFS) and deployment tries to start the Engine (via ovirt-ha-agent) this fails. > > QUEMU Log (/var/log/libvirt/qemu/HostedEngine.log) only shows "2019-11-27 16:17:16.833+0000: shutting down, reason=failed". > > Researching the cause is: The built Libvirt VM XML includes the feature "virt-ssbd" as requirement, which is simly not there. > > From VM XML: > > <cpu mode='custom' match='exact' check='partial'> > <model fallback='allow'>EPYC</model> > <topology sockets='16' cores='4' threads='1'/> > <feature policy='require' name='ibpb'/> > <feature policy='require' name='virt-ssbd'/> > > from cat /proc/cpuinfo: > > processor : 47 > vendor_id : AuthenticAMD > cpu family : 23 > model : 49 > model name : AMD EPYC 7402P 24-Core Processor > stepping : 0 > microcode : 0x830101c > cpu MHz : 2800.000 > cache size : 512 KB > physical id : 0 > siblings : 48 > core id : 30 > cpu cores : 24 > apicid : 61 > initial apicid : 61 > fpu : yes > fpu_exception : yes > cpuid level : 16 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc art rep_good nopl xtopology nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 cpb cat_l3 cdp_l3 hw_pstate sme retpoline_amd ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif umip overflow_recov succor smca > bogomips : 5600.12 > TLB size : 3072 4K pages > clflush size : 64 > cache_alignment : 64 > address sizes : 43 bits physical, 48 bits virtual > power management: ts ttp tm hwpstate cpb eff_freq_ro [13] [14] > > Any solution/workaround available ?

2 1

Re: Moving HostedEngine
by Strahil 27 Nov '19

27 Nov '19

It is highly 'super duper' not recommended to do that. Also, consider using thinLVM (requirement for gluster snapshots) for a brick of the separate gluster volume. I'm using the 3rd partirion of my OS SSD to host my gluster's volume and I have no issues so far. Best Regards, Strahil NikolovOn Nov 28, 2019 01:05, Joseph Goldman <joseph(a)goldman.id.au> wrote: > > So I can't host OTHER VM's on this gluster volume? If its already a running GLuser for other VMs i can't now re-reploy HE in that gluster volume? > > On 2019-11-28 3:27 AM, Alan G wrote: > > I've had to do this a couple of times and always ended up with a working system in the end. > > As a fall back option (although I've never had to use it) I have a backup engine VM running completely outside of oVIrt (ESXi host in my case). Then if the hosted_engine deploy fails for any reason you can restore onto the backup vm as a temp solution while you work through the hosted engine deploy issues. > > A few things that come to mind: - > > * You will need a dedicated gluster volume for hosted_storage and it needs to be replica+arbiter. >> >> * Make sure you put the cluster in global maint mode before performing the engine backup, I recall having issues with the restore when I didn't do that. >> * Migrate all other VMs off the host running Engine before doing the backup. This will be the host you will restore onto. >> >> >> ---- On Wed, 27 Nov 2019 09:46:23 +0000 Joseph Goldman <joseph(a)goldman.id.au> wrote ---- >> >>> Hi List, >>> >>> In one of my installs, I set up the first storage domain (and where >>> the HostedEngine is) on a bigger NFS NAS - since then I have created a >>> Gluster volume that spans the 3 hosts and I'm putting a few VM's in >>> there for higher reliability (as SAN is single point of failure) namely >>> I'd like to put HostedEngine in there so it stays up no matter what and >>> can help report if issues occur (network issue to NAS, NAS dies etc etc) >>> >>> Looking through other posts and documentation, there's no real way to >>> move the HostedEngine storage, is this correct? The solution I've seen >>> is to backup the hosted engine DB, blow it away, and re-deploy it from >>> the .backup file configuring it to the new storage domain in the deploy >>> script - is this the only process? How likely is this to fail? Is it >>> likely that all VM's and settings will be picked straight back up and >>> continue to operate like normal? I dont have a test setup to play around >>> with atm so just trying to gauge confidence in such a solution. >>> >>> Thanks, >>> Joe >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct:

1 0

Re: Moving HostedEngine
by Strahil 27 Nov '19

27 Nov '19

Hi Joseph, It is mandatory to create a dedicated gluster volume for the HostedEngine. There is a thread which explains why and the risks of not following these guidlines. You can set the volume on thinLVM, so you can snapshot your gluster's volume before patching of the engine (of course you have to shutdown the engine in advance). About the transfer, the safest way is to backup & restore as you are not migrating from 1 type of storage domain to another of same type. Yet, I can't help you with that procedure - as I have never done it. Best Regards, Strahil NikolovOn Nov 27, 2019 11:46, Joseph Goldman <joseph(a)goldman.id.au> wrote: > > Hi List, > > In one of my installs, I set up the first storage domain (and where > the HostedEngine is) on a bigger NFS NAS - since then I have created a > Gluster volume that spans the 3 hosts and I'm putting a few VM's in > there for higher reliability (as SAN is single point of failure) namely > I'd like to put HostedEngine in there so it stays up no matter what and > can help report if issues occur (network issue to NAS, NAS dies etc etc) > > Looking through other posts and documentation, there's no real way to > move the HostedEngine storage, is this correct? The solution I've seen > is to backup the hosted engine DB, blow it away, and re-deploy it from > the .backup file configuring it to the new storage domain in the deploy > script - is this the only process? How likely is this to fail? Is it > likely that all VM's and settings will be picked straight back up and > continue to operate like normal? I dont have a test setup to play around > with atm so just trying to gauge confidence in such a solution. > > Thanks, > Joe > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZTO6Q3UTEDJCD…

1 0

Re: spice connection error
by Strahil 27 Nov '19

27 Nov '19

As far as I know , the engine plays a role as a proxy during the establishment of the connection. Check that you can reach both engine and the host from your system. For the same reason, I use noVNC - as you just need a single port to the engine in addition to the rest of the settings. Best Regards, Strahil NikolovOn Nov 27, 2019 11:27, kim.kargaard(a)noroff.no wrote: > > Hi, > > When trying to connect from a remote network on the spice console to a VM, I get the following error: > > (remote-viewer:80195): virt-viewer-WARNING **: 11:05:22.322: Channel error: Could not connect to proxy server xx.xx.xx.xx: Socket I/O timed out > > I found that the display is set to the management network and not the VM networkn in the cluster logical network. However, when I try to set the other vlan to be the display network, I get the following error: > > Error while executing action: Cannot edit Network. IP address has to be set for the NIC that bears a role network. Network: student-vlan100, Nic: p2p1.100 on host node3 violates that rule. > > I am not sure what this means. Any ideas? > > Kind regards > > Kim > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/6YEI3I4NCAHQO…

1 0

Re: Engine deployment last step.... Can anyone help ?
by Strahil 27 Nov '19

27 Nov '19

Hi Rob, Can you check the gluster's volume ? gluster volume status engine gluster volume heal engine info summary Still, this is strange that the firewall is having such differences. Fastest way to sync that node to the settings from the other is to: 1. Backup /etc/firewalld 2. Remove /etc/firewalld 3. Copy /etc/firewalld from another node (either scp or rsync wil do) 4. Restart the firewalld daemon 5. Make a test firewalld reload Best Regards, Strahil NikolovOn Nov 27, 2019 00:09, Rob <rob.downer(a)orbitalsystems.co.uk> wrote: > > Is this the issue ? > > on the deployment host the firewall is active but only on eno2, eno1 appears to have decided to be unmanaged … > > also the deployment host has 17 rules active > > the other two have 7 each… > > > Zone > Interfaces > IP Range > Public > default > eno2 > * > > Unmanaged Interfaces > > > Name > > IP Address > > Sending > > Receiving > > ;vdsmdummy; > > > Inactive > > eno1 > > > > > ovirtmgmt > > 192.168.100.38/24 > > > > virbr0-nic > > >> >> On 25 Nov 2019, at 17:16, Parth Dhanjal <dparth(a)redhat.com> wrote: >> >> Rather than disabling firewalld, >> You can add the ports and restart the firewalld service >> >> # firewall-cmd --add-service=cockpit >> >> # firewall-cmd --add-service=cockpit --permanent >> >> >> >> On Mon, Nov 25, 2019 at 10:43 PM Amit Bawer <abawer(a)redhat.com> wrote: >>> >>> firewalld is running? >>> >>> systemctl disable --now firewalld >>> >>> On Monday, November 25, 2019, Rob <rob.downer(a)orbitalsystems.co.uk> wrote: >>>> >>>> It can’t be DNS, since the engine runs on a separate network anyway ie front end, so why can’t it reach the Volume I wonder >>>> >>>> >>>>> On 25 Nov 2019, at 12:55, Gobinda Das <godas(a)redhat.com> wrote: >>>>> >>>>> There could be two reason >>>>> 1- Your gluster service may not be running. >>>>> 2- In Storage Connection there mentioned <volumename> may not exists >>>>> >>>>> can you please paste the output of "gluster volume status" ? >>>>> >>>>> On Mon, Nov 25, 2019 at 5:03 PM Rob <rob.downer(a)orbitalsystems.co.uk> wrote: >>>>>> >>>>>> [ INFO ] skipping: [localhost] >>>>>> [ INFO ] TASK [ovirt.hosted_engine_setup : Add glusterfs storage domain] >>>>>> [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[Failed to fetch Gluster Volume List]". HTTP response code is 400. >>>>>> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Failed to fetch Gluster Volume List]\". HTTP response code is 400.”} >>>>>> >>>>>> >>>>>>> On 25 Nov 2019, at 09:16, Rob <rob.downer(a)orbitalsystems.co.uk> wrote: >>>>>>> >>>>>>> Yes, >>>>>>> >>>>>>> I’ll restart all Nodes after wiping the failed setup of Hosted engine using. >>>>>>> >>>>>>> ovirt-hosted-engine-cleanup >>>>>>> vdsm-tool configure --force >>>>>>> systemctl restart libvirtd >>>>>>> systemctl restart vdsm >>>>>>> >>>>>>> although last time I did >>>>>>> >>>>>>> systemctl restart vdsm >>>>>>> >>>>>>> VDSM did not restart maybe that is OK as Hosted Engine was then de deployed or is that the issue ? >>>>>>> >>>>>>> >>>>>>>> On 25 Nov 2019, at 09:13, Parth Dhanjal <dparth(a)redhat.com> wrote: >>>>>>>> >>>>>>>> Can you please share the error in case it fails again? >>>>>>>> >>>>>>>> On Mon, Nov 25, 2019 at 2:42 PM Rob <rob.downer(a)orbitalsystems.co.uk> wrote: >>>>>>>>> >>>>>>>>> hmm, I’’l try again, that failed last time. >>>>>>>>> >>>>>>>>> >>>>>>>>>> On 25 Nov 2019, at 09:08, Parth Dhanjal <dparth(a)redhat.com> wrote: >>>>>>>>>> >>>>>>>>>> Hey! >>>>>>>>>> >>>>>>>>>> For >>>>>>>>>> Storage Connection you can add - <hostname1>:/engine >>>>>>>>>> And for >>>>>>>>>> Mount Options - backup-volfile-servers=<hostname2>:<hostname3> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Nov 25, 2019 at 2:31 PM <rob.downer(a)orbitalsystems.co.uk> wrote: >>>>>>>>>>> >>>>>>>>>>> So... >>>>>>>>>>> >>>>>>>>>>> I have got to the last step >>>>>>>>>>> >>>>>>>>>>> 3 Machines with Gluster Storage configured however at the last screen >>>>>>>>>>> >>>>>>>>>>> ....Deploying the Engine to Gluster and the wizard does not auto fill the two fields >>>>>>>>>>> >>>>>>>>>>> Hosted Engine Deployment >>>>>>>>>>> >>>>>>>>>>> Storage Connection >>>>>>>>>>> and >>>>>>>>>>> Mount Options >>>>>>>>>>> >>>>>>>>>>> I also had to expand /tmp as it was not big enough to fit the engine before moving... >>>>>>>>>>> >>>>>>>>>>> What can I do to get the auto complete sorted out ? >>>>>>>>>>> >>>>>>>>>>> I have tried entering ovirt1.kvm.private:/gluster_lv_engine - The Volume name >>>>>>>>>>> and >>>>>>>>>>> ovirt1.kvm.private:/gluster_bricks/engine >>>>>>>>>>> >>>>>>>>>>> Ovirt1 being the actual machine I'm running this on. >>>>>>>>>>> >>>>>>>>>>> Thanks >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Users mailing list -- users(a)ovirt.org >>>>>>>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>>>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>>>>>>>>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >>>>>>>>>>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/NL4HS6MIKWQAG… >>>>>>>>> >>>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Users mailing list -- users(a)ovirt.org >>>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>>>>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >>>>>>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/LQ5YXX7IVV6ZP… >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Users mailing list -- users(a)ovirt.org >>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>>>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >>>>>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VHQ3LTES6ABPL… >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> >>>>> Thanks, >>>>> Gobinda >>>> >>>> >

1 0

HostedEngine Deployment fails on AMD EPYC 7402P 4.3.7
by Ralf Schenk 27 Nov '19

27 Nov '19

Hello, This week I tried to deploy Hosted Engine on Ovirt-Node-NG 4.3.7 based Host. At the time the locally deployed Engine ist copied to hosted-storage (in my case NFS) and deployment tries to start the Engine (via ovirt-ha-agent) this fails. QUEMU Log (/var/log/libvirt/qemu/HostedEngine.log) only shows "2019-11-27 16:17:16.833+0000: shutting down, reason=failed". Researching the cause is: The built Libvirt VM XML includes the feature "virt-ssbd" as requirement, which is simly not there. From VM XML: <cpu mode='custom' match='exact' check='partial'> <model fallback='allow'>EPYC</model> <topology sockets='16' cores='4' threads='1'/> <feature policy='require' name='ibpb'/> <feature policy='require' name='virt-ssbd'/> from cat /proc/cpuinfo: processor : 47 vendor_id : AuthenticAMD cpu family : 23 model : 49 model name : AMD EPYC 7402P 24-Core Processor stepping : 0 microcode : 0x830101c cpu MHz : 2800.000 cache size : 512 KB physical id : 0 siblings : 48 core id : 30 cpu cores : 24 apicid : 61 initial apicid : 61 fpu : yes fpu_exception : yes cpuid level : 16 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc art rep_good nopl xtopology nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 cpb cat_l3 cdp_l3 hw_pstate sme retpoline_amd ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif umip overflow_recov succor smca bogomips : 5600.12 TLB size : 3072 4K pages clflush size : 64 cache_alignment : 64 address sizes : 43 bits physical, 48 bits virtual power management: ts ttp tm hwpstate cpb eff_freq_ro [13] [14] Any solution/workaround available ? -- *Ralf Schenk* fon +49 (0) 24 05 / 40 83 70 fax +49 (0) 24 05 / 40 83 759 mail *rs(a)databay.de* <mailto:rs@databay.de> *Databay AG* Jens-Otto-Krag-Straße 11 D-52146 Würselen *www.databay.de* <http://www.databay.de> Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202 Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm. Philipp Hermanns Aufsichtsratsvorsitzender: Wilhelm Dohmen ------------------------------------------------------------------------

1 0

Certificate of host is invalid
by Jon bae 27 Nov '19

27 Nov '19

Hello everybody, since last update to 4.3.7 I get this error message: Certificate of host *host.name <http://host.name>* is invalid. The certificate doesn't contain valid subject alternative name, please enroll new certificate for the host. Have you an idea of how I can fix that? Regards Jonathan

1 0

spice connection error
by kim.kargaard＠noroff.no 27 Nov '19

27 Nov '19

Hi, When trying to connect from a remote network on the spice console to a VM, I get the following error: (remote-viewer:80195): virt-viewer-WARNING **: 11:05:22.322: Channel error: Could not connect to proxy server xx.xx.xx.xx: Socket I/O timed out I found that the display is set to the management network and not the VM networkn in the cluster logical network. However, when I try to set the other vlan to be the display network, I get the following error: Error while executing action: Cannot edit Network. IP address has to be set for the NIC that bears a role network. Network: student-vlan100, Nic: p2p1.100 on host node3 violates that rule. I am not sure what this means. Any ideas? Kind regards Kim

1 0

Engine deployment last step.... Can anyone help ?
by rob.downer＠orbitalsystems.co.uk 26 Nov '19

26 Nov '19

So... I have got to the last step 3 Machines with Gluster Storage configured however at the last screen ....Deploying the Engine to Gluster and the wizard does not auto fill the two fields Hosted Engine Deployment Storage Connection and Mount Options I also had to expand /tmp as it was not big enough to fit the engine before moving... What can I do to get the auto complete sorted out ? I have tried entering ovirt1.kvm.private:/gluster_lv_engine - The Volume name and ovirt1.kvm.private:/gluster_bricks/engine Ovirt1 being the actual machine I'm running this on. Thanks

5 16

Re: Engine deployment last step.... Can anyone help ?
by Strahil 26 Nov '19

26 Nov '19

You need to set it also permanent via '--permanent', otherwise after a reload - it's gone. Best Regards, Strahil NikolovOn Nov 25, 2019 19:51, Rob <rob.downer(a)orbitalsystems.co.uk> wrote: > > [root@ovirt1 ~]# firewall-cmd --add-service=cockpit > Warning: ALREADY_ENABLED: 'cockpit' already in 'public' > success > [root@ovirt1 ~]# > > > >> On 25 Nov 2019, at 17:16, Parth Dhanjal <dparth(a)redhat.com> wrote: >> >> Rather than disabling firewalld, >> You can add the ports and restart the firewalld service >> >> # firewall-cmd --add-service=cockpit >> >> # firewall-cmd --add-service=cockpit --permanent >> >> >> >> On Mon, Nov 25, 2019 at 10:43 PM Amit Bawer <abawer(a)redhat.com> wrote: >>> >>> firewalld is running? >>> >>> systemctl disable --now firewalld >>> >>> On Monday, November 25, 2019, Rob <rob.downer(a)orbitalsystems.co.uk> wrote: >>>> >>>> It can’t be DNS, since the engine runs on a separate network anyway ie front end, so why can’t it reach the Volume I wonder >>>> >>>> >>>>> On 25 Nov 2019, at 12:55, Gobinda Das <godas(a)redhat.com> wrote: >>>>> >>>>> There could be two reason >>>>> 1- Your gluster service may not be running. >>>>> 2- In Storage Connection there mentioned <volumename> may not exists >>>>> >>>>> can you please paste the output of "gluster volume status" ? >>>>> >>>>> On Mon, Nov 25, 2019 at 5:03 PM Rob <rob.downer(a)orbitalsystems.co.uk> wrote: >>>>>> >>>>>> [ INFO ] skipping: [localhost] >>>>>> [ INFO ] TASK [ovirt.hosted_engine_setup : Add glusterfs storage domain] >>>>>> [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[Failed to fetch Gluster Volume List]". HTTP response code is 400. >>>>>> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Failed to fetch Gluster Volume List]\". HTTP response code is 400.”} >>>>>> >>>>>> <

2 1

Cannot obtain information from export domain
by Arthur Rodrigues Stilben 26 Nov '19

26 Nov '19

Hello everyone, I'm trying to export a virtual machine, but I'm getting the following error: 2019-11-26 16:30:06,250-02 ERROR [org.ovirt.engine.core.bll.exportimport.GetVmsFromExportDomainQuery] (default task-22) [b9a0b9d5-2127-4002-9cee-2e3525bccc89] Exception: org.ovirt.engine.core.common.errors.EngineException: EngineException: org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException: IRSGenericException: IRSErrorException: Failed to GetVmsInfoVDS, error = Storage domain does not exist: (u'5ac6c35d-0406-4a06-a682-ed8fb2d1933f',), code = 358 (Failed with error StorageDomainDoesNotExist and code 358) 2019-11-26 16:30:06,249-02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-22) [b9a0b9d5-2127-4002-9cee-2e3525bccc89] EVENT_ID: IMPORTEXPORT_GET_VMS_INFO_FAILED(200), Correlation ID: null, Call Stack: null, Custom ID: null, Custom Event ID: -1, Message: Failed to retrieve VM/Templates information from export domain BackupMV The version of the oVirt that I am using is 4.1. Att, -- Arthur Rodrigues Stilben

1 0

Re: Fail to attach/create disk from template when running via Ansible
by Vrgotic, Marko 26 Nov '19

26 Nov '19

Hi Martin, Resending as delivery of my last email failed. From: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com> Date: Monday, 25 November 2019 at 09:53 To: Martin Perina <mperina(a)redhat.com>, Eyal Shenitzky <eshenitz(a)redhat.com> Cc: Ryan Barry <rbarry(a)redhat.com>, Ondra Machacek <omachace(a)redhat.com>, "users(a)ovirt.org" <users(a)ovirt.org>, Darko Stojchev <D.Stojchev(a)activevideo.com>, Tal Nisan <tnisan(a)redhat.com> Subject: Re: [ovirt-users] Re: Fail to attach/create disk from template when running via Ansible Hi Martin, Thank you for driving this issue. I have updated the bug ticket on bugzilla, as I was able to reproduce it via WebUI as well. Regarding my other question, How to clean up Locked Instances”, not to lose sight from it: I have attached the engine and server log as requested (below), but I did not get any answer yet. If more information is needed to proceed, please let me know. Kindly awaiting your reply. ----- kind regards/met vrindelijke groet Marko Vrgotic ActiveVideo From: Martin Perina <mperina(a)redhat.com> Date: Thursday, 21 November 2019 at 10:00 To: Eyal Shenitzky <eshenitz(a)redhat.com> Cc: Ryan Barry <rbarry(a)redhat.com>, Ondra Machacek <omachace(a)redhat.com>, "users(a)ovirt.org" <users(a)ovirt.org>, Darko Stojchev <D.Stojchev(a)activevideo.com>, "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com>, Tal Nisan <tnisan(a)redhat.com> Subject: Re: [ovirt-users] Re: Fail to attach/create disk from template when running via Ansible On Thu, Nov 21, 2019 at 9:17 AM Martin Perina <mperina(a)redhat.com<mailto:mperina@redhat.com>> wrote: Hi Eyal, could you please take a look? There is NPE cause most probably by passing invalid vdsId from CreateSnapshotCommand ... Just noticed that Marko created https://bugzilla.redhat.com/show_bug.cgi?id=1772853 to track the issue so let's continue the investigation there ... Thanks, Martin On Thu, Nov 21, 2019 at 8:51 AM Vrgotic, Marko <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> wrote: Hi Martin, The engine.log and server.log files attached. Here is the list of servers from this morning, in last hour, if it helps with going through the logs. [cid:16e8d08b4114cff311] The ones from previous screenshot are there since few days ago. If any additional info or tests are needed, let me know. Kindly awaiting your reply. ----- kind regards/met vrindelijke groet Marko Vrgotic ActiveVideo From: Martin Perina <mperina(a)redhat.com<mailto:mperina@redhat.com>> Date: Thursday, 21 November 2019 at 08:34 To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>>, Ryan Barry <rbarry(a)redhat.com<mailto:rbarry@redhat.com>> Cc: Ondra Machacek <omachace(a)redhat.com<mailto:omachace@redhat.com>>, "users(a)ovirt.org<mailto:users@ovirt.org>" <users(a)ovirt.org<mailto:users@ovirt.org>>, Darko Stojchev <D.Stojchev(a)activevideo.com<mailto:D.Stojchev@activevideo.com>> Subject: Re: [ovirt-users] Re: Fail to attach/create disk from template when running via Ansible Hi Marko, could you please share your engine.log and server.log? Thanks, Martin On Thu, Nov 21, 2019 at 8:31 AM Vrgotic, Marko <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> wrote: Hi Martin and Ondra, I cannot find clean way to remove the entities which are in unknown (probably locked) state. Due to the issue I reported below, the entities I try to create end up in, I assume, locked state. [A screenshot of a cell phone Description automatically generated] Due to this state, I cannot remove them from UI, and if I try to remove them using Ansible, get following error: FAILED! => {"changed": false, "msg": "Timeout exceed while waiting on result state of the entity." Would you be so kind to provide me with steps to clean up these locked instances? Kindly awaiting your reply. ----- kind regards/met vrindelijke groet Marko Vrgotic ActiveVideo From: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> Date: Friday, 15 November 2019 at 11:34 To: Martin Perina <mperina(a)redhat.com<mailto:mperina@redhat.com>> Cc: Ondra Machacek <omachace(a)redhat.com<mailto:omachace@redhat.com>>, "users(a)ovirt.org<mailto:users@ovirt.org>" <users(a)ovirt.org<mailto:users@ovirt.org>>, Darko Stojchev <D.Stojchev(a)activevideo.com<mailto:D.Stojchev@activevideo.com>> Subject: Re: [ovirt-users] Re: Fail to attach/create disk from template when running via Ansible Hi Martin, Here is the BUG URI: https://bugzilla.redhat.com/show_bug.cgi?id=1772853 I am not sure if I selected correct component and team, but its created. If any additional information is required, do not hesitate to let me know. Kindly awaiting your reply. ----- kind regards/met vrindelijke groet Marko Vrgotic ActiveVideo From: Martin Perina <mperina(a)redhat.com<mailto:mperina@redhat.com>> Date: Friday, 15 November 2019 at 11:07 To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> Cc: Ondra Machacek <omachace(a)redhat.com<mailto:omachace@redhat.com>>, "users(a)ovirt.org<mailto:users@ovirt.org>" <users(a)ovirt.org<mailto:users@ovirt.org>>, Darko Stojchev <D.Stojchev(a)activevideo.com<mailto:D.Stojchev@activevideo.com>> Subject: Re: [ovirt-users] Re: Fail to attach/create disk from template when running via Ansible On Fri, Nov 15, 2019 at 11:05 AM Vrgotic, Marko <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> wrote: Hi Martin, You mean to create a bug under Ansible? Sure. No, in bugzilla for oVirt, it doesn't seem to me as ansible modules bug, but rather some issue in engine. Thanks, Martin ----- kind regards/met vrindelijke groet Marko Vrgotic ActiveVideo From: Martin Perina <mperina(a)redhat.com<mailto:mperina@redhat.com>> Date: Friday, 15 November 2019 at 10:30 To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> Cc: Ondra Machacek <omachace(a)redhat.com<mailto:omachace@redhat.com>>, "users(a)ovirt.org<mailto:users@ovirt.org>" <users(a)ovirt.org<mailto:users@ovirt.org>>, Darko Stojchev <D.Stojchev(a)activevideo.com<mailto:D.Stojchev@activevideo.com>> Subject: Re: [ovirt-users] Re: Fail to attach/create disk from template when running via Ansible Hi Marko, could you please create a bug for that and attach full SOS collection logs from engine and relevant host? Thanks, Martin On Wed, Nov 13, 2019 at 2:54 AM Vrgotic, Marko <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> wrote: Hi Ondra, I have rebuilt the staging with 4.3.6 and still same issue. Images are there, I can again create VM via UI, but not via Ansible. Here is the output of the complete run form engine.log: 2019-11-12 12:09:00,457Z INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-49) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2019-11-12 12:09:00,978Z INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-49) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2019-11-12 12:09:01,538Z INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-49) [233de27] Running command: CreateUserSessionCommand internal: false. 2019-11-12 12:09:01,549Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-49) [233de27] EVENT_ID: USER_VDC_LOGIN(30), User admin@internal-authz connecting from '172.16.105.206' using session 'bsgNpfGJTNtzuuQWSyXVJqHhpLK4TY9TQRERWxxzGtpHonoqdk7WIHGZ7mID2+QkBKH9bPp8HVhyvDu66tzPnQ==' logged in. 2019-11-12 12:09:01,691Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Lock Acquired to object 'EngineLock:{exclusiveLocks='[centos-testvm-a910=VM_NAME]', sharedLocks='[400688e8-3c5b-4cca-9ef8-bbb6c79d54ed=DISK, 819aecf6-c83d-4470-9915-e309390d8098=TEMPLATE]'}' 2019-11-12 12:09:01,773Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Running command: AddVmCommand internal: false. Entities affected : ID: d3c90169-ecc8-46a0-a4ec-7c3d99b81b61 Type: ClusterAction group CREATE_VM with role type USER, ID: 819aecf6-c83d-4470-9915-e309390d8098 Type: VmTemplateAction group CREATE_VM with role type USER, ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: StorageAction group CREATE_DISK with role type USER 2019-11-12 12:09:01,866Z INFO [org.ovirt.engine.core.bll.AddRngDeviceCommand] (default task-49) [4d4703a1] Running command: AddRngDeviceCommand internal: true. Entities affected : ID: 6343c55a-c67e-4d75-a767-dfc9412006e6 Type: VMAction group EDIT_VM_PROPERTIES with role type USER 2019-11-12 12:09:01,876Z INFO [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default task-49) [4d4703a1] START, SetVmStatusVDSCommand( SetVmStatusVDSCommandParameters:{vmId='6343c55a-c67e-4d75-a767-dfc9412006e6', status='ImageLocked', exitStatus='Normal'}), log id: 4eedcefb 2019-11-12 12:09:01,887Z INFO [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default task-49) [4d4703a1] FINISH, SetVmStatusVDSCommand, return: , log id: 4eedcefb 2019-11-12 12:09:01,906Z INFO [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Running command: CreateSnapshotFromTemplateCommand internal: true. Entities affected : ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: Storage 2019-11-12 12:09:01,928Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] START, CreateVolumeVDSCommand( CreateVolumeVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', imageSizeInBytes='8589934592', volumeFormat='COW', newImageId='7270dd54-a075-4b14-aca3-7c2a118057f0', imageType='Sparse', newImageDescription='', imageInitialSizeInBytes='0', imageId='767c6837-5191-4650-a49d-abca7d69a708', sourceImageGroupId='400688e8-3c5b-4cca-9ef8-bbb6c79d54ed'}), log id: 2dfac68e 2019-11-12 12:09:02,009Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] FINISH, CreateVolumeVDSCommand, return: 7270dd54-a075-4b14-aca3-7c2a118057f0, log id: 2dfac68e 2019-11-12 12:09:02,014Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] CommandAsyncTask::Adding CommandMultiAsyncTasks object for command 'fb915b7e-4814-4e93-a3ef-4f40c4e3c41b' 2019-11-12 12:09:02,014Z INFO [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] CommandMultiAsyncTasks::attachTask: Attaching task '0eb09758-113f-43b9-aa67-97d2e5a57e05' to command 'fb915b7e-4814-4e93-a3ef-4f40c4e3c41b'. 2019-11-12 12:09:02,027Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Adding task '0eb09758-113f-43b9-aa67-97d2e5a57e05' (Parent Command 'CreateSnapshotFromTemplate', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling hasn't started yet.. 2019-11-12 12:09:02,098Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] EVENT_ID: USER_ADD_VM_STARTED(37), VM centos-testvm-a910 creation was initiated by admin@internal-authz. 2019-11-12 12:09:02,098Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] BaseAsyncTask::startPollingTask: Starting to poll task '0eb09758-113f-43b9-aa67-97d2e5a57e05'. 2019-11-12 12:09:02,758Z INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-19) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Command 'AddVm' (id: '97d4103b-acef-4b55-a379-71a1baa04a4f') waiting on child command id: 'fb915b7e-4814-4e93-a3ef-4f40c4e3c41b' type:'CreateSnapshotFromTemplate' to complete 2019-11-12 12:09:04,773Z INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-52) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Command 'AddVm' (id: '97d4103b-acef-4b55-a379-71a1baa04a4f') waiting on child command id: 'fb915b7e-4814-4e93-a3ef-4f40c4e3c41b' type:'CreateSnapshotFromTemplate' to complete 2019-11-12 12:09:06,117Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-26) [] Polling and updating Async Tasks: 1 tasks, 1 tasks to poll now 2019-11-12 12:09:06,121Z ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksStatusesVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-26) [] Failed in 'HSMGetAllTasksStatusesVDS' method 2019-11-12 12:09:06,128Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-26) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt-staging-hv-02.avinity.tv<http://ovirt-staging-hv-02.avinity.tv> command HSMGetAllTasksStatusesVDS failed: Invalid parameter: 'capacity=8589934592' 2019-11-12 12:09:06,128Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-26) [] SPMAsyncTask::PollTask: Polling task '0eb09758-113f-43b9-aa67-97d2e5a57e05' (Parent Command 'CreateSnapshotFromTemplate', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned status 'finished', result 'cleanSuccess'. 2019-11-12 12:09:06,131Z ERROR [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-26) [] BaseAsyncTask::logEndTaskFailure: Task '0eb09758-113f-43b9-aa67-97d2e5a57e05' (Parent Command 'CreateSnapshotFromTemplate', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended with failure: -- Result: 'cleanSuccess' -- Message: 'VDSGenericException: VDSErrorException: Failed to HSMGetAllTasksStatusesVDS, error = Invalid parameter: 'capacity=8589934592', code = 100', -- Exception: 'VDSGenericException: VDSErrorException: Failed to HSMGetAllTasksStatusesVDS, error = Invalid parameter: 'capacity=8589934592', code = 100' 2019-11-12 12:09:06,133Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-26) [] CommandAsyncTask::endActionIfNecessary: All tasks of command 'fb915b7e-4814-4e93-a3ef-4f40c4e3c41b' has ended -> executing 'endAction' 2019-11-12 12:09:06,133Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-26) [] CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: 'fb915b7e-4814-4e93-a3ef-4f40c4e3c41b'): calling endAction '. 2019-11-12 12:09:06,133Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-274926) [] CommandAsyncTask::endCommandAction [within thread] context: Attempting to endAction 'CreateSnapshotFromTemplate', 2019-11-12 12:09:06,137Z INFO [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Command [id=fb915b7e-4814-4e93-a3ef-4f40c4e3c41b]: Updating status to 'FAILED', The command end method logic will be executed by one of its parent commands. 2019-11-12 12:09:06,137Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'CreateSnapshotFromTemplate' completed, handling the result. 2019-11-12 12:09:06,137Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'CreateSnapshotFromTemplate' succeeded, clearing tasks. 2019-11-12 12:09:06,137Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] SPMAsyncTask::ClearAsyncTask: Attempting to clear task '0eb09758-113f-43b9-aa67-97d2e5a57e05' 2019-11-12 12:09:06,137Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', taskId='0eb09758-113f-43b9-aa67-97d2e5a57e05'}), log id: baaf58a 2019-11-12 12:09:06,138Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] START, HSMClearTaskVDSCommand(HostName = ovirt-staging-hv-02.avinity.tv<http://ovirt-staging-hv-02.avinity.tv>, HSMTaskGuidBaseVDSCommandParameters:{hostId='3c70c563-e32e-4352-b1e1-f6bcc41f77e2', taskId='0eb09758-113f-43b9-aa67-97d2e5a57e05'}), log id: 7321c57d 2019-11-12 12:09:06,147Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] FINISH, HSMClearTaskVDSCommand, return: , log id: 7321c57d 2019-11-12 12:09:06,147Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] FINISH, SPMClearTaskVDSCommand, return: , log id: baaf58a 2019-11-12 12:09:06,152Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] BaseAsyncTask::removeTaskFromDB: Removed task '0eb09758-113f-43b9-aa67-97d2e5a57e05' from DataBase 2019-11-12 12:09:06,152Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] CommandAsyncTask::HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object for entity 'fb915b7e-4814-4e93-a3ef-4f40c4e3c41b' 2019-11-12 12:09:08,790Z INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-34) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Command 'AddVm' id: '97d4103b-acef-4b55-a379-71a1baa04a4f' child commands '[fb915b7e-4814-4e93-a3ef-4f40c4e3c41b]' executions were completed, status 'FAILED' 2019-11-12 12:09:09,821Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.AddVmCommand' with failure. 2019-11-12 12:09:09,825Z ERROR [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' with failure. 2019-11-12 12:09:09,835Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [44f6ef0c] Running command: RemoveImageCommand internal: true. Entities affected : ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: Storage 2019-11-12 12:09:09,873Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [44f6ef0c] START, DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'}), log id: 28915db3 2019-11-12 12:09:09,907Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [44f6ef0c] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:09,907Z ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [44f6ef0c] Command 'DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'})' execution failed: IRSGenericException: IRSErrorException: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:09,907Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [44f6ef0c] FINISH, DeleteImageGroupVDSCommand, return: , log id: 28915db3 2019-11-12 12:09:09,907Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [44f6ef0c] Disk '56ddac45-1913-4d24-af97-2f969fc3fa2e' doesn't exist on storage domain '78bfcb57-3a0d-4a71-a3f8-480ebae37c74', rolling forward 2019-11-12 12:09:09,918Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [44f6ef0c] Removed task '25bf448d-9271-4a85-ad9b-9c63012753ac' from DataBase 2019-11-12 12:09:09,983Z INFO [org.ovirt.engine.core.utils.transaction.TransactionSupport] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] transaction rolled back 2019-11-12 12:09:09,983Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] Lock freed to object 'EngineLock:{exclusiveLocks='[centos-testvm-a910=VM_NAME]', sharedLocks='[400688e8-3c5b-4cca-9ef8-bbb6c79d54ed=DISK, 819aecf6-c83d-4470-9915-e309390d8098=TEMPLATE]'}' 2019-11-12 12:09:10,001Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] EVENT_ID: USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM centos-testvm-a910 creation. 2019-11-12 12:09:10,002Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] Failed invoking callback end method 'onFailed' for command '97d4103b-acef-4b55-a379-71a1baa04a4f' with exception 'null', the callback is marked for end method retries 2019-11-12 12:09:12,019Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.AddVmCommand' with failure. 2019-11-12 12:09:12,023Z ERROR [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' with failure. 2019-11-12 12:09:12,041Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [1b861e85] Running command: RemoveImageCommand internal: true. Entities affected : ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: Storage 2019-11-12 12:09:12,063Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [1b861e85] START, DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'}), log id: 376f65dc 2019-11-12 12:09:12,090Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [1b861e85] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:12,090Z ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [1b861e85] Command 'DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'})' execution failed: IRSGenericException: IRSErrorException: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:12,090Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [1b861e85] FINISH, DeleteImageGroupVDSCommand, return: , log id: 376f65dc 2019-11-12 12:09:12,090Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [1b861e85] Disk '56ddac45-1913-4d24-af97-2f969fc3fa2e' doesn't exist on storage domain '78bfcb57-3a0d-4a71-a3f8-480ebae37c74', rolling forward 2019-11-12 12:09:12,101Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [1b861e85] Removed task 'ebe0e879-8595-44db-9d64-e237afd6c8e8' from DataBase 2019-11-12 12:09:12,157Z INFO [org.ovirt.engine.core.utils.transaction.TransactionSupport] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] transaction rolled back 2019-11-12 12:09:12,157Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Trying to release a shared lock for key: '400688e8-3c5b-4cca-9ef8-bbb6c79d54edDISK' , but lock does not exist 2019-11-12 12:09:12,157Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Trying to release a shared lock for key: '819aecf6-c83d-4470-9915-e309390d8098TEMPLATE' , but lock does not exist 2019-11-12 12:09:12,157Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Trying to release exclusive lock which does not exist, lock key: 'centos-testvm-a910VM_NAME' 2019-11-12 12:09:12,157Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Lock freed to object 'EngineLock:{exclusiveLocks='[centos-testvm-a910=VM_NAME]', sharedLocks='[400688e8-3c5b-4cca-9ef8-bbb6c79d54ed=DISK, 819aecf6-c83d-4470-9915-e309390d8098=TEMPLATE]'}' 2019-11-12 12:09:12,172Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] EVENT_ID: USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM centos-testvm-a910 creation. 2019-11-12 12:09:12,172Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Failed invoking callback end method 'onFailed' for command '97d4103b-acef-4b55-a379-71a1baa04a4f' with exception 'null', the callback is marked for end method retries 2019-11-12 12:09:16,192Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.AddVmCommand' with failure. 2019-11-12 12:09:16,195Z ERROR [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' with failure. 2019-11-12 12:09:16,215Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [8f3849f] Running command: RemoveImageCommand internal: true. Entities affected : ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: Storage 2019-11-12 12:09:16,240Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [8f3849f] START, DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'}), log id: 75027448 2019-11-12 12:09:16,263Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [8f3849f] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:16,263Z ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [8f3849f] Command 'DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'})' execution failed: IRSGenericException: IRSErrorException: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:16,263Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [8f3849f] FINISH, DeleteImageGroupVDSCommand, return: , log id: 75027448 2019-11-12 12:09:16,263Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [8f3849f] Disk '56ddac45-1913-4d24-af97-2f969fc3fa2e' doesn't exist on storage domain '78bfcb57-3a0d-4a71-a3f8-480ebae37c74', rolling forward 2019-11-12 12:09:16,274Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [8f3849f] Removed task '688274fc-0596-44b5-b167-36c86b8b8e5d' from DataBase 2019-11-12 12:09:16,341Z INFO [org.ovirt.engine.core.utils.transaction.TransactionSupport] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] transaction rolled back 2019-11-12 12:09:16,341Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] Trying to release a shared lock for key: '400688e8-3c5b-4cca-9ef8-bbb6c79d54edDISK' , but lock does not exist 2019-11-12 12:09:16,341Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] Trying to release a shared lock for key: '819aecf6-c83d-4470-9915-e309390d8098TEMPLATE' , but lock does not exist 2019-11-12 12:09:16,342Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] Trying to release exclusive lock which does not exist, lock key: 'centos-testvm-a910VM_NAME' 2019-11-12 12:09:16,342Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] Lock freed to object 'EngineLock:{exclusiveLocks='[centos-testvm-a910=VM_NAME]', sharedLocks='[400688e8-3c5b-4cca-9ef8-bbb6c79d54ed=DISK, 819aecf6-c83d-4470-9915-e309390d8098=TEMPLATE]'}' 2019-11-12 12:09:16,357Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] EVENT_ID: USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM centos-testvm-a910 creation. 2019-11-12 12:09:16,357Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] Failed invoking callback end method 'onFailed' for command '97d4103b-acef-4b55-a379-71a1baa04a4f' with exception 'null', the callback is marked for end method retries 2019-11-12 12:09:24,376Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.AddVmCommand' with failure. 2019-11-12 12:09:24,380Z ERROR [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' with failure. 2019-11-12 12:09:24,387Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [153e3c43] Running command: RemoveImageCommand internal: true. Entities affected : ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: Storage 2019-11-12 12:09:24,419Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [153e3c43] START, DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'}), log id: 29a560b1 2019-11-12 12:09:24,444Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [153e3c43] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:24,444Z ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [153e3c43] Command 'DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'})' execution failed: IRSGenericException: IRSErrorException: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:24,444Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [153e3c43] FINISH, DeleteImageGroupVDSCommand, return: , log id: 29a560b1 2019-11-12 12:09:24,445Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [153e3c43] Disk '56ddac45-1913-4d24-af97-2f969fc3fa2e' doesn't exist on storage domain '78bfcb57-3a0d-4a71-a3f8-480ebae37c74', rolling forward 2019-11-12 12:09:24,455Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [153e3c43] Removed task '13b2490d-09a6-4230-a5d3-7b86b536e8c3' from DataBase 2019-11-12 12:09:24,509Z INFO [org.ovirt.engine.core.utils.transaction.TransactionSupport] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [] transaction rolled back 2019-11-12 12:09:24,509Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [] Trying to release a shared lock for key: '400688e8-3c5b-4cca-9ef8-bbb6c79d54edDISK' , but lock does not exist 2019-11-12 12:09:24,509Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [] Trying to release a shared lock for key: '819aecf6-c83d-4470-9915-e309390d8098TEMPLATE' , but lock does not exist 2019-11-12 12:09:24,509Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [] Trying to release exclusive lock which does not exist, lock key: 'centos-testvm-a910VM_NAME' 2019-11-12 12:09:24,509Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [] Lock freed to object 'EngineLock:{exclusiveLocks='[centos-testvm-a910=VM_NAME]', sharedLocks='[400688e8-3c5b-4cca-9ef8-bbb6c79d54ed=DISK, 819aecf6-c83d-4470-9915-e309390d8098=TEMPLATE]'}' 2019-11-12 12:09:24,527Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [] EVENT_ID: USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM centos-testvm-a910 creation. 2019-11-12 12:09:24,527Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [] Failed invoking callback end method 'onFailed' for command '97d4103b-acef-4b55-a379-71a1baa04a4f' with exception 'null', the callback is marked for end method retries 2019-11-12 12:09:34,547Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.AddVmCommand' with failure. 2019-11-12 12:09:34,551Z ERROR [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' with failure. 2019-11-12 12:09:34,568Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [28afe05e] Running command: RemoveImageCommand internal: true. Entities affected : ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: Storage 2019-11-12 12:09:34,591Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [28afe05e] START, DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'}), log id: 207e5265 2019-11-12 12:09:34,617Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [28afe05e] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:34,617Z ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [28afe05e] Command 'DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'})' execution failed: IRSGenericException: IRSErrorException: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:34,618Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [28afe05e] FINISH, DeleteImageGroupVDSCommand, return: , log id: 207e5265 2019-11-12 12:09:34,618Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [28afe05e] Disk '56ddac45-1913-4d24-af97-2f969fc3fa2e' doesn't exist on storage domain '78bfcb57-3a0d-4a71-a3f8-480ebae37c74', rolling forward 2019-11-12 12:09:34,629Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [28afe05e] Removed task 'ad58e8d8-13cc-4ae4-8785-9df252b38c1f' from DataBase 2019-11-12 12:09:34,688Z INFO [org.ovirt.engine.core.utils.transaction.TransactionSupport] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] transaction rolled back 2019-11-12 12:09:34,688Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] Trying to release a shared lock for key: '400688e8-3c5b-4cca-9ef8-bbb6c79d54edDISK' , but lock does not exist 2019-11-12 12:09:34,688Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] Trying to release a shared lock for key: '819aecf6-c83d-4470-9915-e309390d8098TEMPLATE' , but lock does not exist 2019-11-12 12:09:34,688Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] Trying to release exclusive lock which does not exist, lock key: 'centos-testvm-a910VM_NAME' 2019-11-12 12:09:34,688Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] Lock freed to object 'EngineLock:{exclusiveLocks='[centos-testvm-a910=VM_NAME]', sharedLocks='[400688e8-3c5b-4cca-9ef8-bbb6c79d54ed=DISK, 819aecf6-c83d-4470-9915-e309390d8098=TEMPLATE]'}' 2019-11-12 12:09:34,707Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] EVENT_ID: USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM centos-testvm-a910 creation. 2019-11-12 12:09:34,707Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] Failed invoking callback end method 'onFailed' for command '97d4103b-acef-4b55-a379-71a1baa04a4f' with exception 'null', the callback is marked for end method retries 2019-11-12 12:09:42,871Z INFO [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-75) [58fc7cd2] Lock Acquired to object 'EngineLock:{exclusiveLocks='[02a18cd9-ead2-44c7-9923-8fe84d1865ee=PROVIDER]', sharedLocks=''}' 2019-11-12 12:09:42,880Z INFO [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-75) [58fc7cd2] Running command: SyncNetworkProviderCommand internal: true. 2019-11-12 12:09:42,975Z INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-49) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2019-11-12 12:09:43,096Z INFO [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-75) [58fc7cd2] Lock freed to object 'EngineLock:{exclusiveLocks='[02a18cd9-ead2-44c7-9923-8fe84d1865ee=PROVIDER]', sharedLocks=''}' 2019-11-12 12:09:44,729Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.AddVmCommand' with failure. 2019-11-12 12:09:44,732Z ERROR [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' with failure. 2019-11-12 12:09:44,757Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [14057067] Running command: RemoveImageCommand internal: true. Entities affected : ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: Storage 2019-11-12 12:09:44,780Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [14057067] START, DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'}), log id: aaea0bc 2019-11-12 12:09:44,804Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [14057067] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:44,804Z ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [14057067] Command 'DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'})' execution failed: IRSGenericException: IRSErrorException: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:44,804Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [14057067] FINISH, DeleteImageGroupVDSCommand, return: , log id: aaea0bc 2019-11-12 12:09:44,804Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [14057067] Disk '56ddac45-1913-4d24-af97-2f969fc3fa2e' doesn't exist on storage domain '78bfcb57-3a0d-4a71-a3f8-480ebae37c74', rolling forward 2019-11-12 12:09:44,815Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [14057067] Removed task 'c964f397-f054-4d81-98d6-052ce5a30168' from DataBase 2019-11-12 12:09:44,887Z INFO [org.ovirt.engine.core.utils.transaction.TransactionSupport] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [] transaction rolled back 2019-11-12 12:09:44,887Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [] Trying to release a shared lock for key: '400688e8-3c5b-4cca-9ef8-bbb6c79d54edDISK' , but lock does not exist 2019-11-12 12:09:44,887Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [] Trying to release a shared lock for key: '819aecf6-c83d-4470-9915-e309390d8098TEMPLATE' , but lock does not exist 2019-11-12 12:09:44,888Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [] Trying to release exclusive lock which does not exist, lock key: 'centos-testvm-a910VM_NAME' 2019-11-12 12:09:44,888Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [] Lock freed to object 'EngineLock:{exclusiveLocks='[centos-testvm-a910=VM_NAME]', sharedLocks='[400688e8-3c5b-4cca-9ef8-bbb6c79d54ed=DISK, 819aecf6-c83d-4470-9915-e309390d8098=TEMPLATE]'}' 2019-11-12 12:09:44,903Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [] EVENT_ID: USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM centos-testvm-a910 creation. 2019-11-12 12:09:44,924Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Failed invoking callback end method 'onFailed' for command '97d4103b-acef-4b55-a379-71a1baa04a4f' with exception 'null', the callback is marked for end method retries but max number of retries have been attempted. The command will be marked as Failed. 2019-11-12 12:09:44,925Z INFO [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Exception in invoking callback of command AddVm (97d4103b-acef-4b55-a379-71a1baa04a4f): NullPointerException: 2019-11-12 12:09:44,925Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Error invoking callback method 'onFailed' for 'FAILED' command '97d4103b-acef-4b55-a379-71a1baa04a4f' 2019-11-12 12:09:44,925Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Exception: javax.ejb.EJBTransactionRolledbackException at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:203) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:420) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:148) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) [weld-ejb-3.1.1.Final.jar:3.1.1.Final] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:618) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81) at org.ovirt.engine.core.bll.interfaces.BackendInternal$$$view2.endAction(Unknown Source) [bll.jar:] at sun.reflect.GeneratedMethodAccessor1071.invoke(Unknown Source) [:1.8.0_222] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_222] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_222] at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:410) [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] at org.jboss.weld.module.ejb.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:134) [weld-ejb-3.1.1.Final.jar:3.1.1.Final] at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] at org.jboss.weld.module.ejb.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:68) [weld-ejb-3.1.1.Final.jar:3.1.1.Final] at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106) [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] at org.ovirt.engine.core.bll.BackendCommandObjectsHandler$BackendInternal$BackendLocal$2049259618$Proxy$_$$_Weld$EnterpriseProxy$.endAction(Unknown Source) [bll.jar:] at org.ovirt.engine.core.bll.VmCommand.endActionOnDisks(VmCommand.java:266) [bll.jar:] at org.ovirt.engine.core.bll.AddVmCommand.endWithFailure(AddVmCommand.java:1452) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.internalEndWithFailure(CommandBase.java:736) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.endActionInTransactionScope(CommandBase.java:658) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2003) [bll.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInNewTransaction(TransactionSupport.java:202) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInRequired(TransactionSupport.java:137) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:105) [utils.jar:] at org.ovirt.engine.core.bll.CommandBase.endAction(CommandBase.java:520) [bll.jar:] at org.ovirt.engine.core.bll.ChildCommandsCallbackBase.endAction(ChildCommandsCallbackBase.java:134) [bll.jar:] at org.ovirt.engine.core.bll.ChildCommandsCallbackBase.onFailed(ChildCommandsCallbackBase.java:174) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.endCallback(CommandCallbacksPoller.java:67) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:166) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:109) [bll.jar:] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_222] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [rt.jar:1.8.0_222] at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383) [javax.enterprise.concurrent-1.0.jar:] at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534) [javax.enterprise.concurrent-1.0.jar:] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_222] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_222] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_222] at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) [javax.enterprise.concurrent-1.0.jar:] Caused by: java.lang.NullPointerException Please take a look. ----- kind regards/met vrindelijke groet Marko Vrgotic ActiveVideo On 10/10/2019, 14:23, "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> wrote: Hi, I could not check as in the meantime I destroyed my staging setup. Re-provisioning it now and will retest with ansible. On 10/10/2019, 10:51, "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>> wrote: Hi Ondra, That is true, But why does it work from Portal? Image ID is not differ when run when ansible against same template? I will check anyway. On 10/10/2019, 09:47, "Ondra Machacek" <omachace(a)redhat.com<mailto:omachace@redhat.com>> wrote: The error message is: Image does not exist in domain: u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' Can you please check if the image with id 'd680a46a-7188-45f6-b6a7-3333f830c0b4' exists on storage domain with id '935de3ac-a735-4fc8-9161-26bfd751ffc7'? On 08/10/2019 13:05, Vrgotic, Marko wrote: > Dear oVirt, > > Just recently, I have upgraded oVirt staging environment from 4.3.4 to > 4.3.6 release. > > Since then I noticed the issue when creating VMs from template, using > Ansible. When creating VM from template using UI, all works well. > > Tests were executed with same user, with SuperUser priviledges. > > pip freeze > > *ansible==2.7.13* > > asn1crypto==1.0.0 > > bcrypt==3.1.7 > > cffi==1.12.3 > > cryptography==2.7 > > dnspython==1.16.0 > > ipaddress==1.0.22 > > Jinja2==2.10.1 > > lxml==4.4.1 > > MarkupSafe==1.1.1 > > netaddr==0.7.19 > > *ovirt-engine-sdk-python==4.3.3* > > paramiko==2.6.0 > > pycparser==2.19 > > pycurl==7.43.0.3 > > PyNaCl==1.3.0 > > PyYAML==5.1.2 > > six==1.12.0 > > *Logs from engine: * > > 2019-10-08 09:57:42,294Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (default task-23) [067ec489-ae6c-4871-8ab6-8296016ca1ce] Lock Acquired > to object 'EngineLock:{exclusiveLocks='[centos-testvm-024=VM_NAME]', > sharedLocks='[9ac6f4ad-58d0-4a7e-b424-91f2d76abcac=TEMPLATE, > a7e42574-be60-4c94-94a5-cc4b30fdb16f=DISK]'}' > > 2019-10-08 09:57:42,299Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43687) [390b4c75] FINISH, > HSMClearTaskVDSCommand, return: , log id: be932a0 > > 2019-10-08 09:57:42,299Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43687) [390b4c75] FINISH, > SPMClearTaskVDSCommand, return: , log id: 3e25883 > > 2019-10-08 09:57:42,303Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43687) [390b4c75] > BaseAsyncTask::removeTaskFromDB: Removed task > '7e1d68a2-bb49-4456-b228-db851fe6603c' from DataBase > > 2019-10-08 09:57:42,303Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43687) [390b4c75] > CommandAsyncTask::HandleEndActionResult [within thread]: Removing > CommandMultiAsyncTasks object for entity > '4f8a6897-66e8-453b-b706-246cb8505b3e' > > 2019-10-08 09:57:42,375Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (default task-23) [067ec489-ae6c-4871-8ab6-8296016ca1ce] Running > command: AddVmCommand internal: false. Entities affected : ID: > 2e428504-c339-11e9-87ef-00163e3ec101 Type: ClusterAction group CREATE_VM > with role type USER, ID: 9ac6f4ad-58d0-4a7e-b424-91f2d76abcac Type: > VmTemplateAction group CREATE_VM with role type USER, ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: StorageAction group > CREATE_DISK with role type USER > > 2019-10-08 09:57:42,488Z INFO > [org.ovirt.engine.core.bll.AddRngDeviceCommand] (default task-23) > [332c57d4] Running command: AddRngDeviceCommand internal: true. Entities > affected : ID: d5719cf0-2a64-4a28-bbf2-edc1bb05b777 Type: VMAction > group EDIT_VM_PROPERTIES with role type USER > > 2019-10-08 09:57:42,498Z INFO > [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default > task-23) [332c57d4] START, SetVmStatusVDSCommand( > SetVmStatusVDSCommandParameters:{vmId='d5719cf0-2a64-4a28-bbf2-edc1bb05b777', > status='ImageLocked', exitStatus='Normal'}), log id: 2fe004e2 > > 2019-10-08 09:57:42,507Z INFO > [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default > task-23) [332c57d4] FINISH, SetVmStatusVDSCommand, return: , log id: > 2fe004e2 > > 2019-10-08 09:57:42,528Z INFO > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (default task-23) [067ec489-ae6c-4871-8ab6-8296016ca1ce] Running > command: CreateSnapshotFromTemplateCommand internal: true. Entities > affected : ID: 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:57:42,554Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] > (default task-23) [067ec489-ae6c-4871-8ab6-8296016ca1ce] START, > CreateVolumeVDSCommand( > CreateVolumeVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', > imageSizeInBytes='8589934592', volumeFormat='COW', > newImageId='9a96018c-ce7d-4c77-a91a-30fc16c7b2ba', imageType='Sparse', > newImageDescription='', imageInitialSizeInBytes='0', > imageId='f9e0c4d9-81dd-4e44-8a71-33e55d4399c6', > sourceImageGroupId='a7e42574-be60-4c94-94a5-cc4b30fdb16f'}), log id: > 37b29c7d > > 2019-10-08 09:57:42,639Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] > (default task-23) [067ec489-ae6c-4871-8ab6-8296016ca1ce] FINISH, > CreateVolumeVDSCommand, return: 9a96018c-ce7d-4c77-a91a-30fc16c7b2ba, > log id: 37b29c7d > > 2019-10-08 09:57:42,645Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (default task-23) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] CommandAsyncTask::Adding > CommandMultiAsyncTasks object for command > 'f1665b66-2032-4a60-944e-c04beace088e' > > 2019-10-08 09:57:42,645Z INFO > [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (default task-23) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] > CommandMultiAsyncTasks::attachTask: Attaching task > '99abc310-b44b-435c-8d43-922b782a69dc' to command > 'f1665b66-2032-4a60-944e-c04beace088e'. > > 2019-10-08 09:57:42,660Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (default task-23) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Adding task > '99abc310-b44b-435c-8d43-922b782a69dc' (Parent Command > 'CreateSnapshotFromTemplate', Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling > hasn't started yet.. > > 2019-10-08 09:57:42,934Z INFO > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (default task-23) [067ec489-ae6c-4871-8ab6-8296016ca1ce] EVENT_ID: > USER_ADD_VM_STARTED(37), VM centos-testvm-024 creation was initiated by > mteam@internal-authz. > > 2019-10-08 09:57:42,935Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (default task-23) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] BaseAsyncTask::startPollingTask: > Starting to poll task '99abc310-b44b-435c-8d43-922b782a69dc'. > > 2019-10-08 09:57:44,384Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-74) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Command 'AddVm' (id: > '1b65f576-365d-4e8b-a920-621516cbdaed') waiting on child command id: > 'f1665b66-2032-4a60-944e-c04beace088e' type:'CreateSnapshotFromTemplate' > to complete > > 2019-10-08 09:57:48,393Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Command 'AddVm' (id: > '1b65f576-365d-4e8b-a920-621516cbdaed') waiting on child command id: > 'f1665b66-2032-4a60-944e-c04beace088e' type:'CreateSnapshotFromTemplate' > to complete > > 2019-10-08 09:57:48,394Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) [5830ba58] Command > 'AddDisk' id: '937776b8-b94d-4178-b9c2-e39fe42cb06c' child commands > '[63409b0b-749a-45d5-85a5-baf55d5fa2a4]' executions were completed, > status 'SUCCEEDED' > > 2019-10-08 09:57:48,394Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) [5830ba58] Command > 'AddDisk' id: '937776b8-b94d-4178-b9c2-e39fe42cb06c' Updating status to > 'SUCCEEDED', The command end method logic will be executed by one of its > parent commands. > > 2019-10-08 09:57:48,398Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) [5830ba58] Command > 'AddDisk' id: 'fdc5571e-a925-4400-a54a-a1ef1dcd23ae' child commands > '[54d68cae-6585-4351-aaf7-fe687905acf4]' executions were completed, > status 'SUCCEEDED' > > 2019-10-08 09:57:48,398Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) [5830ba58] Command > 'AddDisk' id: 'fdc5571e-a925-4400-a54a-a1ef1dcd23ae' Updating status to > 'SUCCEEDED', The command end method logic will be executed by one of its > parent commands. > > 2019-10-08 09:57:48,401Z INFO > [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) [5830ba58] Command > 'ProcessOvfUpdateForStorageDomain' (id: > 'bdcdae3a-00f6-4176-9d27-0bb0f04912a3') waiting on child command id: > 'b4050edd-62a7-4b83-a4ab-a21c83bf3ade' > type:'CreateOvfVolumeForStorageDomain' to complete > > 2019-10-08 09:57:48,402Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) [5830ba58] Command > 'CreateOvfVolumeForStorageDomain' id: > 'b4050edd-62a7-4b83-a4ab-a21c83bf3ade' child commands > '[937776b8-b94d-4178-b9c2-e39fe42cb06c]' executions were completed, > status 'SUCCEEDED' > > 2019-10-08 09:57:48,404Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) [5830ba58] Command > 'CreateOvfVolumeForStorageDomain' id: > '5fd47910-95b2-4387-8e26-ea2c80b078a0' child commands > '[fdc5571e-a925-4400-a54a-a1ef1dcd23ae]' executions were completed, > status 'SUCCEEDED' > > 2019-10-08 09:57:49,416Z INFO > [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [390b4c75] Command > 'ProcessOvfUpdateForStorageDomain' id: > '849bd16c-00d2-48a2-8fde-631af0dfe1b5' child commands > '[a80a3657-c813-42c1-a43d-27442b5dc238, > 4f8a6897-66e8-453b-b706-246cb8505b3e]' executions were completed, status > 'SUCCEEDED' > > 2019-10-08 09:57:49,418Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.CreateOvfVolumeForStorageDomainCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] Ending > command > 'org.ovirt.engine.core.bll.storage.ovfstore.CreateOvfVolumeForStorageDomainCommand' > successfully. > > 2019-10-08 09:57:49,420Z INFO > [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] Ending > command 'org.ovirt.engine.core.bll.storage.disk.AddDiskCommand' > successfully. > > 2019-10-08 09:57:49,426Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-3) > [5830ba58] Ending command > 'org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand' successfully. > > 2019-10-08 09:57:49,427Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] START, > GetImageInfoVDSCommand( > GetImageInfoVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='66984468-bbfa-4941-8c6b-df72a6d920f2', > imageId='7db55211-041a-40c8-85a6-a2ff1bd182ce'}), log id: 6c02a73c > > 2019-10-08 09:57:49,429Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] START, > GetVolumeInfoVDSCommand(HostName = ovirt-staging-hv-01.avinity.tv<http://ovirt-staging-hv-01.avinity.tv>, > GetVolumeInfoVDSCommandParameters:{hostId='bfc4c379-bd5f-45be-98a4-f0469dc3817c', > storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='66984468-bbfa-4941-8c6b-df72a6d920f2', > imageId='7db55211-041a-40c8-85a6-a2ff1bd182ce'}), log id: 2e131d9d > > 2019-10-08 09:57:49,456Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] FINISH, > GetVolumeInfoVDSCommand, return: > org.ovirt.engine.core.common.businessentities.storage.DiskImage@26992dd0, log > id: 2e131d9d > > 2019-10-08 09:57:49,456Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] FINISH, > GetImageInfoVDSCommand, return: > org.ovirt.engine.core.common.businessentities.storage.DiskImage@26992dd0, log > id: 6c02a73c > > 2019-10-08 09:57:49,464Z WARN > [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [] VM is null - no > unlocking > > 2019-10-08 09:57:49,481Z INFO > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [] EVENT_ID: > USER_ADD_DISK_FINISHED_SUCCESS(2,021), The disk 'OVF_STORE' was > successfully added. > > 2019-10-08 09:57:49,490Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.CreateOvfVolumeForStorageDomainCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] Ending > command > 'org.ovirt.engine.core.bll.storage.ovfstore.CreateOvfVolumeForStorageDomainCommand' > successfully. > > 2019-10-08 09:57:49,491Z INFO > [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] Ending > command 'org.ovirt.engine.core.bll.storage.disk.AddDiskCommand' > successfully. > > 2019-10-08 09:57:49,495Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-3) > [5830ba58] Ending command > 'org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand' successfully. > > 2019-10-08 09:57:49,497Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] START, > GetImageInfoVDSCommand( > GetImageInfoVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='ee208fd3-e05c-4ba8-aba9-fa521d69a870', > imageId='484c1eed-b03a-4fa0-a12d-0087294dec86'}), log id: 7a3dad31 > > 2019-10-08 09:57:49,498Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] START, > GetVolumeInfoVDSCommand(HostName = ovirt-staging-hv-01.avinity.tv<http://ovirt-staging-hv-01.avinity.tv>, > GetVolumeInfoVDSCommandParameters:{hostId='bfc4c379-bd5f-45be-98a4-f0469dc3817c', > storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='ee208fd3-e05c-4ba8-aba9-fa521d69a870', > imageId='484c1eed-b03a-4fa0-a12d-0087294dec86'}), log id: 5b85c4a5 > > 2019-10-08 09:57:49,522Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] FINISH, > GetVolumeInfoVDSCommand, return: > org.ovirt.engine.core.common.businessentities.storage.DiskImage@13555e4, > log id: 5b85c4a5 > > 2019-10-08 09:57:49,522Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] FINISH, > GetImageInfoVDSCommand, return: > org.ovirt.engine.core.common.businessentities.storage.DiskImage@13555e4, > log id: 7a3dad31 > > 2019-10-08 09:57:49,529Z WARN > [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [] VM is null - no > unlocking > > 2019-10-08 09:57:49,540Z INFO > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [] EVENT_ID: > USER_ADD_DISK_FINISHED_SUCCESS(2,021), The disk 'OVF_STORE' was > successfully added. > > 2019-10-08 09:57:50,552Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [390b4c75] Ending > command > 'org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand' > successfully. > > 2019-10-08 09:57:50,575Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] START, > SetVolumeDescriptionVDSCommand( > SetVolumeDescriptionVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='ee208fd3-e05c-4ba8-aba9-fa521d69a870', > imageId='484c1eed-b03a-4fa0-a12d-0087294dec86'}), log id: 7e77a9a8 > > 2019-10-08 09:57:50,576Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] -- > executeIrsBrokerCommand: calling 'setVolumeDescription', parameters: > > 2019-10-08 09:57:50,576Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > spUUID=2e3b3484-c339-11e9-8d02-00163e3ec101 > > 2019-10-08 09:57:50,576Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > sdUUID=935de3ac-a735-4fc8-9161-26bfd751ffc7 > > 2019-10-08 09:57:50,576Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > imageGroupGUID=ee208fd3-e05c-4ba8-aba9-fa521d69a870 > > 2019-10-08 09:57:50,576Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > volUUID=484c1eed-b03a-4fa0-a12d-0087294dec86 > > 2019-10-08 09:57:50,576Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > description={"Updated":false,"Last Updated":null,"Storage > Domains":[{"uuid":"935de3ac-a735-4fc8-9161-26bfd751ffc7"}],"Disk > Description":"OVF_STORE"} > > 2019-10-08 09:57:50,606Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] FINISH, > SetVolumeDescriptionVDSCommand, return: , log id: 7e77a9a8 > > 2019-10-08 09:57:50,614Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Lock > Acquired to object 'EngineLock:{exclusiveLocks='', > sharedLocks='[bfc4c379-bd5f-45be-98a4-f0469dc3817c=VDS_EXECUTION]'}' > > 2019-10-08 09:57:50,623Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Running > command: UploadStreamCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:57:50,624Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] START, > UploadStreamVDSCommand(HostName = ovirt-staging-hv-01.avinity.tv<http://ovirt-staging-hv-01.avinity.tv>, > UploadStreamVDSCommandParameters:{hostId='bfc4c379-bd5f-45be-98a4-f0469dc3817c'}), > log id: 531a4a4a > > 2019-10-08 09:57:50,625Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] -- > executeVdsBrokerCommand, parameters: > > 2019-10-08 09:57:50,625Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > spUUID=2e3b3484-c339-11e9-8d02-00163e3ec101 > > 2019-10-08 09:57:50,625Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > sdUUID=935de3ac-a735-4fc8-9161-26bfd751ffc7 > > 2019-10-08 09:57:50,625Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > imageGUID=ee208fd3-e05c-4ba8-aba9-fa521d69a870 > > 2019-10-08 09:57:50,625Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > volUUID=484c1eed-b03a-4fa0-a12d-0087294dec86 > > 2019-10-08 09:57:50,625Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ size=30720 > > 2019-10-08 09:57:51,331Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] FINISH, > UploadStreamVDSCommand, return: , log id: 531a4a4a > > 2019-10-08 09:57:51,342Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] > CommandAsyncTask::Adding CommandMultiAsyncTasks object for command > 'c11f4d3c-f85b-43c5-986f-a517aed66d7e' > > 2019-10-08 09:57:51,342Z INFO > [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] > CommandMultiAsyncTasks::attachTask: Attaching task > 'e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d' to command > 'c11f4d3c-f85b-43c5-986f-a517aed66d7e'. > > 2019-10-08 09:57:51,351Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Adding > task 'e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d' (Parent Command > 'UploadStream', Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling > hasn't started yet.. > > 2019-10-08 09:57:51,355Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] > BaseAsyncTask::startPollingTask: Starting to poll task > 'e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d'. > > 2019-10-08 09:57:51,358Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Lock freed > to object 'EngineLock:{exclusiveLocks='', > sharedLocks='[bfc4c379-bd5f-45be-98a4-f0469dc3817c=VDS_EXECUTION]'}' > > 2019-10-08 09:57:51,360Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] START, > SetVolumeDescriptionVDSCommand( > SetVolumeDescriptionVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='ee208fd3-e05c-4ba8-aba9-fa521d69a870', > imageId='484c1eed-b03a-4fa0-a12d-0087294dec86'}), log id: 238169f6 > > 2019-10-08 09:57:51,360Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] -- > executeIrsBrokerCommand: calling 'setVolumeDescription', parameters: > > 2019-10-08 09:57:51,360Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > spUUID=2e3b3484-c339-11e9-8d02-00163e3ec101 > > 2019-10-08 09:57:51,360Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > sdUUID=935de3ac-a735-4fc8-9161-26bfd751ffc7 > > 2019-10-08 09:57:51,360Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > imageGroupGUID=ee208fd3-e05c-4ba8-aba9-fa521d69a870 > > 2019-10-08 09:57:51,360Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > volUUID=484c1eed-b03a-4fa0-a12d-0087294dec86 > > 2019-10-08 09:57:51,360Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > description={"Updated":true,"Size":30720,"Last Updated":"Tue Oct 08 > 09:57:50 UTC 2019","Storage > Domains":[{"uuid":"935de3ac-a735-4fc8-9161-26bfd751ffc7"}],"Disk > Description":"OVF_STORE"} > > 2019-10-08 09:57:51,389Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] FINISH, > SetVolumeDescriptionVDSCommand, return: , log id: 238169f6 > > 2019-10-08 09:57:51,596Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] START, > SetVolumeDescriptionVDSCommand( > SetVolumeDescriptionVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='66984468-bbfa-4941-8c6b-df72a6d920f2', > imageId='7db55211-041a-40c8-85a6-a2ff1bd182ce'}), log id: 59bde70f > > 2019-10-08 09:57:51,627Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] -- > executeIrsBrokerCommand: calling 'setVolumeDescription', parameters: > > 2019-10-08 09:57:51,627Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > spUUID=2e3b3484-c339-11e9-8d02-00163e3ec101 > > 2019-10-08 09:57:51,627Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > sdUUID=935de3ac-a735-4fc8-9161-26bfd751ffc7 > > 2019-10-08 09:57:51,627Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > imageGroupGUID=66984468-bbfa-4941-8c6b-df72a6d920f2 > > 2019-10-08 09:57:51,627Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > volUUID=7db55211-041a-40c8-85a6-a2ff1bd182ce > > 2019-10-08 09:57:51,627Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > description={"Updated":false,"Last Updated":null,"Storage > Domains":[{"uuid":"935de3ac-a735-4fc8-9161-26bfd751ffc7"}],"Disk > Description":"OVF_STORE"} > > 2019-10-08 09:57:51,664Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] FINISH, > SetVolumeDescriptionVDSCommand, return: , log id: 59bde70f > > 2019-10-08 09:57:51,672Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Lock > Acquired to object 'EngineLock:{exclusiveLocks='', > sharedLocks='[bfc4c379-bd5f-45be-98a4-f0469dc3817c=VDS_EXECUTION]'}' > > 2019-10-08 09:57:51,683Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Running > command: UploadStreamCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:57:51,684Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] START, > UploadStreamVDSCommand(HostName = ovirt-staging-hv-01.avinity.tv<http://ovirt-staging-hv-01.avinity.tv>, > UploadStreamVDSCommandParameters:{hostId='bfc4c379-bd5f-45be-98a4-f0469dc3817c'}), > log id: 1cb812b6 > > 2019-10-08 09:57:51,684Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] -- > executeVdsBrokerCommand, parameters: > > 2019-10-08 09:57:51,684Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > spUUID=2e3b3484-c339-11e9-8d02-00163e3ec101 > > 2019-10-08 09:57:51,684Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > sdUUID=935de3ac-a735-4fc8-9161-26bfd751ffc7 > > 2019-10-08 09:57:51,684Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > imageGUID=66984468-bbfa-4941-8c6b-df72a6d920f2 > > 2019-10-08 09:57:51,684Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > volUUID=7db55211-041a-40c8-85a6-a2ff1bd182ce > > 2019-10-08 09:57:51,684Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ size=30720 > > 2019-10-08 09:57:51,933Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] FINISH, > UploadStreamVDSCommand, return: , log id: 1cb812b6 > > 2019-10-08 09:57:51,943Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] > CommandAsyncTask::Adding CommandMultiAsyncTasks object for command > 'd0c07988-0e43-4e6d-b86c-e736b28d4537' > > 2019-10-08 09:57:51,943Z INFO > [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] > CommandMultiAsyncTasks::attachTask: Attaching task > 'ba88edd0-8188-472e-8f59-aa3f90e63181' to command > 'd0c07988-0e43-4e6d-b86c-e736b28d4537'. > > 2019-10-08 09:57:51,952Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Adding > task 'ba88edd0-8188-472e-8f59-aa3f90e63181' (Parent Command > 'UploadStream', Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling > hasn't started yet.. > > 2019-10-08 09:57:51,958Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] > BaseAsyncTask::startPollingTask: Starting to poll task > 'ba88edd0-8188-472e-8f59-aa3f90e63181'. > > 2019-10-08 09:57:51,961Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Lock freed > to object 'EngineLock:{exclusiveLocks='', > sharedLocks='[bfc4c379-bd5f-45be-98a4-f0469dc3817c=VDS_EXECUTION]'}' > > 2019-10-08 09:57:51,962Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] START, > SetVolumeDescriptionVDSCommand( > SetVolumeDescriptionVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='66984468-bbfa-4941-8c6b-df72a6d920f2', > imageId='7db55211-041a-40c8-85a6-a2ff1bd182ce'}), log id: 213b3075 > > 2019-10-08 09:57:51,962Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] -- > executeIrsBrokerCommand: calling 'setVolumeDescription', parameters: > > 2019-10-08 09:57:51,962Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > spUUID=2e3b3484-c339-11e9-8d02-00163e3ec101 > > 2019-10-08 09:57:51,962Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > sdUUID=935de3ac-a735-4fc8-9161-26bfd751ffc7 > > 2019-10-08 09:57:51,962Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > imageGroupGUID=66984468-bbfa-4941-8c6b-df72a6d920f2 > > 2019-10-08 09:57:51,962Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > volUUID=7db55211-041a-40c8-85a6-a2ff1bd182ce > > 2019-10-08 09:57:51,962Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > description={"Updated":true,"Size":30720,"Last Updated":"Tue Oct 08 > 09:57:50 UTC 2019","Storage > Domains":[{"uuid":"935de3ac-a735-4fc8-9161-26bfd751ffc7"}],"Disk > Description":"OVF_STORE"} > > 2019-10-08 09:57:52,028Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] FINISH, > SetVolumeDescriptionVDSCommand, return: , log id: 213b3075 > > 2019-10-08 09:57:52,224Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] Polling and > updating Async Tasks: 7 tasks, 3 tasks to poll now > > 2019-10-08 09:57:52,228Z ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksStatusesVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] Failed in > 'HSMGetAllTasksStatusesVDS' method > > 2019-10-08 09:57:52,235Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] EVENT_ID: > VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt-staging-hv-01.avinity.tv<http://ovirt-staging-hv-01.avinity.tv> > command HSMGetAllTasksStatusesVDS failed: Invalid parameter: 'size=16777216' > > 2019-10-08 09:57:52,235Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > SPMAsyncTask::PollTask: Polling task > '99abc310-b44b-435c-8d43-922b782a69dc' (Parent Command > 'CreateSnapshotFromTemplate', Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned > status 'finished', result 'cleanSuccess'. > > 2019-10-08 09:57:52,240Z ERROR > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > BaseAsyncTask::logEndTaskFailure: Task > '99abc310-b44b-435c-8d43-922b782a69dc' (Parent Command > 'CreateSnapshotFromTemplate', Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended > with failure: > > -- Result: 'cleanSuccess' > > -- Message: 'VDSGenericException: VDSErrorException: Failed to > HSMGetAllTasksStatusesVDS, error = Invalid parameter: 'size=16777216', > code = 100', > > -- Exception: 'VDSGenericException: VDSErrorException: Failed to > HSMGetAllTasksStatusesVDS, error = Invalid parameter: 'size=16777216', > code = 100' > > 2019-10-08 09:57:52,241Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > CommandAsyncTask::endActionIfNecessary: All tasks of command > 'f1665b66-2032-4a60-944e-c04beace088e' has ended -> executing 'endAction' > > 2019-10-08 09:57:52,241Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: > 'f1665b66-2032-4a60-944e-c04beace088e'): calling endAction '. > > 2019-10-08 09:57:52,241Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > SPMAsyncTask::PollTask: Polling task > 'e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d' (Parent Command 'UploadStream', > Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned > status 'finished', result 'success'. > > 2019-10-08 09:57:52,241Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > BaseAsyncTask::onTaskEndSuccess: Task > 'e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d' (Parent Command 'UploadStream', > Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended > successfully. > > 2019-10-08 09:57:52,241Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43693) [] > CommandAsyncTask::endCommandAction [within thread] context: Attempting > to endAction 'CreateSnapshotFromTemplate', > > 2019-10-08 09:57:52,242Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > CommandAsyncTask::endActionIfNecessary: All tasks of command > 'c11f4d3c-f85b-43c5-986f-a517aed66d7e' has ended -> executing 'endAction' > > 2019-10-08 09:57:52,243Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: > 'c11f4d3c-f85b-43c5-986f-a517aed66d7e'): calling endAction '. > > 2019-10-08 09:57:52,243Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > SPMAsyncTask::PollTask: Polling task > 'ba88edd0-8188-472e-8f59-aa3f90e63181' (Parent Command 'UploadStream', > Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned > status 'finished', result 'success'. > > 2019-10-08 09:57:52,243Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > BaseAsyncTask::onTaskEndSuccess: Task > 'ba88edd0-8188-472e-8f59-aa3f90e63181' (Parent Command 'UploadStream', > Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended > successfully. > > 2019-10-08 09:57:52,243Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43694) [] > CommandAsyncTask::endCommandAction [within thread] context: Attempting > to endAction 'UploadStream', > > 2019-10-08 09:57:52,244Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > CommandAsyncTask::endActionIfNecessary: All tasks of command > 'd0c07988-0e43-4e6d-b86c-e736b28d4537' has ended -> executing 'endAction' > > 2019-10-08 09:57:52,244Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: > 'd0c07988-0e43-4e6d-b86c-e736b28d4537'): calling endAction '. > > 2019-10-08 09:57:52,245Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43695) [] > CommandAsyncTask::endCommandAction [within thread] context: Attempting > to endAction 'UploadStream', > > 2019-10-08 09:57:52,245Z INFO > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Command > [id=f1665b66-2032-4a60-944e-c04beace088e]: Updating status to 'FAILED', > The command end method logic will be executed by one of its parent commands. > > 2019-10-08 09:57:52,247Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] > CommandAsyncTask::HandleEndActionResult [within thread]: endAction for > action type 'CreateSnapshotFromTemplate' completed, handling the result. > > 2019-10-08 09:57:52,247Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] > CommandAsyncTask::HandleEndActionResult [within thread]: endAction for > action type 'CreateSnapshotFromTemplate' succeeded, clearing tasks. > > 2019-10-08 09:57:52,247Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] SPMAsyncTask::ClearAsyncTask: > Attempting to clear task '99abc310-b44b-435c-8d43-922b782a69dc' > > 2019-10-08 09:57:52,247Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] Ending command > 'org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand' > successfully. > > 2019-10-08 09:57:52,247Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] Ending command > 'org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand' > successfully. > > 2019-10-08 09:57:52,247Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] START, SPMClearTaskVDSCommand( > SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > taskId='99abc310-b44b-435c-8d43-922b782a69dc'}), log id: 66a4e67 > > 2019-10-08 09:57:52,247Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] START, > HSMClearTaskVDSCommand(HostName = ovirt-staging-hv-01.avinity.tv<http://ovirt-staging-hv-01.avinity.tv>, > HSMTaskGuidBaseVDSCommandParameters:{hostId='bfc4c379-bd5f-45be-98a4-f0469dc3817c', > taskId='99abc310-b44b-435c-8d43-922b782a69dc'}), log id: 7ec6d8b8 > > 2019-10-08 09:57:52,249Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] > CommandAsyncTask::HandleEndActionResult [within thread]: endAction for > action type 'UploadStream' completed, handling the result. > > 2019-10-08 09:57:52,249Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] > CommandAsyncTask::HandleEndActionResult [within thread]: endAction for > action type 'UploadStream' succeeded, clearing tasks. > > 2019-10-08 09:57:52,249Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] > SPMAsyncTask::ClearAsyncTask: Attempting to clear task > 'e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d' > > 2019-10-08 09:57:52,249Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] START, > SPMClearTaskVDSCommand( > SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > taskId='e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d'}), log id: 356927d > > 2019-10-08 09:57:52,250Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] > CommandAsyncTask::HandleEndActionResult [within thread]: endAction for > action type 'UploadStream' completed, handling the result. > > 2019-10-08 09:57:52,250Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] > CommandAsyncTask::HandleEndActionResult [within thread]: endAction for > action type 'UploadStream' succeeded, clearing tasks. > > 2019-10-08 09:57:52,250Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] > SPMAsyncTask::ClearAsyncTask: Attempting to clear task > 'ba88edd0-8188-472e-8f59-aa3f90e63181' > > 2019-10-08 09:57:52,251Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] START, > SPMClearTaskVDSCommand( > SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > taskId='ba88edd0-8188-472e-8f59-aa3f90e63181'}), log id: 75844e34 > > 2019-10-08 09:57:52,259Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] FINISH, HSMClearTaskVDSCommand, > return: , log id: 7ec6d8b8 > > 2019-10-08 09:57:52,259Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] FINISH, SPMClearTaskVDSCommand, > return: , log id: 66a4e67 > > 2019-10-08 09:57:52,260Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] START, > HSMClearTaskVDSCommand(HostName = ovirt-staging-hv-01.avinity.tv<http://ovirt-staging-hv-01.avinity.tv>, > HSMTaskGuidBaseVDSCommandParameters:{hostId='bfc4c379-bd5f-45be-98a4-f0469dc3817c', > taskId='e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d'}), log id: 3b239769 > > 2019-10-08 09:57:52,263Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] BaseAsyncTask::removeTaskFromDB: > Removed task '99abc310-b44b-435c-8d43-922b782a69dc' from DataBase > > 2019-10-08 09:57:52,263Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] > CommandAsyncTask::HandleEndActionResult [within thread]: Removing > CommandMultiAsyncTasks object for entity > 'f1665b66-2032-4a60-944e-c04beace088e' > > 2019-10-08 09:57:52,297Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] FINISH, > HSMClearTaskVDSCommand, return: , log id: 3b239769 > > 2019-10-08 09:57:52,297Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] FINISH, > SPMClearTaskVDSCommand, return: , log id: 356927d > > 2019-10-08 09:57:52,298Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] START, > HSMClearTaskVDSCommand(HostName = ovirt-staging-hv-01.avinity.tv<http://ovirt-staging-hv-01.avinity.tv>, > HSMTaskGuidBaseVDSCommandParameters:{hostId='bfc4c379-bd5f-45be-98a4-f0469dc3817c', > taskId='ba88edd0-8188-472e-8f59-aa3f90e63181'}), log id: 32d44e1 > > 2019-10-08 09:57:52,301Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] > BaseAsyncTask::removeTaskFromDB: Removed task > 'e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d' from DataBase > > 2019-10-08 09:57:52,301Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] > CommandAsyncTask::HandleEndActionResult [within thread]: Removing > CommandMultiAsyncTasks object for entity > 'c11f4d3c-f85b-43c5-986f-a517aed66d7e' > > 2019-10-08 09:57:52,314Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] FINISH, > HSMClearTaskVDSCommand, return: , log id: 32d44e1 > > 2019-10-08 09:57:52,314Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] FINISH, > SPMClearTaskVDSCommand, return: , log id: 75844e34 > > 2019-10-08 09:57:52,317Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] > BaseAsyncTask::removeTaskFromDB: Removed task > 'ba88edd0-8188-472e-8f59-aa3f90e63181' from DataBase > > 2019-10-08 09:57:52,317Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] > CommandAsyncTask::HandleEndActionResult [within thread]: Removing > CommandMultiAsyncTasks object for entity > 'd0c07988-0e43-4e6d-b86c-e736b28d4537' > > 2019-10-08 09:57:54,039Z INFO > [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-44) [5830ba58] Command > 'ProcessOvfUpdateForStorageDomain' id: > 'bdcdae3a-00f6-4176-9d27-0bb0f04912a3' child commands > '[b4050edd-62a7-4b83-a4ab-a21c83bf3ade, > 5fd47910-95b2-4387-8e26-ea2c80b078a0, > c11f4d3c-f85b-43c5-986f-a517aed66d7e, > d0c07988-0e43-4e6d-b86c-e736b28d4537]' executions were completed, status > 'SUCCEEDED' > > 2019-10-08 09:57:55,046Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-40) [5830ba58] Ending > command > 'org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand' > successfully. > > 2019-10-08 09:57:58,077Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-76) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Command 'AddVm' id: > '1b65f576-365d-4e8b-a920-621516cbdaed' child commands > '[f1665b66-2032-4a60-944e-c04beace088e]' executions were completed, > status 'FAILED' > > 2019-10-08 09:57:59,094Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.AddVmCommand' with failure. > > 2019-10-08 09:57:59,099Z ERROR > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' > with failure. > > 2019-10-08 09:57:59,104Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [5794ed92] Running > command: RemoveImageCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:57:59,126Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [5794ed92] START, > DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'}), log id: 69861a78 > > 2019-10-08 09:57:59,139Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [5794ed92] EVENT_ID: > IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS > failed: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:57:59,139Z ERROR > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [5794ed92] Command > 'DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'})' execution failed: > IRSGenericException: IRSErrorException: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:57:59,139Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [5794ed92] FINISH, > DeleteImageGroupVDSCommand, return: , log id: 69861a78 > > 2019-10-08 09:57:59,139Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [5794ed92] Disk > 'd680a46a-7188-45f6-b6a7-3333f830c0b4' doesn't exist on storage domain > '935de3ac-a735-4fc8-9161-26bfd751ffc7', rolling forward > > 2019-10-08 09:57:59,149Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [5794ed92] Removed > task 'b4c4c723-4ba1-4d5a-86e6-24658a293a04' from DataBase > > 2019-10-08 09:57:59,220Z INFO > [org.ovirt.engine.core.utils.transaction.TransactionSupport] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [] transaction > rolled back > > 2019-10-08 09:57:59,220Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [] Lock freed to > object 'EngineLock:{exclusiveLocks='[centos-testvm-024=VM_NAME]', > sharedLocks='[9ac6f4ad-58d0-4a7e-b424-91f2d76abcac=TEMPLATE, > a7e42574-be60-4c94-94a5-cc4b30fdb16f=DISK]'}' > > 2019-10-08 09:57:59,233Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [] EVENT_ID: > USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM > centos-testvm-024 creation. > > 2019-10-08 09:57:59,233Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [] Failed invoking > callback end method 'onFailed' for command > '1b65f576-365d-4e8b-a920-621516cbdaed' with exception 'null', the > callback is marked for end method retries > > 2019-10-08 09:58:01,252Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.AddVmCommand' with failure. > > 2019-10-08 09:58:01,257Z ERROR > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' > with failure. > > 2019-10-08 09:58:01,270Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [19251787] Running > command: RemoveImageCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:58:01,308Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [19251787] START, > DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'}), log id: 35fec55 > > 2019-10-08 09:58:01,324Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [19251787] EVENT_ID: > IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS > failed: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:01,324Z ERROR > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [19251787] Command > 'DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'})' execution failed: > IRSGenericException: IRSErrorException: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:01,324Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [19251787] FINISH, > DeleteImageGroupVDSCommand, return: , log id: 35fec55 > > 2019-10-08 09:58:01,324Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [19251787] Disk > 'd680a46a-7188-45f6-b6a7-3333f830c0b4' doesn't exist on storage domain > '935de3ac-a735-4fc8-9161-26bfd751ffc7', rolling forward > > 2019-10-08 09:58:01,335Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [19251787] Removed > task '6ed0a844-5363-4afd-bffc-a80b6ace69ea' from DataBase > > 2019-10-08 09:58:01,395Z INFO > [org.ovirt.engine.core.utils.transaction.TransactionSupport] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] transaction > rolled back > > 2019-10-08 09:58:01,395Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] Trying to release > a shared lock for key: '9ac6f4ad-58d0-4a7e-b424-91f2d76abcacTEMPLATE' , > but lock does not exist > > 2019-10-08 09:58:01,395Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] Trying to release > a shared lock for key: 'a7e42574-be60-4c94-94a5-cc4b30fdb16fDISK' , but > lock does not exist > > 2019-10-08 09:58:01,395Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] Trying to release > exclusive lock which does not exist, lock key: 'centos-testvm-024VM_NAME' > > 2019-10-08 09:58:01,395Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] Lock freed to > object 'EngineLock:{exclusiveLocks='[centos-testvm-024=VM_NAME]', > sharedLocks='[9ac6f4ad-58d0-4a7e-b424-91f2d76abcac=TEMPLATE, > a7e42574-be60-4c94-94a5-cc4b30fdb16f=DISK]'}' > > 2019-10-08 09:58:01,407Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] EVENT_ID: > USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM > centos-testvm-024 creation. > > 2019-10-08 09:58:01,407Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] Failed invoking > callback end method 'onFailed' for command > '1b65f576-365d-4e8b-a920-621516cbdaed' with exception 'null', the > callback is marked for end method retries > > 2019-10-08 09:58:05,427Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.AddVmCommand' with failure. > > 2019-10-08 09:58:05,430Z ERROR > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' > with failure. > > 2019-10-08 09:58:05,437Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [cf91364] Running > command: RemoveImageCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:58:05,452Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [cf91364] START, > DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'}), log id: 6ac726b6 > > 2019-10-08 09:58:05,466Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [cf91364] EVENT_ID: > IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS > failed: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:05,466Z ERROR > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [cf91364] Command > 'DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'})' execution failed: > IRSGenericException: IRSErrorException: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:05,466Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [cf91364] FINISH, > DeleteImageGroupVDSCommand, return: , log id: 6ac726b6 > > 2019-10-08 09:58:05,467Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [cf91364] Disk > 'd680a46a-7188-45f6-b6a7-3333f830c0b4' doesn't exist on storage domain > '935de3ac-a735-4fc8-9161-26bfd751ffc7', rolling forward > > 2019-10-08 09:58:05,477Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [cf91364] Removed > task '31bd7a11-203d-4459-ac54-3c398c85771d' from DataBase > > 2019-10-08 09:58:05,490Z INFO > [org.ovirt.engine.core.utils.transaction.TransactionSupport] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] transaction > rolled back > > 2019-10-08 09:58:05,490Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] Trying to release > a shared lock for key: '9ac6f4ad-58d0-4a7e-b424-91f2d76abcacTEMPLATE' , > but lock does not exist > > 2019-10-08 09:58:05,490Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] Trying to release > a shared lock for key: 'a7e42574-be60-4c94-94a5-cc4b30fdb16fDISK' , but > lock does not exist > > 2019-10-08 09:58:05,490Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] Trying to release > exclusive lock which does not exist, lock key: 'centos-testvm-024VM_NAME' > > 2019-10-08 09:58:05,490Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] Lock freed to > object 'EngineLock:{exclusiveLocks='[centos-testvm-024=VM_NAME]', > sharedLocks='[9ac6f4ad-58d0-4a7e-b424-91f2d76abcac=TEMPLATE, > a7e42574-be60-4c94-94a5-cc4b30fdb16f=DISK]'}' > > 2019-10-08 09:58:05,503Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] EVENT_ID: > USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM > centos-testvm-024 creation. > > 2019-10-08 09:58:05,503Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] Failed invoking > callback end method 'onFailed' for command > '1b65f576-365d-4e8b-a920-621516cbdaed' with exception 'null', the > callback is marked for end method retries > > 2019-10-08 09:58:13,523Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.AddVmCommand' with failure. > > 2019-10-08 09:58:13,527Z ERROR > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' > with failure. > > 2019-10-08 09:58:13,533Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [56103b5a] Running > command: RemoveImageCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:58:13,548Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [56103b5a] START, > DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'}), log id: 33164673 > > 2019-10-08 09:58:13,560Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [56103b5a] EVENT_ID: > IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS > failed: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:13,560Z ERROR > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [56103b5a] Command > 'DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'})' execution failed: > IRSGenericException: IRSErrorException: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:13,560Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [56103b5a] FINISH, > DeleteImageGroupVDSCommand, return: , log id: 33164673 > > 2019-10-08 09:58:13,560Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [56103b5a] Disk > 'd680a46a-7188-45f6-b6a7-3333f830c0b4' doesn't exist on storage domain > '935de3ac-a735-4fc8-9161-26bfd751ffc7', rolling forward > > 2019-10-08 09:58:13,570Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [56103b5a] Removed > task 'ce6882de-2d89-4298-bdcf-86d621a54084' from DataBase > > 2019-10-08 09:58:13,583Z INFO > [org.ovirt.engine.core.utils.transaction.TransactionSupport] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] transaction > rolled back > > 2019-10-08 09:58:13,583Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] Trying to release > a shared lock for key: '9ac6f4ad-58d0-4a7e-b424-91f2d76abcacTEMPLATE' , > but lock does not exist > > 2019-10-08 09:58:13,583Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] Trying to release > a shared lock for key: 'a7e42574-be60-4c94-94a5-cc4b30fdb16fDISK' , but > lock does not exist > > 2019-10-08 09:58:13,583Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] Trying to release > exclusive lock which does not exist, lock key: 'centos-testvm-024VM_NAME' > > 2019-10-08 09:58:13,583Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] Lock freed to > object 'EngineLock:{exclusiveLocks='[centos-testvm-024=VM_NAME]', > sharedLocks='[9ac6f4ad-58d0-4a7e-b424-91f2d76abcac=TEMPLATE, > a7e42574-be60-4c94-94a5-cc4b30fdb16f=DISK]'}' > > 2019-10-08 09:58:13,595Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] EVENT_ID: > USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM > centos-testvm-024 creation. > > 2019-10-08 09:58:13,595Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] Failed invoking > callback end method 'onFailed' for command > '1b65f576-365d-4e8b-a920-621516cbdaed' with exception 'null', the > callback is marked for end method retries > > 2019-10-08 09:58:23,616Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.AddVmCommand' with failure. > > 2019-10-08 09:58:23,620Z ERROR > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' > with failure. > > 2019-10-08 09:58:23,627Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [48f2f9bd] Running > command: RemoveImageCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:58:23,642Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [48f2f9bd] START, > DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'}), log id: 7346a5bd > > 2019-10-08 09:58:23,663Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [48f2f9bd] EVENT_ID: > IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS > failed: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:23,663Z ERROR > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [48f2f9bd] Command > 'DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'})' execution failed: > IRSGenericException: IRSErrorException: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:23,663Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [48f2f9bd] FINISH, > DeleteImageGroupVDSCommand, return: , log id: 7346a5bd > > 2019-10-08 09:58:23,663Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [48f2f9bd] Disk > 'd680a46a-7188-45f6-b6a7-3333f830c0b4' doesn't exist on storage domain > '935de3ac-a735-4fc8-9161-26bfd751ffc7', rolling forward > > 2019-10-08 09:58:23,682Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [48f2f9bd] Removed > task '8483357d-6d4f-418e-9751-70fcb69685cb' from DataBase > > 2019-10-08 09:58:23,695Z INFO > [org.ovirt.engine.core.utils.transaction.TransactionSupport] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] transaction > rolled back > > 2019-10-08 09:58:23,695Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] Trying to release > a shared lock for key: '9ac6f4ad-58d0-4a7e-b424-91f2d76abcacTEMPLATE' , > but lock does not exist > > 2019-10-08 09:58:23,695Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] Trying to release > a shared lock for key: 'a7e42574-be60-4c94-94a5-cc4b30fdb16fDISK' , but > lock does not exist > > 2019-10-08 09:58:23,695Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] Trying to release > exclusive lock which does not exist, lock key: 'centos-testvm-024VM_NAME' > > 2019-10-08 09:58:23,695Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] Lock freed to > object 'EngineLock:{exclusiveLocks='[centos-testvm-024=VM_NAME]', > sharedLocks='[9ac6f4ad-58d0-4a7e-b424-91f2d76abcac=TEMPLATE, > a7e42574-be60-4c94-94a5-cc4b30fdb16f=DISK]'}' > > 2019-10-08 09:58:23,706Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] EVENT_ID: > USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM > centos-testvm-024 creation. > > 2019-10-08 09:58:23,706Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] Failed invoking > callback end method 'onFailed' for command > '1b65f576-365d-4e8b-a920-621516cbdaed' with exception 'null', the > callback is marked for end method retries > > 2019-10-08 09:58:33,725Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.AddVmCommand' with failure. > > 2019-10-08 09:58:33,729Z ERROR > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' > with failure. > > 2019-10-08 09:58:33,736Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [3eea0406] Running > command: RemoveImageCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:58:33,752Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [3eea0406] START, > DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'}), log id: 6d120001 > > 2019-10-08 09:58:33,767Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [3eea0406] EVENT_ID: > IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS > failed: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:33,767Z ERROR > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [3eea0406] Command > 'DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'})' execution failed: > IRSGenericException: IRSErrorException: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:33,767Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [3eea0406] FINISH, > DeleteImageGroupVDSCommand, return: , log id: 6d120001 > > 2019-10-08 09:58:33,767Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [3eea0406] Disk > 'd680a46a-7188-45f6-b6a7-3333f830c0b4' doesn't exist on storage domain > '935de3ac-a735-4fc8-9161-26bfd751ffc7', rolling forward > > 2019-10-08 09:58:33,778Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [3eea0406] Removed > task 'bfb5e88a-0e62-4e03-b02b-a5a0b36f84db' from DataBase > > 2019-10-08 09:58:33,791Z INFO > [org.ovirt.engine.core.utils.transaction.TransactionSupport] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] transaction > rolled back > > 2019-10-08 09:58:33,791Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] Trying to release > a shared lock for key: '9ac6f4ad-58d0-4a7e-b424-91f2d76abcacTEMPLATE' , > but lock does not exist > > 2019-10-08 09:58:33,791Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] Trying to release > a shared lock for key: 'a7e42574-be60-4c94-94a5-cc4b30fdb16fDISK' , but > lock does not exist > > 2019-10-08 09:58:33,791Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] Trying to release > exclusive lock which does not exist, lock key: 'centos-testvm-024VM_NAME' > > 2019-10-08 09:58:33,791Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] Lock freed to > object 'EngineLock:{exclusiveLocks='[centos-testvm-024=VM_NAME]', > sharedLocks='[9ac6f4ad-58d0-4a7e-b424-91f2d76abcac=TEMPLATE, > a7e42574-be60-4c94-94a5-cc4b30fdb16f=DISK]'}' > > 2019-10-08 09:58:33,804Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] EVENT_ID: > USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM > centos-testvm-024 creation. > > 2019-10-08 09:58:33,824Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Failed invoking callback end > method 'onFailed' for command '1b65f576-365d-4e8b-a920-621516cbdaed' > with exception 'null', the callback is marked for end method retries but > max number of retries have been attempted. The command will be marked as > Failed. > > 2019-10-08 09:58:33,824Z INFO > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Exception in invoking callback of > command AddVm (1b65f576-365d-4e8b-a920-621516cbdaed): NullPointerException: > > 2019-10-08 09:58:33,824Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Error invoking callback method > 'onFailed' for 'FAILED' command '1b65f576-365d-4e8b-a920-621516cbdaed' > > 2019-10-08 09:58:33,824Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Exception: > javax.ejb.EJBTransactionRolledbackException > > at > org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:203) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:420) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:148) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) > > at > org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) > [weld-ejb-3.1.1.Final.jar:3.1.1.Final] > > at > org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438) > > at > org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:618) > > at > org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57) > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) > > at > org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) > > at > org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > > at > org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81) > > at > org.ovirt.engine.core.bll.interfaces.BackendInternal$$$view3.endAction(Unknown > Source) [bll.jar:] > > at > sun.reflect.GeneratedMethodAccessor1032.invoke(Unknown Source) [:1.8.0_222] > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [rt.jar:1.8.0_222] > > at java.lang.reflect.Method.invoke(Method.java:498) > [rt.jar:1.8.0_222] > > at > org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:410) > [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] > > at > org.jboss.weld.module.ejb.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:134) > [weld-ejb-3.1.1.Final.jar:3.1.1.Final] > > at > org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) > [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] > > at > org.jboss.weld.module.ejb.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:68) > [weld-ejb-3.1.1.Final.jar:3.1.1.Final] > > at > org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106) > [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] > > at > org.ovirt.engine.core.bll.BackendCommandObjectsHandler$BackendInternal$BackendLocal$2049259618$Proxy$_$$_Weld$EnterpriseProxy$.endAction(Unknown > Source) [bll.jar:] > > at > org.ovirt.engine.core.bll.VmCommand.endActionOnDisks(VmCommand.java:266) > [bll.jar:] > > at > org.ovirt.engine.core.bll.AddVmCommand.endWithFailure(AddVmCommand.java:1452) > [bll.jar:] > > at > org.ovirt.engine.core.bll.CommandBase.internalEndWithFailure(CommandBase.java:736) > [bll.jar:] > > at > org.ovirt.engine.core.bll.CommandBase.endActionInTransactionScope(CommandBase.java:658) > [bll.jar:] > > at > org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2003) > [bll.jar:] > > at > org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInNewTransaction(TransactionSupport.java:202) > [utils.jar:] > > at > org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInRequired(TransactionSupport.java:137) > [utils.jar:] > > at > org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:105) > [utils.jar:] > > at > org.ovirt.engine.core.bll.CommandBase.endAction(CommandBase.java:520) > [bll.jar:] > > at > org.ovirt.engine.core.bll.ChildCommandsCallbackBase.endAction(ChildCommandsCallbackBase.java:134) > [bll.jar:] > > at > org.ovirt.engine.core.bll.ChildCommandsCallbackBase.onFailed(ChildCommandsCallbackBase.java:174) > [bll.jar:] > > at > org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.endCallback(CommandCallbacksPoller.java:67) > [bll.jar:] > > at > org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:166) > [bll.jar:] > > at > org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:109) > [bll.jar:] > > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [rt.jar:1.8.0_222] > > at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > [rt.jar:1.8.0_222] > > at > org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383) > [javax.enterprise.concurrent-1.0.jar:] > > at > org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534) > [javax.enterprise.concurrent-1.0.jar:] > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [rt.jar:1.8.0_222] > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [rt.jar:1.8.0_222] > > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_222] > > at > org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) > [javax.enterprise.concurrent-1.0.jar:] > > Caused by: java.lang.NullPointerException > > *Ansible output:* > > The full traceback is: > > Traceback (most recent call last): > > File > "/var/folders/40/w2c8fp151854mddz_4n3czwm0000gn/T/ansible_ovirt_vm_payload_uy4lqway/__main__.py", > line 2024, in main > > clone_permissions=module.params['clone_permissions'], > > File > "/var/folders/40/w2c8fp151854mddz_4n3czwm0000gn/T/ansible_ovirt_vm_payload_uy4lqway/ansible_ovirt_vm_payload.zip/ansible/module_utils/ovirt.py", > line 610, in create > > poll_interval=self._module.params['poll_interval'], > > File > "/var/folders/40/w2c8fp151854mddz_4n3czwm0000gn/T/ansible_ovirt_vm_payload_uy4lqway/ansible_ovirt_vm_payload.zip/ansible/module_utils/ovirt.py", > line 341, in wait > > raise Exception("Timeout exceed while waiting on result state of > the entity.") > > Exception: Timeout exceed while waiting on result state of the entity. > > fatal: [centos-testvm-024.avinity.tv<http://centos-testvm-024.avinity.tv> -> localhost]: FAILED! => { > > "changed": false, > > "invocation": { > > "module_args": { > > "affinity_group_mappings": [], > > "affinity_label_mappings": [], > > "allow_partial_import": null, > > "ballooning_enabled": null, > > "boot_devices": null, > > "boot_menu": null, > > "cd_iso": null, > > "clone": false, > > "clone_permissions": false, > > "cloud_init": { > > "authorized_ssh_keys": "ssh-rsa removed pubkey", > > "host_name": "centos-testvm-024.avinity.tv<http://centos-testvm-024.avinity.tv>", > > "user_name": "centos" > > }, > > "cloud_init_nics": [], > > "cloud_init_persist": false, > > "cluster": "avshared1", > > "cluster_mappings": [], > > "comment": "oVirt Template Bakery Validation", > > "cpu_cores": null, > > "cpu_mode": null, > > "cpu_pinning": null, > > "cpu_shares": null, > > "cpu_sockets": null, > > "cpu_threads": null, > > "custom_compatibility_version": null, > > "custom_properties": null, > > "delete_protected": null, > > "description": null, > > "disk_format": "cow", > > "disks": [], > > "domain_mappings": [], > > "fetch_nested": false, > > "force": false, > > "graphical_console": null, > > "high_availability": null, > > "high_availability_priority": null, > > "host": null, > > "host_devices": null, > > "id": null, > > "initrd_path": null, > > "instance_type": "Medium", > > "io_threads": null, > > "kernel_params": null, > > "kernel_path": null, > > "kvm": null, > > "lease": null, > > "lun_mappings": [], > > "memory": null, > > "memory_guaranteed": null, > > "memory_max": null, > > "name": "centos-testvm-024", > > "nested_attributes": [], > > "nics": [ > > { > > "interface": "virtio", > > "name": "nic1", > > "profile_name": "tenant1" > > } > > ], > > "numa_nodes": [], > > "numa_tune_mode": null, > > "operating_system": null, > > "placement_policy": null, > > "poll_interval": 3, > > "quota_id": null, > > "reassign_bad_macs": null, > > "rng_device": null, > > "role_mappings": [], > > "serial_console": null, > > "serial_policy": null, > > "serial_policy_value": null, > > "smartcard_enabled": null, > > "soundcard_enabled": null, > > "sso": null, > > "state": "running", > > "stateless": null, > > "storage_domain": null, > > "sysprep": null, > > "template": "av-centos-75-baseimage_nfs9000", > > "template_version": null, > > "ticket": null, > > "timeout": 180, > > "timezone": null, > > "type": null, > > "usb_support": null, > > "use_latest_template_version": null, > > "vmware": null, > > "vnic_profile_mappings": [], > > "wait": true, > > "watchdog": null, > > "xen": null > > } > > }, > > "msg": "Timeout exceed while waiting on result state of the entity." > > } > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> > To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/EB5AXLUNU6LRV… > _______________________________________________ Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ATKD7TYOKB2UH… -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o. -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o. -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o. -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o. -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

1 0

VMs Locked - vProtect snapshots
by joseph＠goldman.id.au 25 Nov '19

25 Nov '19

After a few tricky power issues at a site in a less developed country, I had to restart my 3 node ovirt cluster with hosted engine. Everything seemed to come up fine, but that night when my scheduled snapshots/backups etc ran (vProtect) some weird things happened. It created a couple snapshots and couldn't copy them saying disk is locked (even though in the GUI no disks or snapshots were locked) After a couple tries all of a sudden the whole VM is 'locked' this means I can't migrate it, cant start it (if it shuts down) couldn't remove old snapshots etc. I had this happen on another VM and my only solution there was to clone it, but now its happened to all of them and im not sure why. I have run the db utility on command line to unlock everything, nothing is listed as locked, but I still cant run any operations on the VM's. I even cloned them to get them up and running again, but I can't delete the old VM still sitting there (or the disk, snapshots or anything) just keep getting VM is locked. How the hell do I force an unlock of these entities when everything tells me its not locked? I'm almost at a point where I want to back up all VM's and start again but i'd much rather learn some more so I can manage these issues in future. Any help is appreciated! thanks

2 2

Gluster setup 3 Node - Now only showing single node setup in setup Wizard
by rob.downer＠orbitalsystems.co.uk 25 Nov '19

25 Nov '19

I have set up 3 Nodes with a separate volume for Gluster, I have set up the two networks and DNS works fine SSH has been set up for Gluster and you can login via ssh to the other two hosts from the host used to set up. When going to Virtualisation > Setup Gluster and Hosted Engine only single node shows up. I have restarted all 3 machines. All nodes machines show up in Dashboard etc... I have set this up before but it all worked, I erased everything and set up again with the separate volume to be used for Gluster storage

3 4

Beginning oVirt / Hyperconverged
by email＠christian-reiss.de 25 Nov '19

25 Nov '19

Hey folks! Quick question, really: I have 4 servers of identical hardware. The documentation says "you need 3", not "you need 3 or more"; is it possible to run hyperconverged with 4 servers (in same rack, let's neglect the possibility of 2 failing servers (split brain))? Also: I have a nice seperate server (low power footprint, big on cpu (8) and has 32gb ram)-- would love to use this as engine server only. Can I initiate a hyperconverged system with 4 working host starting from a stand-alone engine? Or does "hyperconverged" a must for HA engine on the cluster? One last one: Installing ovirt nodes, obviously. This will by default create a lvm across the entire RAID volume; can I simply create folders (with correct permissions) and use those as gluster bricks? Or do I need to partition the RAID in a special way? Thanks for your pointers, Chris.

4 3

Windows 2019 Server - Memory Usage
by Joseph Goldman 24 Nov '19

24 Nov '19

Hi List, My Windows Server 2019 installs dont seem to report memory usage to the ovirt engine. They have the ovirt-guest-agent installed, is there something else I need to do to get them reporting back to the engine/hypervisor? Thanks, Joe

1 0

VM Lock state location
by Joseph Goldman 24 Nov '19

24 Nov '19

Hi *, Trying to figure out where a VM's lockstate is stored. I have a few VM's that seem to be stuck in lock state. I have done an ./unlock_entity.sh -t all, and a -q gives me nothing in a lock state. I have jumped on psql DB direct and looked through as many tables as I can looking for a locked status, everything seems fine. In the engine, on these VM's if I try to do any actions I get a message similar to: 'Failed to Acquire Lock to object 'EngineLock:{exclusiveLocks='[6c2fc524-2f13-4cad-9108-347be2e88d1a=VM]', sharedLocks=''}'' When this issue first started, I was trying to do backups with snapshots, I got a lot of messages similar to this: /var/log/ovirt-engine/engine.log-20191121.gz:2019-11-20 11:44:30,441+10 WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-41) [6cafc1ef] Trying to release a shared lock for key: '6 c2fc524-2f13-4cad-9108-347be2e88d1aVM' , but lock does not exist /var/log/ovirt-engine/engine.log-20191121.gz:2019-11-20 11:44:30,441+10 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-41) [6cafc1ef] Lock freed to object ' EngineLock:{exclusiveLocks='', sharedLocks='[6c2fc524-2f13-4cad-9108-347be2e88d1a=VM, ab5d4e18-f0c6-4472-8d2e-8c3bd1ff1a6a=DISK]'}' I have made sure there is nothing in async_tasks, commands and the _entities tables for both. There was some command_entities, but I took a backup of the engine and decided to run a delete on that table (There was about 5 stuck records there) but that hasn't helped The affected VMs, cant delete snapshots, cant delete their disks, cant delete the VM, cant boot the VMs - they are just stuck in the engine. My ultimate question is, where is the engine looking up that lockstate as I believe it is stuck locked in error, so I can go there and manually force a removal of the lock state and at least delete these VM's - as ultimately I have cloned them to get the VM's back up and running. Can anyone point me in the right direction? Willing to pay consulting fee if you believe you have the answer for this one. Thanks, Joe

3 4

oVirt Admin Portal unaccessible via chrome (firefox works)
by Strahil Nikolov 24 Nov '19

24 Nov '19

Hello Community, I have a constantly loading chrome on my openSuSE 15.1 (and my android phone), while firefox has no issues . Can someone test accessing the oVirt Admin portal via chrome on x86_64 Linux ? Best Regards,Strahil Nikolov

5 5

Ovirt 4.3.6 USB passthrough not working with iommu_intel=on iommu=pt
by Don Dupuis 24 Nov '19

24 Nov '19

I am trying to pass through a USB Dongle to a Windows virtual machine in ovirt 4.3.6. This will work if these options aren't used. Below is the output of lsusb with no iommu enable: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 1604:10c0 Tascam Bus 001 Device 004: ID 1604:10c0 Tascam Bus 001 Device 003: ID 1604:10c0 Tascam Bus 001 Device 002: ID 07f2:0001 Microcomputer Applications, Inc. KEYLOK II Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The device I am passing through is Bus 001 Device 002. This is the error I get in vdsmd.log: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 867, in _startUnderlyingVm self._run() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2890, in _run self._domDependentInit() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2466, in _domDependentInit self._vmDependentInit() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2480, in _vmDependentInit self._getUnderlyingVmDevicesInfo() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2448, in _getUnderlyingVmDevicesInfo vmdevices.common.update_device_info(self, self._devices) File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/common.py", line 94, in update_device_info hostdevice.HostDevice.update_device_info(vm, devices[hwclass.HOSTDEV]) File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/hostdevice.py", line 426, in update_device_info vm, device_conf, device_xml) File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/hostdevice.py", line 223, in update_from_xml if host_address == dev.hostAddress: AttributeError: 'MdevDevice' object has no attribute 'hostAddress' 2019-11-18 18:20:06,173-0600 INFO (vm/9944089c) [virt.vm] (vmId='9944089c-2109-4352-a0c6-7d0d9e04bb3f') Changed state to Down: 'MdevDevice' object has no attribute 'hostAddress' (code=1) (vm:1690) I am using kernel 3.10.0-957.12.1.el7.x86_64 vdsm is vdsm-4.30.33-1.el7.x86_64 libvirt is libvirt-5.0.0-1.el7.x86_64 qemu is qemu-img-ev-2.12.0-33.1.el7.x86_64 Any help with this issue would be appreciated. Thanks Don

4 9

metrics
by suporte＠logicworks.pt 24 Nov '19

24 Nov '19

Hi, I'm trying to install metrics for Version 4.3.6.7-1.el7 Do I need a RH subscription to downloading the RHEL guest image? (qcow_url:) Thanks -- Jose Ferradeira http://www.logicworks.pt

4 17

Export of disk possible?
by Gianluca Cecchi 24 Nov '19

24 Nov '19

Hello, in 4.3 I can: - Storage -> Domains -> Select Domain -> Disks -> Select Disk -> Download and this will download the disk image to my client, that then I can upload to a different environment - Storage -> Disks -> Select Disk -> Export But then, even if I have an export domain active I get this kind of window that I don't understand.... https://drive.google.com/file/d/1UU7NaoQ9F01oEkciUgz29HW-4dOPQVeF/view?usp=… Perhaps it means another DC managed by the same Engine is needed? How can I export a virtual disk from an engine environment to another engine environment? Yes, I can artificially create a VM and attach the disk to it and then export the VM, but is there a functionality to directly export a disk to an export domain? Thanks, Gianluca

2 1

Dm-VDO in Gluster
by rob.downer＠orbitalsystems.co.uk 23 Nov '19

23 Nov '19

I have 3 nodes set up with a 2TB Partition on each for Gluster set up. The drives are all SSD should I enable DM-VDO ? has anyone one got a simple / Pro / Con list ? I understand response is slower if enabled also some CPU hit both are acceptable. Thanks

1 0

Howto recover/reinstall a failed oVirt node in a 3 node HCI cluster
by Timo Eissler 22 Nov '19

22 Nov '19

Hello, i can't find the documentation on howto recover from a single host OS disk failure in a 3 node HCI cluster. I already searched the ovirt, RHV and RHHI documentation but i can't find the corresponding documentation. So can anyone please give me some hints? In our dev lab i have 3 servers with 2 disks each. sda for ovirt node and sdb for gluster. Let's assume the disk sda of a single node is defunct and needs to be replaced. So i grab a new disk and reinstall ovirt node from PXE. After the installation is finished i would like to reinstall the host from ovirt admin portal, but that doesn't work because of an invalid fingerprint. So how can i re-add that host to ovirt and gluster? Kind regards, Timo

2 1

python ovirtsdk
by serphentos＠sharedlink.tk 22 Nov '19

22 Nov '19

Hello. Can someone explain how to attach logical network to host via ovirtsdk? I saw a example of attaching networks to cluster or dc, but not a host https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/assign_n…

2 2

Re: Fail to attach/create disk from template when running via Ansible
by Vrgotic, Marko 21 Nov '19

21 Nov '19

Hi Ondra, I have rebuilt the staging with 4.3.6 and still same issue. Images are there, I can again create VM via UI, but not via Ansible. Here is the output of the complete run form engine.log: 2019-11-12 12:09:00,457Z INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-49) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2019-11-12 12:09:00,978Z INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-49) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2019-11-12 12:09:01,538Z INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-49) [233de27] Running command: CreateUserSessionCommand internal: false. 2019-11-12 12:09:01,549Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-49) [233de27] EVENT_ID: USER_VDC_LOGIN(30), User admin@internal-authz connecting from '172.16.105.206' using session 'bsgNpfGJTNtzuuQWSyXVJqHhpLK4TY9TQRERWxxzGtpHonoqdk7WIHGZ7mID2+QkBKH9bPp8HVhyvDu66tzPnQ==' logged in. 2019-11-12 12:09:01,691Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Lock Acquired to object 'EngineLock:{exclusiveLocks='[centos-testvm-a910=VM_NAME]', sharedLocks='[400688e8-3c5b-4cca-9ef8-bbb6c79d54ed=DISK, 819aecf6-c83d-4470-9915-e309390d8098=TEMPLATE]'}' 2019-11-12 12:09:01,773Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Running command: AddVmCommand internal: false. Entities affected : ID: d3c90169-ecc8-46a0-a4ec-7c3d99b81b61 Type: ClusterAction group CREATE_VM with role type USER, ID: 819aecf6-c83d-4470-9915-e309390d8098 Type: VmTemplateAction group CREATE_VM with role type USER, ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: StorageAction group CREATE_DISK with role type USER 2019-11-12 12:09:01,866Z INFO [org.ovirt.engine.core.bll.AddRngDeviceCommand] (default task-49) [4d4703a1] Running command: AddRngDeviceCommand internal: true. Entities affected : ID: 6343c55a-c67e-4d75-a767-dfc9412006e6 Type: VMAction group EDIT_VM_PROPERTIES with role type USER 2019-11-12 12:09:01,876Z INFO [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default task-49) [4d4703a1] START, SetVmStatusVDSCommand( SetVmStatusVDSCommandParameters:{vmId='6343c55a-c67e-4d75-a767-dfc9412006e6', status='ImageLocked', exitStatus='Normal'}), log id: 4eedcefb 2019-11-12 12:09:01,887Z INFO [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default task-49) [4d4703a1] FINISH, SetVmStatusVDSCommand, return: , log id: 4eedcefb 2019-11-12 12:09:01,906Z INFO [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Running command: CreateSnapshotFromTemplateCommand internal: true. Entities affected : ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: Storage 2019-11-12 12:09:01,928Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] START, CreateVolumeVDSCommand( CreateVolumeVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', imageSizeInBytes='8589934592', volumeFormat='COW', newImageId='7270dd54-a075-4b14-aca3-7c2a118057f0', imageType='Sparse', newImageDescription='', imageInitialSizeInBytes='0', imageId='767c6837-5191-4650-a49d-abca7d69a708', sourceImageGroupId='400688e8-3c5b-4cca-9ef8-bbb6c79d54ed'}), log id: 2dfac68e 2019-11-12 12:09:02,009Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] FINISH, CreateVolumeVDSCommand, return: 7270dd54-a075-4b14-aca3-7c2a118057f0, log id: 2dfac68e 2019-11-12 12:09:02,014Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] CommandAsyncTask::Adding CommandMultiAsyncTasks object for command 'fb915b7e-4814-4e93-a3ef-4f40c4e3c41b' 2019-11-12 12:09:02,014Z INFO [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] CommandMultiAsyncTasks::attachTask: Attaching task '0eb09758-113f-43b9-aa67-97d2e5a57e05' to command 'fb915b7e-4814-4e93-a3ef-4f40c4e3c41b'. 2019-11-12 12:09:02,027Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Adding task '0eb09758-113f-43b9-aa67-97d2e5a57e05' (Parent Command 'CreateSnapshotFromTemplate', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling hasn't started yet.. 2019-11-12 12:09:02,098Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] EVENT_ID: USER_ADD_VM_STARTED(37), VM centos-testvm-a910 creation was initiated by admin@internal-authz. 2019-11-12 12:09:02,098Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (default task-49) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] BaseAsyncTask::startPollingTask: Starting to poll task '0eb09758-113f-43b9-aa67-97d2e5a57e05'. 2019-11-12 12:09:02,758Z INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-19) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Command 'AddVm' (id: '97d4103b-acef-4b55-a379-71a1baa04a4f') waiting on child command id: 'fb915b7e-4814-4e93-a3ef-4f40c4e3c41b' type:'CreateSnapshotFromTemplate' to complete 2019-11-12 12:09:04,773Z INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-52) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Command 'AddVm' (id: '97d4103b-acef-4b55-a379-71a1baa04a4f') waiting on child command id: 'fb915b7e-4814-4e93-a3ef-4f40c4e3c41b' type:'CreateSnapshotFromTemplate' to complete 2019-11-12 12:09:06,117Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-26) [] Polling and updating Async Tasks: 1 tasks, 1 tasks to poll now 2019-11-12 12:09:06,121Z ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksStatusesVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-26) [] Failed in 'HSMGetAllTasksStatusesVDS' method 2019-11-12 12:09:06,128Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-26) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt-staging-hv-02.avinity.tv command HSMGetAllTasksStatusesVDS failed: Invalid parameter: 'capacity=8589934592' 2019-11-12 12:09:06,128Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-26) [] SPMAsyncTask::PollTask: Polling task '0eb09758-113f-43b9-aa67-97d2e5a57e05' (Parent Command 'CreateSnapshotFromTemplate', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned status 'finished', result 'cleanSuccess'. 2019-11-12 12:09:06,131Z ERROR [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-26) [] BaseAsyncTask::logEndTaskFailure: Task '0eb09758-113f-43b9-aa67-97d2e5a57e05' (Parent Command 'CreateSnapshotFromTemplate', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended with failure: -- Result: 'cleanSuccess' -- Message: 'VDSGenericException: VDSErrorException: Failed to HSMGetAllTasksStatusesVDS, error = Invalid parameter: 'capacity=8589934592', code = 100', -- Exception: 'VDSGenericException: VDSErrorException: Failed to HSMGetAllTasksStatusesVDS, error = Invalid parameter: 'capacity=8589934592', code = 100' 2019-11-12 12:09:06,133Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-26) [] CommandAsyncTask::endActionIfNecessary: All tasks of command 'fb915b7e-4814-4e93-a3ef-4f40c4e3c41b' has ended -> executing 'endAction' 2019-11-12 12:09:06,133Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-26) [] CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: 'fb915b7e-4814-4e93-a3ef-4f40c4e3c41b'): calling endAction '. 2019-11-12 12:09:06,133Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-274926) [] CommandAsyncTask::endCommandAction [within thread] context: Attempting to endAction 'CreateSnapshotFromTemplate', 2019-11-12 12:09:06,137Z INFO [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Command [id=fb915b7e-4814-4e93-a3ef-4f40c4e3c41b]: Updating status to 'FAILED', The command end method logic will be executed by one of its parent commands. 2019-11-12 12:09:06,137Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'CreateSnapshotFromTemplate' completed, handling the result. 2019-11-12 12:09:06,137Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'CreateSnapshotFromTemplate' succeeded, clearing tasks. 2019-11-12 12:09:06,137Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] SPMAsyncTask::ClearAsyncTask: Attempting to clear task '0eb09758-113f-43b9-aa67-97d2e5a57e05' 2019-11-12 12:09:06,137Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', taskId='0eb09758-113f-43b9-aa67-97d2e5a57e05'}), log id: baaf58a 2019-11-12 12:09:06,138Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] START, HSMClearTaskVDSCommand(HostName = ovirt-staging-hv-02.avinity.tv, HSMTaskGuidBaseVDSCommandParameters:{hostId='3c70c563-e32e-4352-b1e1-f6bcc41f77e2', taskId='0eb09758-113f-43b9-aa67-97d2e5a57e05'}), log id: 7321c57d 2019-11-12 12:09:06,147Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] FINISH, HSMClearTaskVDSCommand, return: , log id: 7321c57d 2019-11-12 12:09:06,147Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] FINISH, SPMClearTaskVDSCommand, return: , log id: baaf58a 2019-11-12 12:09:06,152Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] BaseAsyncTask::removeTaskFromDB: Removed task '0eb09758-113f-43b9-aa67-97d2e5a57e05' from DataBase 2019-11-12 12:09:06,152Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-274926) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] CommandAsyncTask::HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object for entity 'fb915b7e-4814-4e93-a3ef-4f40c4e3c41b' 2019-11-12 12:09:08,790Z INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-34) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Command 'AddVm' id: '97d4103b-acef-4b55-a379-71a1baa04a4f' child commands '[fb915b7e-4814-4e93-a3ef-4f40c4e3c41b]' executions were completed, status 'FAILED' 2019-11-12 12:09:09,821Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.AddVmCommand' with failure. 2019-11-12 12:09:09,825Z ERROR [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' with failure. 2019-11-12 12:09:09,835Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [44f6ef0c] Running command: RemoveImageCommand internal: true. Entities affected : ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: Storage 2019-11-12 12:09:09,873Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [44f6ef0c] START, DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'}), log id: 28915db3 2019-11-12 12:09:09,907Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [44f6ef0c] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:09,907Z ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [44f6ef0c] Command 'DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'})' execution failed: IRSGenericException: IRSErrorException: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:09,907Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [44f6ef0c] FINISH, DeleteImageGroupVDSCommand, return: , log id: 28915db3 2019-11-12 12:09:09,907Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [44f6ef0c] Disk '56ddac45-1913-4d24-af97-2f969fc3fa2e' doesn't exist on storage domain '78bfcb57-3a0d-4a71-a3f8-480ebae37c74', rolling forward 2019-11-12 12:09:09,918Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [44f6ef0c] Removed task '25bf448d-9271-4a85-ad9b-9c63012753ac' from DataBase 2019-11-12 12:09:09,983Z INFO [org.ovirt.engine.core.utils.transaction.TransactionSupport] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] transaction rolled back 2019-11-12 12:09:09,983Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] Lock freed to object 'EngineLock:{exclusiveLocks='[centos-testvm-a910=VM_NAME]', sharedLocks='[400688e8-3c5b-4cca-9ef8-bbb6c79d54ed=DISK, 819aecf6-c83d-4470-9915-e309390d8098=TEMPLATE]'}' 2019-11-12 12:09:10,001Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] EVENT_ID: USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM centos-testvm-a910 creation. 2019-11-12 12:09:10,002Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-13) [] Failed invoking callback end method 'onFailed' for command '97d4103b-acef-4b55-a379-71a1baa04a4f' with exception 'null', the callback is marked for end method retries 2019-11-12 12:09:12,019Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.AddVmCommand' with failure. 2019-11-12 12:09:12,023Z ERROR [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' with failure. 2019-11-12 12:09:12,041Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [1b861e85] Running command: RemoveImageCommand internal: true. Entities affected : ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: Storage 2019-11-12 12:09:12,063Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [1b861e85] START, DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'}), log id: 376f65dc 2019-11-12 12:09:12,090Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [1b861e85] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:12,090Z ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [1b861e85] Command 'DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'})' execution failed: IRSGenericException: IRSErrorException: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:12,090Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [1b861e85] FINISH, DeleteImageGroupVDSCommand, return: , log id: 376f65dc 2019-11-12 12:09:12,090Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [1b861e85] Disk '56ddac45-1913-4d24-af97-2f969fc3fa2e' doesn't exist on storage domain '78bfcb57-3a0d-4a71-a3f8-480ebae37c74', rolling forward 2019-11-12 12:09:12,101Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [1b861e85] Removed task 'ebe0e879-8595-44db-9d64-e237afd6c8e8' from DataBase 2019-11-12 12:09:12,157Z INFO [org.ovirt.engine.core.utils.transaction.TransactionSupport] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] transaction rolled back 2019-11-12 12:09:12,157Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Trying to release a shared lock for key: '400688e8-3c5b-4cca-9ef8-bbb6c79d54edDISK' , but lock does not exist 2019-11-12 12:09:12,157Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Trying to release a shared lock for key: '819aecf6-c83d-4470-9915-e309390d8098TEMPLATE' , but lock does not exist 2019-11-12 12:09:12,157Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Trying to release exclusive lock which does not exist, lock key: 'centos-testvm-a910VM_NAME' 2019-11-12 12:09:12,157Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Lock freed to object 'EngineLock:{exclusiveLocks='[centos-testvm-a910=VM_NAME]', sharedLocks='[400688e8-3c5b-4cca-9ef8-bbb6c79d54ed=DISK, 819aecf6-c83d-4470-9915-e309390d8098=TEMPLATE]'}' 2019-11-12 12:09:12,172Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] EVENT_ID: USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM centos-testvm-a910 creation. 2019-11-12 12:09:12,172Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Failed invoking callback end method 'onFailed' for command '97d4103b-acef-4b55-a379-71a1baa04a4f' with exception 'null', the callback is marked for end method retries 2019-11-12 12:09:16,192Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.AddVmCommand' with failure. 2019-11-12 12:09:16,195Z ERROR [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' with failure. 2019-11-12 12:09:16,215Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [8f3849f] Running command: RemoveImageCommand internal: true. Entities affected : ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: Storage 2019-11-12 12:09:16,240Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [8f3849f] START, DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'}), log id: 75027448 2019-11-12 12:09:16,263Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [8f3849f] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:16,263Z ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [8f3849f] Command 'DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'})' execution failed: IRSGenericException: IRSErrorException: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:16,263Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [8f3849f] FINISH, DeleteImageGroupVDSCommand, return: , log id: 75027448 2019-11-12 12:09:16,263Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [8f3849f] Disk '56ddac45-1913-4d24-af97-2f969fc3fa2e' doesn't exist on storage domain '78bfcb57-3a0d-4a71-a3f8-480ebae37c74', rolling forward 2019-11-12 12:09:16,274Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [8f3849f] Removed task '688274fc-0596-44b5-b167-36c86b8b8e5d' from DataBase 2019-11-12 12:09:16,341Z INFO [org.ovirt.engine.core.utils.transaction.TransactionSupport] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] transaction rolled back 2019-11-12 12:09:16,341Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] Trying to release a shared lock for key: '400688e8-3c5b-4cca-9ef8-bbb6c79d54edDISK' , but lock does not exist 2019-11-12 12:09:16,341Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] Trying to release a shared lock for key: '819aecf6-c83d-4470-9915-e309390d8098TEMPLATE' , but lock does not exist 2019-11-12 12:09:16,342Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] Trying to release exclusive lock which does not exist, lock key: 'centos-testvm-a910VM_NAME' 2019-11-12 12:09:16,342Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] Lock freed to object 'EngineLock:{exclusiveLocks='[centos-testvm-a910=VM_NAME]', sharedLocks='[400688e8-3c5b-4cca-9ef8-bbb6c79d54ed=DISK, 819aecf6-c83d-4470-9915-e309390d8098=TEMPLATE]'}' 2019-11-12 12:09:16,357Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] EVENT_ID: USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM centos-testvm-a910 creation. 2019-11-12 12:09:16,357Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-78) [] Failed invoking callback end method 'onFailed' for command '97d4103b-acef-4b55-a379-71a1baa04a4f' with exception 'null', the callback is marked for end method retries 2019-11-12 12:09:24,376Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.AddVmCommand' with failure. 2019-11-12 12:09:24,380Z ERROR [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' with failure. 2019-11-12 12:09:24,387Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [153e3c43] Running command: RemoveImageCommand internal: true. Entities affected : ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: Storage 2019-11-12 12:09:24,419Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [153e3c43] START, DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'}), log id: 29a560b1 2019-11-12 12:09:24,444Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [153e3c43] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:24,444Z ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [153e3c43] Command 'DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'})' execution failed: IRSGenericException: IRSErrorException: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:24,444Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [153e3c43] FINISH, DeleteImageGroupVDSCommand, return: , log id: 29a560b1 2019-11-12 12:09:24,445Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [153e3c43] Disk '56ddac45-1913-4d24-af97-2f969fc3fa2e' doesn't exist on storage domain '78bfcb57-3a0d-4a71-a3f8-480ebae37c74', rolling forward 2019-11-12 12:09:24,455Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [153e3c43] Removed task '13b2490d-09a6-4230-a5d3-7b86b536e8c3' from DataBase 2019-11-12 12:09:24,509Z INFO [org.ovirt.engine.core.utils.transaction.TransactionSupport] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [] transaction rolled back 2019-11-12 12:09:24,509Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [] Trying to release a shared lock for key: '400688e8-3c5b-4cca-9ef8-bbb6c79d54edDISK' , but lock does not exist 2019-11-12 12:09:24,509Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [] Trying to release a shared lock for key: '819aecf6-c83d-4470-9915-e309390d8098TEMPLATE' , but lock does not exist 2019-11-12 12:09:24,509Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [] Trying to release exclusive lock which does not exist, lock key: 'centos-testvm-a910VM_NAME' 2019-11-12 12:09:24,509Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [] Lock freed to object 'EngineLock:{exclusiveLocks='[centos-testvm-a910=VM_NAME]', sharedLocks='[400688e8-3c5b-4cca-9ef8-bbb6c79d54ed=DISK, 819aecf6-c83d-4470-9915-e309390d8098=TEMPLATE]'}' 2019-11-12 12:09:24,527Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [] EVENT_ID: USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM centos-testvm-a910 creation. 2019-11-12 12:09:24,527Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-20) [] Failed invoking callback end method 'onFailed' for command '97d4103b-acef-4b55-a379-71a1baa04a4f' with exception 'null', the callback is marked for end method retries 2019-11-12 12:09:34,547Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.AddVmCommand' with failure. 2019-11-12 12:09:34,551Z ERROR [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' with failure. 2019-11-12 12:09:34,568Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [28afe05e] Running command: RemoveImageCommand internal: true. Entities affected : ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: Storage 2019-11-12 12:09:34,591Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [28afe05e] START, DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'}), log id: 207e5265 2019-11-12 12:09:34,617Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [28afe05e] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:34,617Z ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [28afe05e] Command 'DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'})' execution failed: IRSGenericException: IRSErrorException: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:34,618Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [28afe05e] FINISH, DeleteImageGroupVDSCommand, return: , log id: 207e5265 2019-11-12 12:09:34,618Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [28afe05e] Disk '56ddac45-1913-4d24-af97-2f969fc3fa2e' doesn't exist on storage domain '78bfcb57-3a0d-4a71-a3f8-480ebae37c74', rolling forward 2019-11-12 12:09:34,629Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [28afe05e] Removed task 'ad58e8d8-13cc-4ae4-8785-9df252b38c1f' from DataBase 2019-11-12 12:09:34,688Z INFO [org.ovirt.engine.core.utils.transaction.TransactionSupport] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] transaction rolled back 2019-11-12 12:09:34,688Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] Trying to release a shared lock for key: '400688e8-3c5b-4cca-9ef8-bbb6c79d54edDISK' , but lock does not exist 2019-11-12 12:09:34,688Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] Trying to release a shared lock for key: '819aecf6-c83d-4470-9915-e309390d8098TEMPLATE' , but lock does not exist 2019-11-12 12:09:34,688Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] Trying to release exclusive lock which does not exist, lock key: 'centos-testvm-a910VM_NAME' 2019-11-12 12:09:34,688Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] Lock freed to object 'EngineLock:{exclusiveLocks='[centos-testvm-a910=VM_NAME]', sharedLocks='[400688e8-3c5b-4cca-9ef8-bbb6c79d54ed=DISK, 819aecf6-c83d-4470-9915-e309390d8098=TEMPLATE]'}' 2019-11-12 12:09:34,707Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] EVENT_ID: USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM centos-testvm-a910 creation. 2019-11-12 12:09:34,707Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [] Failed invoking callback end method 'onFailed' for command '97d4103b-acef-4b55-a379-71a1baa04a4f' with exception 'null', the callback is marked for end method retries 2019-11-12 12:09:42,871Z INFO [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-75) [58fc7cd2] Lock Acquired to object 'EngineLock:{exclusiveLocks='[02a18cd9-ead2-44c7-9923-8fe84d1865ee=PROVIDER]', sharedLocks=''}' 2019-11-12 12:09:42,880Z INFO [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-75) [58fc7cd2] Running command: SyncNetworkProviderCommand internal: true. 2019-11-12 12:09:42,975Z INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-49) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2019-11-12 12:09:43,096Z INFO [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-75) [58fc7cd2] Lock freed to object 'EngineLock:{exclusiveLocks='[02a18cd9-ead2-44c7-9923-8fe84d1865ee=PROVIDER]', sharedLocks=''}' 2019-11-12 12:09:44,729Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.AddVmCommand' with failure. 2019-11-12 12:09:44,732Z ERROR [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Ending command 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' with failure. 2019-11-12 12:09:44,757Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [14057067] Running command: RemoveImageCommand internal: true. Entities affected : ID: 78bfcb57-3a0d-4a71-a3f8-480ebae37c74 Type: Storage 2019-11-12 12:09:44,780Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [14057067] START, DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'}), log id: aaea0bc 2019-11-12 12:09:44,804Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [14057067] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:44,804Z ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [14057067] Command 'DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='47523e52-311f-4829-a731-3d91f7885974', ignoreFailoverLimit='false', storageDomainId='78bfcb57-3a0d-4a71-a3f8-480ebae37c74', imageGroupId='56ddac45-1913-4d24-af97-2f969fc3fa2e', postZeros='false', discard='false', forceDelete='false'})' execution failed: IRSGenericException: IRSErrorException: Image does not exist in domain: u'image=56ddac45-1913-4d24-af97-2f969fc3fa2e, domain=78bfcb57-3a0d-4a71-a3f8-480ebae37c74' 2019-11-12 12:09:44,804Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [14057067] FINISH, DeleteImageGroupVDSCommand, return: , log id: aaea0bc 2019-11-12 12:09:44,804Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [14057067] Disk '56ddac45-1913-4d24-af97-2f969fc3fa2e' doesn't exist on storage domain '78bfcb57-3a0d-4a71-a3f8-480ebae37c74', rolling forward 2019-11-12 12:09:44,815Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [14057067] Removed task 'c964f397-f054-4d81-98d6-052ce5a30168' from DataBase 2019-11-12 12:09:44,887Z INFO [org.ovirt.engine.core.utils.transaction.TransactionSupport] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [] transaction rolled back 2019-11-12 12:09:44,887Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [] Trying to release a shared lock for key: '400688e8-3c5b-4cca-9ef8-bbb6c79d54edDISK' , but lock does not exist 2019-11-12 12:09:44,887Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [] Trying to release a shared lock for key: '819aecf6-c83d-4470-9915-e309390d8098TEMPLATE' , but lock does not exist 2019-11-12 12:09:44,888Z WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [] Trying to release exclusive lock which does not exist, lock key: 'centos-testvm-a910VM_NAME' 2019-11-12 12:09:44,888Z INFO [org.ovirt.engine.core.bll.AddVmCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [] Lock freed to object 'EngineLock:{exclusiveLocks='[centos-testvm-a910=VM_NAME]', sharedLocks='[400688e8-3c5b-4cca-9ef8-bbb6c79d54ed=DISK, 819aecf6-c83d-4470-9915-e309390d8098=TEMPLATE]'}' 2019-11-12 12:09:44,903Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [] EVENT_ID: USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM centos-testvm-a910 creation. 2019-11-12 12:09:44,924Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Failed invoking callback end method 'onFailed' for command '97d4103b-acef-4b55-a379-71a1baa04a4f' with exception 'null', the callback is marked for end method retries but max number of retries have been attempted. The command will be marked as Failed. 2019-11-12 12:09:44,925Z INFO [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Exception in invoking callback of command AddVm (97d4103b-acef-4b55-a379-71a1baa04a4f): NullPointerException: 2019-11-12 12:09:44,925Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Error invoking callback method 'onFailed' for 'FAILED' command '97d4103b-acef-4b55-a379-71a1baa04a4f' 2019-11-12 12:09:44,925Z ERROR [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] (EE-ManagedThreadFactory-engineScheduled-Thread-98) [7748e6ab-7fb3-4ec5-9b2a-c7012a050efa] Exception: javax.ejb.EJBTransactionRolledbackException at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:203) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:420) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:148) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) [weld-ejb-3.1.1.Final.jar:3.1.1.Final] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:618) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81) at org.ovirt.engine.core.bll.interfaces.BackendInternal$$$view2.endAction(Unknown Source) [bll.jar:] at sun.reflect.GeneratedMethodAccessor1071.invoke(Unknown Source) [:1.8.0_222] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_222] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_222] at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:410) [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] at org.jboss.weld.module.ejb.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:134) [weld-ejb-3.1.1.Final.jar:3.1.1.Final] at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] at org.jboss.weld.module.ejb.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:68) [weld-ejb-3.1.1.Final.jar:3.1.1.Final] at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106) [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] at org.ovirt.engine.core.bll.BackendCommandObjectsHandler$BackendInternal$BackendLocal$2049259618$Proxy$_$$_Weld$EnterpriseProxy$.endAction(Unknown Source) [bll.jar:] at org.ovirt.engine.core.bll.VmCommand.endActionOnDisks(VmCommand.java:266) [bll.jar:] at org.ovirt.engine.core.bll.AddVmCommand.endWithFailure(AddVmCommand.java:1452) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.internalEndWithFailure(CommandBase.java:736) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.endActionInTransactionScope(CommandBase.java:658) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2003) [bll.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInNewTransaction(TransactionSupport.java:202) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInRequired(TransactionSupport.java:137) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:105) [utils.jar:] at org.ovirt.engine.core.bll.CommandBase.endAction(CommandBase.java:520) [bll.jar:] at org.ovirt.engine.core.bll.ChildCommandsCallbackBase.endAction(ChildCommandsCallbackBase.java:134) [bll.jar:] at org.ovirt.engine.core.bll.ChildCommandsCallbackBase.onFailed(ChildCommandsCallbackBase.java:174) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.endCallback(CommandCallbacksPoller.java:67) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:166) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:109) [bll.jar:] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_222] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [rt.jar:1.8.0_222] at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383) [javax.enterprise.concurrent-1.0.jar:] at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534) [javax.enterprise.concurrent-1.0.jar:] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_222] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_222] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_222] at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) [javax.enterprise.concurrent-1.0.jar:] Caused by: java.lang.NullPointerException Please take a look. ----- kind regards/met vrindelijke groet Marko Vrgotic ActiveVideo On 10/10/2019, 14:23, "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com> wrote: Hi, I could not check as in the meantime I destroyed my staging setup. Re-provisioning it now and will retest with ansible. On 10/10/2019, 10:51, "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com> wrote: Hi Ondra, That is true, But why does it work from Portal? Image ID is not differ when run when ansible against same template? I will check anyway. On 10/10/2019, 09:47, "Ondra Machacek" <omachace(a)redhat.com> wrote: The error message is: Image does not exist in domain: u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' Can you please check if the image with id 'd680a46a-7188-45f6-b6a7-3333f830c0b4' exists on storage domain with id '935de3ac-a735-4fc8-9161-26bfd751ffc7'? On 08/10/2019 13:05, Vrgotic, Marko wrote: > Dear oVirt, > > Just recently, I have upgraded oVirt staging environment from 4.3.4 to > 4.3.6 release. > > Since then I noticed the issue when creating VMs from template, using > Ansible. When creating VM from template using UI, all works well. > > Tests were executed with same user, with SuperUser priviledges. > > pip freeze > > *ansible==2.7.13* > > asn1crypto==1.0.0 > > bcrypt==3.1.7 > > cffi==1.12.3 > > cryptography==2.7 > > dnspython==1.16.0 > > ipaddress==1.0.22 > > Jinja2==2.10.1 > > lxml==4.4.1 > > MarkupSafe==1.1.1 > > netaddr==0.7.19 > > *ovirt-engine-sdk-python==4.3.3* > > paramiko==2.6.0 > > pycparser==2.19 > > pycurl==7.43.0.3 > > PyNaCl==1.3.0 > > PyYAML==5.1.2 > > six==1.12.0 > > *Logs from engine: * > > 2019-10-08 09:57:42,294Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (default task-23) [067ec489-ae6c-4871-8ab6-8296016ca1ce] Lock Acquired > to object 'EngineLock:{exclusiveLocks='[centos-testvm-024=VM_NAME]', > sharedLocks='[9ac6f4ad-58d0-4a7e-b424-91f2d76abcac=TEMPLATE, > a7e42574-be60-4c94-94a5-cc4b30fdb16f=DISK]'}' > > 2019-10-08 09:57:42,299Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43687) [390b4c75] FINISH, > HSMClearTaskVDSCommand, return: , log id: be932a0 > > 2019-10-08 09:57:42,299Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43687) [390b4c75] FINISH, > SPMClearTaskVDSCommand, return: , log id: 3e25883 > > 2019-10-08 09:57:42,303Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43687) [390b4c75] > BaseAsyncTask::removeTaskFromDB: Removed task > '7e1d68a2-bb49-4456-b228-db851fe6603c' from DataBase > > 2019-10-08 09:57:42,303Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43687) [390b4c75] > CommandAsyncTask::HandleEndActionResult [within thread]: Removing > CommandMultiAsyncTasks object for entity > '4f8a6897-66e8-453b-b706-246cb8505b3e' > > 2019-10-08 09:57:42,375Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (default task-23) [067ec489-ae6c-4871-8ab6-8296016ca1ce] Running > command: AddVmCommand internal: false. Entities affected : ID: > 2e428504-c339-11e9-87ef-00163e3ec101 Type: ClusterAction group CREATE_VM > with role type USER, ID: 9ac6f4ad-58d0-4a7e-b424-91f2d76abcac Type: > VmTemplateAction group CREATE_VM with role type USER, ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: StorageAction group > CREATE_DISK with role type USER > > 2019-10-08 09:57:42,488Z INFO > [org.ovirt.engine.core.bll.AddRngDeviceCommand] (default task-23) > [332c57d4] Running command: AddRngDeviceCommand internal: true. Entities > affected : ID: d5719cf0-2a64-4a28-bbf2-edc1bb05b777 Type: VMAction > group EDIT_VM_PROPERTIES with role type USER > > 2019-10-08 09:57:42,498Z INFO > [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default > task-23) [332c57d4] START, SetVmStatusVDSCommand( > SetVmStatusVDSCommandParameters:{vmId='d5719cf0-2a64-4a28-bbf2-edc1bb05b777', > status='ImageLocked', exitStatus='Normal'}), log id: 2fe004e2 > > 2019-10-08 09:57:42,507Z INFO > [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default > task-23) [332c57d4] FINISH, SetVmStatusVDSCommand, return: , log id: > 2fe004e2 > > 2019-10-08 09:57:42,528Z INFO > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (default task-23) [067ec489-ae6c-4871-8ab6-8296016ca1ce] Running > command: CreateSnapshotFromTemplateCommand internal: true. Entities > affected : ID: 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:57:42,554Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] > (default task-23) [067ec489-ae6c-4871-8ab6-8296016ca1ce] START, > CreateVolumeVDSCommand( > CreateVolumeVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', > imageSizeInBytes='8589934592', volumeFormat='COW', > newImageId='9a96018c-ce7d-4c77-a91a-30fc16c7b2ba', imageType='Sparse', > newImageDescription='', imageInitialSizeInBytes='0', > imageId='f9e0c4d9-81dd-4e44-8a71-33e55d4399c6', > sourceImageGroupId='a7e42574-be60-4c94-94a5-cc4b30fdb16f'}), log id: > 37b29c7d > > 2019-10-08 09:57:42,639Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] > (default task-23) [067ec489-ae6c-4871-8ab6-8296016ca1ce] FINISH, > CreateVolumeVDSCommand, return: 9a96018c-ce7d-4c77-a91a-30fc16c7b2ba, > log id: 37b29c7d > > 2019-10-08 09:57:42,645Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (default task-23) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] CommandAsyncTask::Adding > CommandMultiAsyncTasks object for command > 'f1665b66-2032-4a60-944e-c04beace088e' > > 2019-10-08 09:57:42,645Z INFO > [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (default task-23) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] > CommandMultiAsyncTasks::attachTask: Attaching task > '99abc310-b44b-435c-8d43-922b782a69dc' to command > 'f1665b66-2032-4a60-944e-c04beace088e'. > > 2019-10-08 09:57:42,660Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (default task-23) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Adding task > '99abc310-b44b-435c-8d43-922b782a69dc' (Parent Command > 'CreateSnapshotFromTemplate', Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling > hasn't started yet.. > > 2019-10-08 09:57:42,934Z INFO > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (default task-23) [067ec489-ae6c-4871-8ab6-8296016ca1ce] EVENT_ID: > USER_ADD_VM_STARTED(37), VM centos-testvm-024 creation was initiated by > mteam@internal-authz. > > 2019-10-08 09:57:42,935Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (default task-23) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] BaseAsyncTask::startPollingTask: > Starting to poll task '99abc310-b44b-435c-8d43-922b782a69dc'. > > 2019-10-08 09:57:44,384Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-74) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Command 'AddVm' (id: > '1b65f576-365d-4e8b-a920-621516cbdaed') waiting on child command id: > 'f1665b66-2032-4a60-944e-c04beace088e' type:'CreateSnapshotFromTemplate' > to complete > > 2019-10-08 09:57:48,393Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Command 'AddVm' (id: > '1b65f576-365d-4e8b-a920-621516cbdaed') waiting on child command id: > 'f1665b66-2032-4a60-944e-c04beace088e' type:'CreateSnapshotFromTemplate' > to complete > > 2019-10-08 09:57:48,394Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) [5830ba58] Command > 'AddDisk' id: '937776b8-b94d-4178-b9c2-e39fe42cb06c' child commands > '[63409b0b-749a-45d5-85a5-baf55d5fa2a4]' executions were completed, > status 'SUCCEEDED' > > 2019-10-08 09:57:48,394Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) [5830ba58] Command > 'AddDisk' id: '937776b8-b94d-4178-b9c2-e39fe42cb06c' Updating status to > 'SUCCEEDED', The command end method logic will be executed by one of its > parent commands. > > 2019-10-08 09:57:48,398Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) [5830ba58] Command > 'AddDisk' id: 'fdc5571e-a925-4400-a54a-a1ef1dcd23ae' child commands > '[54d68cae-6585-4351-aaf7-fe687905acf4]' executions were completed, > status 'SUCCEEDED' > > 2019-10-08 09:57:48,398Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) [5830ba58] Command > 'AddDisk' id: 'fdc5571e-a925-4400-a54a-a1ef1dcd23ae' Updating status to > 'SUCCEEDED', The command end method logic will be executed by one of its > parent commands. > > 2019-10-08 09:57:48,401Z INFO > [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) [5830ba58] Command > 'ProcessOvfUpdateForStorageDomain' (id: > 'bdcdae3a-00f6-4176-9d27-0bb0f04912a3') waiting on child command id: > 'b4050edd-62a7-4b83-a4ab-a21c83bf3ade' > type:'CreateOvfVolumeForStorageDomain' to complete > > 2019-10-08 09:57:48,402Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) [5830ba58] Command > 'CreateOvfVolumeForStorageDomain' id: > 'b4050edd-62a7-4b83-a4ab-a21c83bf3ade' child commands > '[937776b8-b94d-4178-b9c2-e39fe42cb06c]' executions were completed, > status 'SUCCEEDED' > > 2019-10-08 09:57:48,404Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-37) [5830ba58] Command > 'CreateOvfVolumeForStorageDomain' id: > '5fd47910-95b2-4387-8e26-ea2c80b078a0' child commands > '[fdc5571e-a925-4400-a54a-a1ef1dcd23ae]' executions were completed, > status 'SUCCEEDED' > > 2019-10-08 09:57:49,416Z INFO > [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [390b4c75] Command > 'ProcessOvfUpdateForStorageDomain' id: > '849bd16c-00d2-48a2-8fde-631af0dfe1b5' child commands > '[a80a3657-c813-42c1-a43d-27442b5dc238, > 4f8a6897-66e8-453b-b706-246cb8505b3e]' executions were completed, status > 'SUCCEEDED' > > 2019-10-08 09:57:49,418Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.CreateOvfVolumeForStorageDomainCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] Ending > command > 'org.ovirt.engine.core.bll.storage.ovfstore.CreateOvfVolumeForStorageDomainCommand' > successfully. > > 2019-10-08 09:57:49,420Z INFO > [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] Ending > command 'org.ovirt.engine.core.bll.storage.disk.AddDiskCommand' > successfully. > > 2019-10-08 09:57:49,426Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-3) > [5830ba58] Ending command > 'org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand' successfully. > > 2019-10-08 09:57:49,427Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] START, > GetImageInfoVDSCommand( > GetImageInfoVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='66984468-bbfa-4941-8c6b-df72a6d920f2', > imageId='7db55211-041a-40c8-85a6-a2ff1bd182ce'}), log id: 6c02a73c > > 2019-10-08 09:57:49,429Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] START, > GetVolumeInfoVDSCommand(HostName = ovirt-staging-hv-01.avinity.tv, > GetVolumeInfoVDSCommandParameters:{hostId='bfc4c379-bd5f-45be-98a4-f0469dc3817c', > storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='66984468-bbfa-4941-8c6b-df72a6d920f2', > imageId='7db55211-041a-40c8-85a6-a2ff1bd182ce'}), log id: 2e131d9d > > 2019-10-08 09:57:49,456Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] FINISH, > GetVolumeInfoVDSCommand, return: > org.ovirt.engine.core.common.businessentities.storage.DiskImage@26992dd0, log > id: 2e131d9d > > 2019-10-08 09:57:49,456Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] FINISH, > GetImageInfoVDSCommand, return: > org.ovirt.engine.core.common.businessentities.storage.DiskImage@26992dd0, log > id: 6c02a73c > > 2019-10-08 09:57:49,464Z WARN > [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [] VM is null - no > unlocking > > 2019-10-08 09:57:49,481Z INFO > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [] EVENT_ID: > USER_ADD_DISK_FINISHED_SUCCESS(2,021), The disk 'OVF_STORE' was > successfully added. > > 2019-10-08 09:57:49,490Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.CreateOvfVolumeForStorageDomainCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] Ending > command > 'org.ovirt.engine.core.bll.storage.ovfstore.CreateOvfVolumeForStorageDomainCommand' > successfully. > > 2019-10-08 09:57:49,491Z INFO > [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] Ending > command 'org.ovirt.engine.core.bll.storage.disk.AddDiskCommand' > successfully. > > 2019-10-08 09:57:49,495Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-3) > [5830ba58] Ending command > 'org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand' successfully. > > 2019-10-08 09:57:49,497Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] START, > GetImageInfoVDSCommand( > GetImageInfoVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='ee208fd3-e05c-4ba8-aba9-fa521d69a870', > imageId='484c1eed-b03a-4fa0-a12d-0087294dec86'}), log id: 7a3dad31 > > 2019-10-08 09:57:49,498Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] START, > GetVolumeInfoVDSCommand(HostName = ovirt-staging-hv-01.avinity.tv, > GetVolumeInfoVDSCommandParameters:{hostId='bfc4c379-bd5f-45be-98a4-f0469dc3817c', > storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='ee208fd3-e05c-4ba8-aba9-fa521d69a870', > imageId='484c1eed-b03a-4fa0-a12d-0087294dec86'}), log id: 5b85c4a5 > > 2019-10-08 09:57:49,522Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] FINISH, > GetVolumeInfoVDSCommand, return: > org.ovirt.engine.core.common.businessentities.storage.DiskImage@13555e4, > log id: 5b85c4a5 > > 2019-10-08 09:57:49,522Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [5830ba58] FINISH, > GetImageInfoVDSCommand, return: > org.ovirt.engine.core.common.businessentities.storage.DiskImage@13555e4, > log id: 7a3dad31 > > 2019-10-08 09:57:49,529Z WARN > [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [] VM is null - no > unlocking > > 2019-10-08 09:57:49,540Z INFO > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-3) [] EVENT_ID: > USER_ADD_DISK_FINISHED_SUCCESS(2,021), The disk 'OVF_STORE' was > successfully added. > > 2019-10-08 09:57:50,552Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [390b4c75] Ending > command > 'org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand' > successfully. > > 2019-10-08 09:57:50,575Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] START, > SetVolumeDescriptionVDSCommand( > SetVolumeDescriptionVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='ee208fd3-e05c-4ba8-aba9-fa521d69a870', > imageId='484c1eed-b03a-4fa0-a12d-0087294dec86'}), log id: 7e77a9a8 > > 2019-10-08 09:57:50,576Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] -- > executeIrsBrokerCommand: calling 'setVolumeDescription', parameters: > > 2019-10-08 09:57:50,576Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > spUUID=2e3b3484-c339-11e9-8d02-00163e3ec101 > > 2019-10-08 09:57:50,576Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > sdUUID=935de3ac-a735-4fc8-9161-26bfd751ffc7 > > 2019-10-08 09:57:50,576Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > imageGroupGUID=ee208fd3-e05c-4ba8-aba9-fa521d69a870 > > 2019-10-08 09:57:50,576Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > volUUID=484c1eed-b03a-4fa0-a12d-0087294dec86 > > 2019-10-08 09:57:50,576Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > description={"Updated":false,"Last Updated":null,"Storage > Domains":[{"uuid":"935de3ac-a735-4fc8-9161-26bfd751ffc7"}],"Disk > Description":"OVF_STORE"} > > 2019-10-08 09:57:50,606Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] FINISH, > SetVolumeDescriptionVDSCommand, return: , log id: 7e77a9a8 > > 2019-10-08 09:57:50,614Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Lock > Acquired to object 'EngineLock:{exclusiveLocks='', > sharedLocks='[bfc4c379-bd5f-45be-98a4-f0469dc3817c=VDS_EXECUTION]'}' > > 2019-10-08 09:57:50,623Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Running > command: UploadStreamCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:57:50,624Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] START, > UploadStreamVDSCommand(HostName = ovirt-staging-hv-01.avinity.tv, > UploadStreamVDSCommandParameters:{hostId='bfc4c379-bd5f-45be-98a4-f0469dc3817c'}), > log id: 531a4a4a > > 2019-10-08 09:57:50,625Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] -- > executeVdsBrokerCommand, parameters: > > 2019-10-08 09:57:50,625Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > spUUID=2e3b3484-c339-11e9-8d02-00163e3ec101 > > 2019-10-08 09:57:50,625Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > sdUUID=935de3ac-a735-4fc8-9161-26bfd751ffc7 > > 2019-10-08 09:57:50,625Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > imageGUID=ee208fd3-e05c-4ba8-aba9-fa521d69a870 > > 2019-10-08 09:57:50,625Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > volUUID=484c1eed-b03a-4fa0-a12d-0087294dec86 > > 2019-10-08 09:57:50,625Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ size=30720 > > 2019-10-08 09:57:51,331Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] FINISH, > UploadStreamVDSCommand, return: , log id: 531a4a4a > > 2019-10-08 09:57:51,342Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] > CommandAsyncTask::Adding CommandMultiAsyncTasks object for command > 'c11f4d3c-f85b-43c5-986f-a517aed66d7e' > > 2019-10-08 09:57:51,342Z INFO > [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] > CommandMultiAsyncTasks::attachTask: Attaching task > 'e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d' to command > 'c11f4d3c-f85b-43c5-986f-a517aed66d7e'. > > 2019-10-08 09:57:51,351Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Adding > task 'e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d' (Parent Command > 'UploadStream', Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling > hasn't started yet.. > > 2019-10-08 09:57:51,355Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] > BaseAsyncTask::startPollingTask: Starting to poll task > 'e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d'. > > 2019-10-08 09:57:51,358Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Lock freed > to object 'EngineLock:{exclusiveLocks='', > sharedLocks='[bfc4c379-bd5f-45be-98a4-f0469dc3817c=VDS_EXECUTION]'}' > > 2019-10-08 09:57:51,360Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] START, > SetVolumeDescriptionVDSCommand( > SetVolumeDescriptionVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='ee208fd3-e05c-4ba8-aba9-fa521d69a870', > imageId='484c1eed-b03a-4fa0-a12d-0087294dec86'}), log id: 238169f6 > > 2019-10-08 09:57:51,360Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] -- > executeIrsBrokerCommand: calling 'setVolumeDescription', parameters: > > 2019-10-08 09:57:51,360Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > spUUID=2e3b3484-c339-11e9-8d02-00163e3ec101 > > 2019-10-08 09:57:51,360Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > sdUUID=935de3ac-a735-4fc8-9161-26bfd751ffc7 > > 2019-10-08 09:57:51,360Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > imageGroupGUID=ee208fd3-e05c-4ba8-aba9-fa521d69a870 > > 2019-10-08 09:57:51,360Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > volUUID=484c1eed-b03a-4fa0-a12d-0087294dec86 > > 2019-10-08 09:57:51,360Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > description={"Updated":true,"Size":30720,"Last Updated":"Tue Oct 08 > 09:57:50 UTC 2019","Storage > Domains":[{"uuid":"935de3ac-a735-4fc8-9161-26bfd751ffc7"}],"Disk > Description":"OVF_STORE"} > > 2019-10-08 09:57:51,389Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] FINISH, > SetVolumeDescriptionVDSCommand, return: , log id: 238169f6 > > 2019-10-08 09:57:51,596Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] START, > SetVolumeDescriptionVDSCommand( > SetVolumeDescriptionVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='66984468-bbfa-4941-8c6b-df72a6d920f2', > imageId='7db55211-041a-40c8-85a6-a2ff1bd182ce'}), log id: 59bde70f > > 2019-10-08 09:57:51,627Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] -- > executeIrsBrokerCommand: calling 'setVolumeDescription', parameters: > > 2019-10-08 09:57:51,627Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > spUUID=2e3b3484-c339-11e9-8d02-00163e3ec101 > > 2019-10-08 09:57:51,627Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > sdUUID=935de3ac-a735-4fc8-9161-26bfd751ffc7 > > 2019-10-08 09:57:51,627Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > imageGroupGUID=66984468-bbfa-4941-8c6b-df72a6d920f2 > > 2019-10-08 09:57:51,627Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > volUUID=7db55211-041a-40c8-85a6-a2ff1bd182ce > > 2019-10-08 09:57:51,627Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > description={"Updated":false,"Last Updated":null,"Storage > Domains":[{"uuid":"935de3ac-a735-4fc8-9161-26bfd751ffc7"}],"Disk > Description":"OVF_STORE"} > > 2019-10-08 09:57:51,664Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] FINISH, > SetVolumeDescriptionVDSCommand, return: , log id: 59bde70f > > 2019-10-08 09:57:51,672Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Lock > Acquired to object 'EngineLock:{exclusiveLocks='', > sharedLocks='[bfc4c379-bd5f-45be-98a4-f0469dc3817c=VDS_EXECUTION]'}' > > 2019-10-08 09:57:51,683Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Running > command: UploadStreamCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:57:51,684Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] START, > UploadStreamVDSCommand(HostName = ovirt-staging-hv-01.avinity.tv, > UploadStreamVDSCommandParameters:{hostId='bfc4c379-bd5f-45be-98a4-f0469dc3817c'}), > log id: 1cb812b6 > > 2019-10-08 09:57:51,684Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] -- > executeVdsBrokerCommand, parameters: > > 2019-10-08 09:57:51,684Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > spUUID=2e3b3484-c339-11e9-8d02-00163e3ec101 > > 2019-10-08 09:57:51,684Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > sdUUID=935de3ac-a735-4fc8-9161-26bfd751ffc7 > > 2019-10-08 09:57:51,684Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > imageGUID=66984468-bbfa-4941-8c6b-df72a6d920f2 > > 2019-10-08 09:57:51,684Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > volUUID=7db55211-041a-40c8-85a6-a2ff1bd182ce > > 2019-10-08 09:57:51,684Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ size=30720 > > 2019-10-08 09:57:51,933Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UploadStreamVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] FINISH, > UploadStreamVDSCommand, return: , log id: 1cb812b6 > > 2019-10-08 09:57:51,943Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] > CommandAsyncTask::Adding CommandMultiAsyncTasks object for command > 'd0c07988-0e43-4e6d-b86c-e736b28d4537' > > 2019-10-08 09:57:51,943Z INFO > [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] > CommandMultiAsyncTasks::attachTask: Attaching task > 'ba88edd0-8188-472e-8f59-aa3f90e63181' to command > 'd0c07988-0e43-4e6d-b86c-e736b28d4537'. > > 2019-10-08 09:57:51,952Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Adding > task 'ba88edd0-8188-472e-8f59-aa3f90e63181' (Parent Command > 'UploadStream', Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling > hasn't started yet.. > > 2019-10-08 09:57:51,958Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] > BaseAsyncTask::startPollingTask: Starting to poll task > 'ba88edd0-8188-472e-8f59-aa3f90e63181'. > > 2019-10-08 09:57:51,961Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] Lock freed > to object 'EngineLock:{exclusiveLocks='', > sharedLocks='[bfc4c379-bd5f-45be-98a4-f0469dc3817c=VDS_EXECUTION]'}' > > 2019-10-08 09:57:51,962Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] START, > SetVolumeDescriptionVDSCommand( > SetVolumeDescriptionVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='66984468-bbfa-4941-8c6b-df72a6d920f2', > imageId='7db55211-041a-40c8-85a6-a2ff1bd182ce'}), log id: 213b3075 > > 2019-10-08 09:57:51,962Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] -- > executeIrsBrokerCommand: calling 'setVolumeDescription', parameters: > > 2019-10-08 09:57:51,962Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > spUUID=2e3b3484-c339-11e9-8d02-00163e3ec101 > > 2019-10-08 09:57:51,962Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > sdUUID=935de3ac-a735-4fc8-9161-26bfd751ffc7 > > 2019-10-08 09:57:51,962Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > imageGroupGUID=66984468-bbfa-4941-8c6b-df72a6d920f2 > > 2019-10-08 09:57:51,962Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > volUUID=7db55211-041a-40c8-85a6-a2ff1bd182ce > > 2019-10-08 09:57:51,962Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] ++ > description={"Updated":true,"Size":30720,"Last Updated":"Tue Oct 08 > 09:57:50 UTC 2019","Storage > Domains":[{"uuid":"935de3ac-a735-4fc8-9161-26bfd751ffc7"}],"Disk > Description":"OVF_STORE"} > > 2019-10-08 09:57:52,028Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-1) [5830ba58] FINISH, > SetVolumeDescriptionVDSCommand, return: , log id: 213b3075 > > 2019-10-08 09:57:52,224Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] Polling and > updating Async Tasks: 7 tasks, 3 tasks to poll now > > 2019-10-08 09:57:52,228Z ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksStatusesVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] Failed in > 'HSMGetAllTasksStatusesVDS' method > > 2019-10-08 09:57:52,235Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] EVENT_ID: > VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt-staging-hv-01.avinity.tv > command HSMGetAllTasksStatusesVDS failed: Invalid parameter: 'size=16777216' > > 2019-10-08 09:57:52,235Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > SPMAsyncTask::PollTask: Polling task > '99abc310-b44b-435c-8d43-922b782a69dc' (Parent Command > 'CreateSnapshotFromTemplate', Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned > status 'finished', result 'cleanSuccess'. > > 2019-10-08 09:57:52,240Z ERROR > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > BaseAsyncTask::logEndTaskFailure: Task > '99abc310-b44b-435c-8d43-922b782a69dc' (Parent Command > 'CreateSnapshotFromTemplate', Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended > with failure: > > -- Result: 'cleanSuccess' > > -- Message: 'VDSGenericException: VDSErrorException: Failed to > HSMGetAllTasksStatusesVDS, error = Invalid parameter: 'size=16777216', > code = 100', > > -- Exception: 'VDSGenericException: VDSErrorException: Failed to > HSMGetAllTasksStatusesVDS, error = Invalid parameter: 'size=16777216', > code = 100' > > 2019-10-08 09:57:52,241Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > CommandAsyncTask::endActionIfNecessary: All tasks of command > 'f1665b66-2032-4a60-944e-c04beace088e' has ended -> executing 'endAction' > > 2019-10-08 09:57:52,241Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: > 'f1665b66-2032-4a60-944e-c04beace088e'): calling endAction '. > > 2019-10-08 09:57:52,241Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > SPMAsyncTask::PollTask: Polling task > 'e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d' (Parent Command 'UploadStream', > Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned > status 'finished', result 'success'. > > 2019-10-08 09:57:52,241Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > BaseAsyncTask::onTaskEndSuccess: Task > 'e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d' (Parent Command 'UploadStream', > Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended > successfully. > > 2019-10-08 09:57:52,241Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43693) [] > CommandAsyncTask::endCommandAction [within thread] context: Attempting > to endAction 'CreateSnapshotFromTemplate', > > 2019-10-08 09:57:52,242Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > CommandAsyncTask::endActionIfNecessary: All tasks of command > 'c11f4d3c-f85b-43c5-986f-a517aed66d7e' has ended -> executing 'endAction' > > 2019-10-08 09:57:52,243Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: > 'c11f4d3c-f85b-43c5-986f-a517aed66d7e'): calling endAction '. > > 2019-10-08 09:57:52,243Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > SPMAsyncTask::PollTask: Polling task > 'ba88edd0-8188-472e-8f59-aa3f90e63181' (Parent Command 'UploadStream', > Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned > status 'finished', result 'success'. > > 2019-10-08 09:57:52,243Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > BaseAsyncTask::onTaskEndSuccess: Task > 'ba88edd0-8188-472e-8f59-aa3f90e63181' (Parent Command 'UploadStream', > Parameters Type > 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended > successfully. > > 2019-10-08 09:57:52,243Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43694) [] > CommandAsyncTask::endCommandAction [within thread] context: Attempting > to endAction 'UploadStream', > > 2019-10-08 09:57:52,244Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > CommandAsyncTask::endActionIfNecessary: All tasks of command > 'd0c07988-0e43-4e6d-b86c-e736b28d4537' has ended -> executing 'endAction' > > 2019-10-08 09:57:52,244Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engineScheduled-Thread-91) [] > CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: > 'd0c07988-0e43-4e6d-b86c-e736b28d4537'): calling endAction '. > > 2019-10-08 09:57:52,245Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43695) [] > CommandAsyncTask::endCommandAction [within thread] context: Attempting > to endAction 'UploadStream', > > 2019-10-08 09:57:52,245Z INFO > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Command > [id=f1665b66-2032-4a60-944e-c04beace088e]: Updating status to 'FAILED', > The command end method logic will be executed by one of its parent commands. > > 2019-10-08 09:57:52,247Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] > CommandAsyncTask::HandleEndActionResult [within thread]: endAction for > action type 'CreateSnapshotFromTemplate' completed, handling the result. > > 2019-10-08 09:57:52,247Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] > CommandAsyncTask::HandleEndActionResult [within thread]: endAction for > action type 'CreateSnapshotFromTemplate' succeeded, clearing tasks. > > 2019-10-08 09:57:52,247Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] SPMAsyncTask::ClearAsyncTask: > Attempting to clear task '99abc310-b44b-435c-8d43-922b782a69dc' > > 2019-10-08 09:57:52,247Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] Ending command > 'org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand' > successfully. > > 2019-10-08 09:57:52,247Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] Ending command > 'org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommand' > successfully. > > 2019-10-08 09:57:52,247Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] START, SPMClearTaskVDSCommand( > SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > taskId='99abc310-b44b-435c-8d43-922b782a69dc'}), log id: 66a4e67 > > 2019-10-08 09:57:52,247Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] START, > HSMClearTaskVDSCommand(HostName = ovirt-staging-hv-01.avinity.tv, > HSMTaskGuidBaseVDSCommandParameters:{hostId='bfc4c379-bd5f-45be-98a4-f0469dc3817c', > taskId='99abc310-b44b-435c-8d43-922b782a69dc'}), log id: 7ec6d8b8 > > 2019-10-08 09:57:52,249Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] > CommandAsyncTask::HandleEndActionResult [within thread]: endAction for > action type 'UploadStream' completed, handling the result. > > 2019-10-08 09:57:52,249Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] > CommandAsyncTask::HandleEndActionResult [within thread]: endAction for > action type 'UploadStream' succeeded, clearing tasks. > > 2019-10-08 09:57:52,249Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] > SPMAsyncTask::ClearAsyncTask: Attempting to clear task > 'e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d' > > 2019-10-08 09:57:52,249Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] START, > SPMClearTaskVDSCommand( > SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > taskId='e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d'}), log id: 356927d > > 2019-10-08 09:57:52,250Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] > CommandAsyncTask::HandleEndActionResult [within thread]: endAction for > action type 'UploadStream' completed, handling the result. > > 2019-10-08 09:57:52,250Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] > CommandAsyncTask::HandleEndActionResult [within thread]: endAction for > action type 'UploadStream' succeeded, clearing tasks. > > 2019-10-08 09:57:52,250Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] > SPMAsyncTask::ClearAsyncTask: Attempting to clear task > 'ba88edd0-8188-472e-8f59-aa3f90e63181' > > 2019-10-08 09:57:52,251Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] START, > SPMClearTaskVDSCommand( > SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > taskId='ba88edd0-8188-472e-8f59-aa3f90e63181'}), log id: 75844e34 > > 2019-10-08 09:57:52,259Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] FINISH, HSMClearTaskVDSCommand, > return: , log id: 7ec6d8b8 > > 2019-10-08 09:57:52,259Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] FINISH, SPMClearTaskVDSCommand, > return: , log id: 66a4e67 > > 2019-10-08 09:57:52,260Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] START, > HSMClearTaskVDSCommand(HostName = ovirt-staging-hv-01.avinity.tv, > HSMTaskGuidBaseVDSCommandParameters:{hostId='bfc4c379-bd5f-45be-98a4-f0469dc3817c', > taskId='e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d'}), log id: 3b239769 > > 2019-10-08 09:57:52,263Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] BaseAsyncTask::removeTaskFromDB: > Removed task '99abc310-b44b-435c-8d43-922b782a69dc' from DataBase > > 2019-10-08 09:57:52,263Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43693) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] > CommandAsyncTask::HandleEndActionResult [within thread]: Removing > CommandMultiAsyncTasks object for entity > 'f1665b66-2032-4a60-944e-c04beace088e' > > 2019-10-08 09:57:52,297Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] FINISH, > HSMClearTaskVDSCommand, return: , log id: 3b239769 > > 2019-10-08 09:57:52,297Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] FINISH, > SPMClearTaskVDSCommand, return: , log id: 356927d > > 2019-10-08 09:57:52,298Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] START, > HSMClearTaskVDSCommand(HostName = ovirt-staging-hv-01.avinity.tv, > HSMTaskGuidBaseVDSCommandParameters:{hostId='bfc4c379-bd5f-45be-98a4-f0469dc3817c', > taskId='ba88edd0-8188-472e-8f59-aa3f90e63181'}), log id: 32d44e1 > > 2019-10-08 09:57:52,301Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] > BaseAsyncTask::removeTaskFromDB: Removed task > 'e5d00ff5-eaa2-48e9-ab10-d6d06a01e89d' from DataBase > > 2019-10-08 09:57:52,301Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43694) [5830ba58] > CommandAsyncTask::HandleEndActionResult [within thread]: Removing > CommandMultiAsyncTasks object for entity > 'c11f4d3c-f85b-43c5-986f-a517aed66d7e' > > 2019-10-08 09:57:52,314Z INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] FINISH, > HSMClearTaskVDSCommand, return: , log id: 32d44e1 > > 2019-10-08 09:57:52,314Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] FINISH, > SPMClearTaskVDSCommand, return: , log id: 75844e34 > > 2019-10-08 09:57:52,317Z INFO > [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] > BaseAsyncTask::removeTaskFromDB: Removed task > 'ba88edd0-8188-472e-8f59-aa3f90e63181' from DataBase > > 2019-10-08 09:57:52,317Z INFO > [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] > (EE-ManagedThreadFactory-engine-Thread-43695) [5830ba58] > CommandAsyncTask::HandleEndActionResult [within thread]: Removing > CommandMultiAsyncTasks object for entity > 'd0c07988-0e43-4e6d-b86c-e736b28d4537' > > 2019-10-08 09:57:54,039Z INFO > [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-44) [5830ba58] Command > 'ProcessOvfUpdateForStorageDomain' id: > 'bdcdae3a-00f6-4176-9d27-0bb0f04912a3' child commands > '[b4050edd-62a7-4b83-a4ab-a21c83bf3ade, > 5fd47910-95b2-4387-8e26-ea2c80b078a0, > c11f4d3c-f85b-43c5-986f-a517aed66d7e, > d0c07988-0e43-4e6d-b86c-e736b28d4537]' executions were completed, status > 'SUCCEEDED' > > 2019-10-08 09:57:55,046Z INFO > [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-40) [5830ba58] Ending > command > 'org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand' > successfully. > > 2019-10-08 09:57:58,077Z INFO > [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] > (EE-ManagedThreadFactory-engineScheduled-Thread-76) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Command 'AddVm' id: > '1b65f576-365d-4e8b-a920-621516cbdaed' child commands > '[f1665b66-2032-4a60-944e-c04beace088e]' executions were completed, > status 'FAILED' > > 2019-10-08 09:57:59,094Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.AddVmCommand' with failure. > > 2019-10-08 09:57:59,099Z ERROR > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' > with failure. > > 2019-10-08 09:57:59,104Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [5794ed92] Running > command: RemoveImageCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:57:59,126Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [5794ed92] START, > DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'}), log id: 69861a78 > > 2019-10-08 09:57:59,139Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [5794ed92] EVENT_ID: > IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS > failed: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:57:59,139Z ERROR > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [5794ed92] Command > 'DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'})' execution failed: > IRSGenericException: IRSErrorException: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:57:59,139Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [5794ed92] FINISH, > DeleteImageGroupVDSCommand, return: , log id: 69861a78 > > 2019-10-08 09:57:59,139Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [5794ed92] Disk > 'd680a46a-7188-45f6-b6a7-3333f830c0b4' doesn't exist on storage domain > '935de3ac-a735-4fc8-9161-26bfd751ffc7', rolling forward > > 2019-10-08 09:57:59,149Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [5794ed92] Removed > task 'b4c4c723-4ba1-4d5a-86e6-24658a293a04' from DataBase > > 2019-10-08 09:57:59,220Z INFO > [org.ovirt.engine.core.utils.transaction.TransactionSupport] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [] transaction > rolled back > > 2019-10-08 09:57:59,220Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [] Lock freed to > object 'EngineLock:{exclusiveLocks='[centos-testvm-024=VM_NAME]', > sharedLocks='[9ac6f4ad-58d0-4a7e-b424-91f2d76abcac=TEMPLATE, > a7e42574-be60-4c94-94a5-cc4b30fdb16f=DISK]'}' > > 2019-10-08 09:57:59,233Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [] EVENT_ID: > USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM > centos-testvm-024 creation. > > 2019-10-08 09:57:59,233Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-27) [] Failed invoking > callback end method 'onFailed' for command > '1b65f576-365d-4e8b-a920-621516cbdaed' with exception 'null', the > callback is marked for end method retries > > 2019-10-08 09:58:01,252Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.AddVmCommand' with failure. > > 2019-10-08 09:58:01,257Z ERROR > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' > with failure. > > 2019-10-08 09:58:01,270Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [19251787] Running > command: RemoveImageCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:58:01,308Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [19251787] START, > DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'}), log id: 35fec55 > > 2019-10-08 09:58:01,324Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [19251787] EVENT_ID: > IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS > failed: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:01,324Z ERROR > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [19251787] Command > 'DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'})' execution failed: > IRSGenericException: IRSErrorException: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:01,324Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [19251787] FINISH, > DeleteImageGroupVDSCommand, return: , log id: 35fec55 > > 2019-10-08 09:58:01,324Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [19251787] Disk > 'd680a46a-7188-45f6-b6a7-3333f830c0b4' doesn't exist on storage domain > '935de3ac-a735-4fc8-9161-26bfd751ffc7', rolling forward > > 2019-10-08 09:58:01,335Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [19251787] Removed > task '6ed0a844-5363-4afd-bffc-a80b6ace69ea' from DataBase > > 2019-10-08 09:58:01,395Z INFO > [org.ovirt.engine.core.utils.transaction.TransactionSupport] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] transaction > rolled back > > 2019-10-08 09:58:01,395Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] Trying to release > a shared lock for key: '9ac6f4ad-58d0-4a7e-b424-91f2d76abcacTEMPLATE' , > but lock does not exist > > 2019-10-08 09:58:01,395Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] Trying to release > a shared lock for key: 'a7e42574-be60-4c94-94a5-cc4b30fdb16fDISK' , but > lock does not exist > > 2019-10-08 09:58:01,395Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] Trying to release > exclusive lock which does not exist, lock key: 'centos-testvm-024VM_NAME' > > 2019-10-08 09:58:01,395Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] Lock freed to > object 'EngineLock:{exclusiveLocks='[centos-testvm-024=VM_NAME]', > sharedLocks='[9ac6f4ad-58d0-4a7e-b424-91f2d76abcac=TEMPLATE, > a7e42574-be60-4c94-94a5-cc4b30fdb16f=DISK]'}' > > 2019-10-08 09:58:01,407Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] EVENT_ID: > USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM > centos-testvm-024 creation. > > 2019-10-08 09:58:01,407Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] Failed invoking > callback end method 'onFailed' for command > '1b65f576-365d-4e8b-a920-621516cbdaed' with exception 'null', the > callback is marked for end method retries > > 2019-10-08 09:58:05,427Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.AddVmCommand' with failure. > > 2019-10-08 09:58:05,430Z ERROR > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' > with failure. > > 2019-10-08 09:58:05,437Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [cf91364] Running > command: RemoveImageCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:58:05,452Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [cf91364] START, > DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'}), log id: 6ac726b6 > > 2019-10-08 09:58:05,466Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [cf91364] EVENT_ID: > IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS > failed: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:05,466Z ERROR > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [cf91364] Command > 'DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'})' execution failed: > IRSGenericException: IRSErrorException: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:05,466Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [cf91364] FINISH, > DeleteImageGroupVDSCommand, return: , log id: 6ac726b6 > > 2019-10-08 09:58:05,467Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [cf91364] Disk > 'd680a46a-7188-45f6-b6a7-3333f830c0b4' doesn't exist on storage domain > '935de3ac-a735-4fc8-9161-26bfd751ffc7', rolling forward > > 2019-10-08 09:58:05,477Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [cf91364] Removed > task '31bd7a11-203d-4459-ac54-3c398c85771d' from DataBase > > 2019-10-08 09:58:05,490Z INFO > [org.ovirt.engine.core.utils.transaction.TransactionSupport] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] transaction > rolled back > > 2019-10-08 09:58:05,490Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] Trying to release > a shared lock for key: '9ac6f4ad-58d0-4a7e-b424-91f2d76abcacTEMPLATE' , > but lock does not exist > > 2019-10-08 09:58:05,490Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] Trying to release > a shared lock for key: 'a7e42574-be60-4c94-94a5-cc4b30fdb16fDISK' , but > lock does not exist > > 2019-10-08 09:58:05,490Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] Trying to release > exclusive lock which does not exist, lock key: 'centos-testvm-024VM_NAME' > > 2019-10-08 09:58:05,490Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] Lock freed to > object 'EngineLock:{exclusiveLocks='[centos-testvm-024=VM_NAME]', > sharedLocks='[9ac6f4ad-58d0-4a7e-b424-91f2d76abcac=TEMPLATE, > a7e42574-be60-4c94-94a5-cc4b30fdb16f=DISK]'}' > > 2019-10-08 09:58:05,503Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] EVENT_ID: > USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM > centos-testvm-024 creation. > > 2019-10-08 09:58:05,503Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-17) [] Failed invoking > callback end method 'onFailed' for command > '1b65f576-365d-4e8b-a920-621516cbdaed' with exception 'null', the > callback is marked for end method retries > > 2019-10-08 09:58:13,523Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.AddVmCommand' with failure. > > 2019-10-08 09:58:13,527Z ERROR > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' > with failure. > > 2019-10-08 09:58:13,533Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [56103b5a] Running > command: RemoveImageCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:58:13,548Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [56103b5a] START, > DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'}), log id: 33164673 > > 2019-10-08 09:58:13,560Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [56103b5a] EVENT_ID: > IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS > failed: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:13,560Z ERROR > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [56103b5a] Command > 'DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'})' execution failed: > IRSGenericException: IRSErrorException: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:13,560Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [56103b5a] FINISH, > DeleteImageGroupVDSCommand, return: , log id: 33164673 > > 2019-10-08 09:58:13,560Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [56103b5a] Disk > 'd680a46a-7188-45f6-b6a7-3333f830c0b4' doesn't exist on storage domain > '935de3ac-a735-4fc8-9161-26bfd751ffc7', rolling forward > > 2019-10-08 09:58:13,570Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [56103b5a] Removed > task 'ce6882de-2d89-4298-bdcf-86d621a54084' from DataBase > > 2019-10-08 09:58:13,583Z INFO > [org.ovirt.engine.core.utils.transaction.TransactionSupport] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] transaction > rolled back > > 2019-10-08 09:58:13,583Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] Trying to release > a shared lock for key: '9ac6f4ad-58d0-4a7e-b424-91f2d76abcacTEMPLATE' , > but lock does not exist > > 2019-10-08 09:58:13,583Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] Trying to release > a shared lock for key: 'a7e42574-be60-4c94-94a5-cc4b30fdb16fDISK' , but > lock does not exist > > 2019-10-08 09:58:13,583Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] Trying to release > exclusive lock which does not exist, lock key: 'centos-testvm-024VM_NAME' > > 2019-10-08 09:58:13,583Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] Lock freed to > object 'EngineLock:{exclusiveLocks='[centos-testvm-024=VM_NAME]', > sharedLocks='[9ac6f4ad-58d0-4a7e-b424-91f2d76abcac=TEMPLATE, > a7e42574-be60-4c94-94a5-cc4b30fdb16f=DISK]'}' > > 2019-10-08 09:58:13,595Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] EVENT_ID: > USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM > centos-testvm-024 creation. > > 2019-10-08 09:58:13,595Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-35) [] Failed invoking > callback end method 'onFailed' for command > '1b65f576-365d-4e8b-a920-621516cbdaed' with exception 'null', the > callback is marked for end method retries > > 2019-10-08 09:58:23,616Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.AddVmCommand' with failure. > > 2019-10-08 09:58:23,620Z ERROR > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' > with failure. > > 2019-10-08 09:58:23,627Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [48f2f9bd] Running > command: RemoveImageCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:58:23,642Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [48f2f9bd] START, > DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'}), log id: 7346a5bd > > 2019-10-08 09:58:23,663Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [48f2f9bd] EVENT_ID: > IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS > failed: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:23,663Z ERROR > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [48f2f9bd] Command > 'DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'})' execution failed: > IRSGenericException: IRSErrorException: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:23,663Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [48f2f9bd] FINISH, > DeleteImageGroupVDSCommand, return: , log id: 7346a5bd > > 2019-10-08 09:58:23,663Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [48f2f9bd] Disk > 'd680a46a-7188-45f6-b6a7-3333f830c0b4' doesn't exist on storage domain > '935de3ac-a735-4fc8-9161-26bfd751ffc7', rolling forward > > 2019-10-08 09:58:23,682Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [48f2f9bd] Removed > task '8483357d-6d4f-418e-9751-70fcb69685cb' from DataBase > > 2019-10-08 09:58:23,695Z INFO > [org.ovirt.engine.core.utils.transaction.TransactionSupport] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] transaction > rolled back > > 2019-10-08 09:58:23,695Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] Trying to release > a shared lock for key: '9ac6f4ad-58d0-4a7e-b424-91f2d76abcacTEMPLATE' , > but lock does not exist > > 2019-10-08 09:58:23,695Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] Trying to release > a shared lock for key: 'a7e42574-be60-4c94-94a5-cc4b30fdb16fDISK' , but > lock does not exist > > 2019-10-08 09:58:23,695Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] Trying to release > exclusive lock which does not exist, lock key: 'centos-testvm-024VM_NAME' > > 2019-10-08 09:58:23,695Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] Lock freed to > object 'EngineLock:{exclusiveLocks='[centos-testvm-024=VM_NAME]', > sharedLocks='[9ac6f4ad-58d0-4a7e-b424-91f2d76abcac=TEMPLATE, > a7e42574-be60-4c94-94a5-cc4b30fdb16f=DISK]'}' > > 2019-10-08 09:58:23,706Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] EVENT_ID: > USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM > centos-testvm-024 creation. > > 2019-10-08 09:58:23,706Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-71) [] Failed invoking > callback end method 'onFailed' for command > '1b65f576-365d-4e8b-a920-621516cbdaed' with exception 'null', the > callback is marked for end method retries > > 2019-10-08 09:58:33,725Z ERROR [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.AddVmCommand' with failure. > > 2019-10-08 09:58:33,729Z ERROR > [org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Ending command > 'org.ovirt.engine.core.bll.snapshots.CreateSnapshotFromTemplateCommand' > with failure. > > 2019-10-08 09:58:33,736Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [3eea0406] Running > command: RemoveImageCommand internal: true. Entities affected : ID: > 935de3ac-a735-4fc8-9161-26bfd751ffc7 Type: Storage > > 2019-10-08 09:58:33,752Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [3eea0406] START, > DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'}), log id: 6d120001 > > 2019-10-08 09:58:33,767Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [3eea0406] EVENT_ID: > IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS > failed: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:33,767Z ERROR > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [3eea0406] Command > 'DeleteImageGroupVDSCommand( > DeleteImageGroupVDSCommandParameters:{storagePoolId='2e3b3484-c339-11e9-8d02-00163e3ec101', > ignoreFailoverLimit='false', > storageDomainId='935de3ac-a735-4fc8-9161-26bfd751ffc7', > imageGroupId='d680a46a-7188-45f6-b6a7-3333f830c0b4', postZeros='false', > discard='false', forceDelete='false'})' execution failed: > IRSGenericException: IRSErrorException: Image does not exist in domain: > u'image=d680a46a-7188-45f6-b6a7-3333f830c0b4, > domain=935de3ac-a735-4fc8-9161-26bfd751ffc7' > > 2019-10-08 09:58:33,767Z INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [3eea0406] FINISH, > DeleteImageGroupVDSCommand, return: , log id: 6d120001 > > 2019-10-08 09:58:33,767Z INFO > [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [3eea0406] Disk > 'd680a46a-7188-45f6-b6a7-3333f830c0b4' doesn't exist on storage domain > '935de3ac-a735-4fc8-9161-26bfd751ffc7', rolling forward > > 2019-10-08 09:58:33,778Z INFO > [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [3eea0406] Removed > task 'bfb5e88a-0e62-4e03-b02b-a5a0b36f84db' from DataBase > > 2019-10-08 09:58:33,791Z INFO > [org.ovirt.engine.core.utils.transaction.TransactionSupport] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] transaction > rolled back > > 2019-10-08 09:58:33,791Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] Trying to release > a shared lock for key: '9ac6f4ad-58d0-4a7e-b424-91f2d76abcacTEMPLATE' , > but lock does not exist > > 2019-10-08 09:58:33,791Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] Trying to release > a shared lock for key: 'a7e42574-be60-4c94-94a5-cc4b30fdb16fDISK' , but > lock does not exist > > 2019-10-08 09:58:33,791Z WARN > [org.ovirt.engine.core.bll.lock.InMemoryLockManager] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] Trying to release > exclusive lock which does not exist, lock key: 'centos-testvm-024VM_NAME' > > 2019-10-08 09:58:33,791Z INFO [org.ovirt.engine.core.bll.AddVmCommand] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] Lock freed to > object 'EngineLock:{exclusiveLocks='[centos-testvm-024=VM_NAME]', > sharedLocks='[9ac6f4ad-58d0-4a7e-b424-91f2d76abcac=TEMPLATE, > a7e42574-be60-4c94-94a5-cc4b30fdb16f=DISK]'}' > > 2019-10-08 09:58:33,804Z ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] EVENT_ID: > USER_ADD_VM_FINISHED_FAILURE(60), Failed to complete VM > centos-testvm-024 creation. > > 2019-10-08 09:58:33,824Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Failed invoking callback end > method 'onFailed' for command '1b65f576-365d-4e8b-a920-621516cbdaed' > with exception 'null', the callback is marked for end method retries but > max number of retries have been attempted. The command will be marked as > Failed. > > 2019-10-08 09:58:33,824Z INFO > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Exception in invoking callback of > command AddVm (1b65f576-365d-4e8b-a920-621516cbdaed): NullPointerException: > > 2019-10-08 09:58:33,824Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Error invoking callback method > 'onFailed' for 'FAILED' command '1b65f576-365d-4e8b-a920-621516cbdaed' > > 2019-10-08 09:58:33,824Z ERROR > [org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller] > (EE-ManagedThreadFactory-engineScheduled-Thread-63) > [067ec489-ae6c-4871-8ab6-8296016ca1ce] Exception: > javax.ejb.EJBTransactionRolledbackException > > at > org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:203) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:420) [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:148) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) > > at > org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) > [weld-ejb-3.1.1.Final.jar:3.1.1.Final] > > at > org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) > [wildfly-ejb3-17.0.1.Final.jar:17.0.1.Final] > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438) > > at > org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:618) > > at > org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57) > > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > > at > org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) > > at > org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) > > at > org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > > at > org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81) > > at > org.ovirt.engine.core.bll.interfaces.BackendInternal$$$view3.endAction(Unknown > Source) [bll.jar:] > > at > sun.reflect.GeneratedMethodAccessor1032.invoke(Unknown Source) [:1.8.0_222] > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [rt.jar:1.8.0_222] > > at java.lang.reflect.Method.invoke(Method.java:498) > [rt.jar:1.8.0_222] > > at > org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:410) > [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] > > at > org.jboss.weld.module.ejb.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:134) > [weld-ejb-3.1.1.Final.jar:3.1.1.Final] > > at > org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) > [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] > > at > org.jboss.weld.module.ejb.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:68) > [weld-ejb-3.1.1.Final.jar:3.1.1.Final] > > at > org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106) > [weld-core-impl-3.1.1.Final.jar:3.1.1.Final] > > at > org.ovirt.engine.core.bll.BackendCommandObjectsHandler$BackendInternal$BackendLocal$2049259618$Proxy$_$$_Weld$EnterpriseProxy$.endAction(Unknown > Source) [bll.jar:] > > at > org.ovirt.engine.core.bll.VmCommand.endActionOnDisks(VmCommand.java:266) > [bll.jar:] > > at > org.ovirt.engine.core.bll.AddVmCommand.endWithFailure(AddVmCommand.java:1452) > [bll.jar:] > > at > org.ovirt.engine.core.bll.CommandBase.internalEndWithFailure(CommandBase.java:736) > [bll.jar:] > > at > org.ovirt.engine.core.bll.CommandBase.endActionInTransactionScope(CommandBase.java:658) > [bll.jar:] > > at > org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2003) > [bll.jar:] > > at > org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInNewTransaction(TransactionSupport.java:202) > [utils.jar:] > > at > org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInRequired(TransactionSupport.java:137) > [utils.jar:] > > at > org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:105) > [utils.jar:] > > at > org.ovirt.engine.core.bll.CommandBase.endAction(CommandBase.java:520) > [bll.jar:] > > at > org.ovirt.engine.core.bll.ChildCommandsCallbackBase.endAction(ChildCommandsCallbackBase.java:134) > [bll.jar:] > > at > org.ovirt.engine.core.bll.ChildCommandsCallbackBase.onFailed(ChildCommandsCallbackBase.java:174) > [bll.jar:] > > at > org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.endCallback(CommandCallbacksPoller.java:67) > [bll.jar:] > > at > org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:166) > [bll.jar:] > > at > org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:109) > [bll.jar:] > > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [rt.jar:1.8.0_222] > > at > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > [rt.jar:1.8.0_222] > > at > org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383) > [javax.enterprise.concurrent-1.0.jar:] > > at > org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534) > [javax.enterprise.concurrent-1.0.jar:] > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [rt.jar:1.8.0_222] > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [rt.jar:1.8.0_222] > > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_222] > > at > org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) > [javax.enterprise.concurrent-1.0.jar:] > > Caused by: java.lang.NullPointerException > > *Ansible output:* > > The full traceback is: > > Traceback (most recent call last): > > File > "/var/folders/40/w2c8fp151854mddz_4n3czwm0000gn/T/ansible_ovirt_vm_payload_uy4lqway/__main__.py", > line 2024, in main > > clone_permissions=module.params['clone_permissions'], > > File > "/var/folders/40/w2c8fp151854mddz_4n3czwm0000gn/T/ansible_ovirt_vm_payload_uy4lqway/ansible_ovirt_vm_payload.zip/ansible/module_utils/ovirt.py", > line 610, in create > > poll_interval=self._module.params['poll_interval'], > > File > "/var/folders/40/w2c8fp151854mddz_4n3czwm0000gn/T/ansible_ovirt_vm_payload_uy4lqway/ansible_ovirt_vm_payload.zip/ansible/module_utils/ovirt.py", > line 341, in wait > > raise Exception("Timeout exceed while waiting on result state of > the entity.") > > Exception: Timeout exceed while waiting on result state of the entity. > > fatal: [centos-testvm-024.avinity.tv -> localhost]: FAILED! => { > > "changed": false, > > "invocation": { > > "module_args": { > > "affinity_group_mappings": [], > > "affinity_label_mappings": [], > > "allow_partial_import": null, > > "ballooning_enabled": null, > > "boot_devices": null, > > "boot_menu": null, > > "cd_iso": null, > > "clone": false, > > "clone_permissions": false, > > "cloud_init": { > > "authorized_ssh_keys": "ssh-rsa removed pubkey", > > "host_name": "centos-testvm-024.avinity.tv", > > "user_name": "centos" > > }, > > "cloud_init_nics": [], > > "cloud_init_persist": false, > > "cluster": "avshared1", > > "cluster_mappings": [], > > "comment": "oVirt Template Bakery Validation", > > "cpu_cores": null, > > "cpu_mode": null, > > "cpu_pinning": null, > > "cpu_shares": null, > > "cpu_sockets": null, > > "cpu_threads": null, > > "custom_compatibility_version": null, > > "custom_properties": null, > > "delete_protected": null, > > "description": null, > > "disk_format": "cow", > > "disks": [], > > "domain_mappings": [], > > "fetch_nested": false, > > "force": false, > > "graphical_console": null, > > "high_availability": null, > > "high_availability_priority": null, > > "host": null, > > "host_devices": null, > > "id": null, > > "initrd_path": null, > > "instance_type": "Medium", > > "io_threads": null, > > "kernel_params": null, > > "kernel_path": null, > > "kvm": null, > > "lease": null, > > "lun_mappings": [], > > "memory": null, > > "memory_guaranteed": null, > > "memory_max": null, > > "name": "centos-testvm-024", > > "nested_attributes": [], > > "nics": [ > > { > > "interface": "virtio", > > "name": "nic1", > > "profile_name": "tenant1" > > } > > ], > > "numa_nodes": [], > > "numa_tune_mode": null, > > "operating_system": null, > > "placement_policy": null, > > "poll_interval": 3, > > "quota_id": null, > > "reassign_bad_macs": null, > > "rng_device": null, > > "role_mappings": [], > > "serial_console": null, > > "serial_policy": null, > > "serial_policy_value": null, > > "smartcard_enabled": null, > > "soundcard_enabled": null, > > "sso": null, > > "state": "running", > > "stateless": null, > > "storage_domain": null, > > "sysprep": null, > > "template": "av-centos-75-baseimage_nfs9000", > > "template_version": null, > > "ticket": null, > > "timeout": 180, > > "timezone": null, > > "type": null, > > "usb_support": null, > > "use_latest_template_version": null, > > "vmware": null, > > "vnic_profile_mappings": [], > > "wait": true, > > "watchdog": null, > > "xen": null > > } > > }, > > "msg": "Timeout exceed while waiting on result state of the entity." > > } > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/EB5AXLUNU6LRV… >

2 11

How to tell a migrated engine it is not running as a hosted engine anymore?
by rens.verhage＠topicus.nl 21 Nov '19

21 Nov '19

I migrated a hosted ovirt-engine to a standalone machine. To do so, I created a backup with scope=all and imported this back-up into a newly installed engine. Everything was working fine. Not much later, I made a mistake and wanted to start over, so I decided to do an engine-cleanup and re-import my back-up. However, when I perform the engine-cleanup, I get this error message: [ ERROR ] It seems that you are running your engine inside of the hosted-engine VM and are not in "Global Maintenance" mode. In that case you should put the system into the "Global Maintenance" mode before running engine-setup, or the hosted-engine HA agent might kill the machine, which might corrupt your data. This is not true. The engine is now running as a standalone server. There must be a config parameter somewhere in a config file or in the database that tells the engine what mode it is running in, but I haven't found it yet. I can't find any documentation for this issue, all migration guides tell you how to migrate from standalone to hosted engine, not the other way around. How can I fix this?

1 0

[ANN] oVirt 4.3.7 is now generally available
by Sandro Bonazzola 21 Nov '19

21 Nov '19

The oVirt Project is pleased to announce the general availability of oVirt 4.3.7 as of November 21st, 2019. This update is the seventh in a series of stabilization updates to the 4.3 series. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but < 8) * CentOS Linux (or similar) 7.7 or later (but < 8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but < 8) * CentOS Linux (or similar) 7.7 or later (but < 8) * oVirt Node 4.3 (available for x86_64 only) See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available[2] oVirt Node and Appliance have been updated including: - oVirt 4.3.7: http://www.ovirt.org/release/4.3.7/ - Latest CentOS 7.7 updates including: - CEBA-2019:3077 CentOS 7 binutils BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-October/023463.html> - CEBA-2019:3057 CentOS 7 lvm2 BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-October/023475.html> - CEBA-2019:3081 CentOS 7 firewalld BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-October/023478.html> - CEBA-2019:3054 CentOS 7 hostname BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-October/023483.html> - CESA-2019:3128 Important CentOS 7 java-1.8.0-openjdk Security Update <https://lists.centos.org/pipermail/centos-announce/2019-October/023492.html> - (CESA not published yet, Important: kernel security update) https://access.redhat.com/errata/RHSA-2019:3889 - CEEA-2019:3846 CentOS 7 microcode_ctl Enhancement Update <https://lists.centos.org/pipermail/centos-announce/2019-November/023515.html> - CESA-2019:2964 Important CentOS 7 patch Security Update <https://lists.centos.org/pipermail/centos-announce/2019-October/023495.html> - CEBA-2019:3068 CentOS 7 procps-ng BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-October/023471.html> - CEBA-2019:3061 CentOS 7 rsyslog BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-October/023466.html> - CESA-2019:3197 Important CentOS 7 sudo Security Update <https://lists.centos.org/pipermail/centos-announce/2019-October/023499.html> - CEBA-2019:3072 CentOS 7 systemd BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-October/023460.html> - CEBA-2019:3056 CentOS 7 dnsmasq BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-October/023485.html> - CEBA-2019:3070 CentOS 7 ipa BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-October/023486.html> - CEBA-2019:3071 CentOS 7 libguestfs BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-October/023459.html> - CEBA-2019:3066 CentOS 7 sos BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-October/023461.html> - latest CentOS Virt and Storage SIG updates: - Ansible 2.9.1: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Glusterfs 6.6: https://docs.gluster.org/en/latest/release-notes/6.6/ - QEMU KVM EV 2.12.0-33.1.el7_7.4 : https://cbs.centos.org/koji/buildinfo?buildID=27696 Given the amount of security fixes provided by this release, upgrade is recommended as soon as practical. Additional Resources: * Read more about the oVirt 4.3.7 release highlights: http://www.ovirt.org/release/4.3.7/ * 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.3.7/ [2] http://resources.ovirt.org/pub/ovirt-4.3/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Can't start VM. An old snapshot is hold a vm state
by serphentos＠sharedlink.tk 21 Nov '19

21 Nov '19

Hello. I have a two vm's that can't start because a old snapshot (auto-generated then we migrate a disk to another storage) I tried to unlock entity and start vm or remove snapshot but still receive an errors.

1 0

port-mirror in Linux bridge
by p.staniforth＠leedsbeckett.ac.uk 20 Nov '19

20 Nov '19

Hello, Does anyone know how the port-mirror is implemented in oVirt? I am trying to investigate intermittent problems we are having with snort in oVirt VMs. Regards, Paul S.

1 0

Newbie Questions
by Dirk Streubel 20 Nov '19

20 Nov '19

Hello, i'am a new user and i have a few questions, maybe somebody can Help. It is possible to install the Server Management on a Raspberry PI 4 with 4GB. I find in the official Re Hat Document "Red Hat Virtualization Manager Hardware Requirements" that 4GB RAM is enough. And the PI has a 128 GB Flash Card. Would it work? Have somebody tested it? Another Question: Since yesterday i am trying to ad a host in my environment on ovirt Version 4.3.6. My Server Management runs under Fedora 31 under KVM/Virt-Manager without any problems. Adding a new Host doesn't work. I have tried to ad another VM with 8 Cores and 32 GB RAM as a host. This is not working, maybe VMs in VMs under ovirt is not possible, i don't know. So i try a physical Machine here as a Host. This and the other Installations fails with the Information: no route to Host. I found a bug and it says that the bug is closed. In the bug stand that maybe something wrong with the openvswitch. So i tried the following commands on the Server Management: ovn-nbctl show and ovn-sbctl show and the output was nothing. journalctl -xfe on the host that i want to migrate gave my the output: Nov 17 10:30:38 hypervisor1.linux.fritz.box sshd[12632]: Accepted keyboard-interactive/pam for root from 10.2.0.99 port 43260 ssh2 Nov 17 10:30:38 hypervisor1.linux.fritz.box systemd-logind[960]: New session 5 of user root. -- Subject: A new session 5 has been created for user root -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A new session with the ID 5 has been created for the user root. -- -- The leading process of the session is 12632. Nov 17 10:30:38 hypervisor1.linux.fritz.box sshd[12632]: pam_unix(sshd:session): session opened for user root by (uid=0) Nov 17 10:30:38 hypervisor1.linux.fritz.box systemd[1]: Started Session 5 of user root. -- Subject: Unit session-5.scope has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-5.scope has finished starting up. -- -- The start-up result is done. Nov 17 10:30:39 hypervisor1.linux.fritz.box sshd[12632]: pam_unix(sshd:session): session closed for user root Nov 17 10:30:39 hypervisor1.linux.fritz.box systemd-logind[960]: Removed session 5. -- Subject: Session 5 has been terminated -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A session with the ID 5 has been terminated. Nov 17 10:30:39 hypervisor1.linux.fritz.box sshd[12654]: Accepted keyboard-interactive/pam for root from 10.2.0.99 port 43264 ssh2 Nov 17 10:30:39 hypervisor1.linux.fritz.box systemd-logind[960]: New session 6 of user root. -- Subject: A new session 6 has been created for user root -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A new session with the ID 6 has been created for the user root. -- -- The leading process of the session is 12654. Nov 17 10:30:39 hypervisor1.linux.fritz.box systemd[1]: Started Session 6 of user root. -- Subject: Unit session-6.scope has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-6.scope has finished starting up. -- -- The start-up result is done. Nov 17 10:30:39 hypervisor1.linux.fritz.box sshd[12654]: pam_unix(sshd:session): session opened for user root by (uid=0) Nov 17 10:30:54 hypervisor1.linux.fritz.box sshd[12654]: pam_unix(sshd:session): session closed for user root Nov 17 10:30:54 hypervisor1.linux.fritz.box systemd-logind[960]: Removed session 6. -- Subject: Session 6 has been terminated -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A session with the ID 6 has been terminated. Maybe i mix some things, i don't know :( Regards Dirk

5 8

Re: [ANN] oVirt 4.3.7 Third Release Candidate is now available for testing
by Strahil 20 Nov '19

20 Nov '19

Hi Sahina, I have a strange situation: 1. When I try to access the file via 'sudo -u vdsm dd if=disk of=test bs=4M' the command fails on aprox 60MB. 2. If I run same command as root , remove the file and then run again via vdsm user -> this time no i/o error reported. My guess is that I need to check what's going on the bricks themselve ... Best Regards, Strahil Nikolov

1 0

Re: Warning: out of sync hosts ovirt-node3 ?
by Strahil 20 Nov '19

20 Nov '19

Go to Compute -> Hosts -> select the host and go to network tab. Click on it and check if it is 'out of sync'. There is a button (somewhere on the right ) to sync all networks. Best Regards, Strahil NikolovOn Nov 14, 2019 09:34, wangyu13476969128(a)126.com wrote: > > In the ovirt-engine web interface, compute-->clusters, there is a cluster with the following information: > Warning: out of sync hosts ovirt-node3 ? > > What is the cause ? How can I solve this problem ? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/QIKGY3HLQJXR5…

4 4

Newbie Thin Client question
by crege7＠gmail.com 20 Nov '19

20 Nov '19

I am new to this whole technology and I can't find anything about thin clients. I was wondering if I can even use oVirt with a thin client, if anyone knows how help would be much appreciated. I am also wondering if there is a way to use a Raspberry Pi as a thin client.

3 2

Gluster & Hyper Converged setup
by rob.downer＠orbitalsystems.co.uk 19 Nov '19

19 Nov '19

Hi, Gluster will not set up and fails... can anyone see why ? /etc/hosts set up for both backend Gluster network and front end, also LAN DNS set up on the subnet for the front end. TASK [gluster.infra/roles/backend_setup : Set PV data alignment for JBOD] ****** task path: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vg_create.yml:17 skipping: [gfs2.gluster.private] => {"changed": false, "skip_reason": "Conditional result was False"} skipping: [gfs1.gluster.private] => {"changed": false, "skip_reason": "Conditional result was False"} skipping: [gfs3.gluster.private] => {"changed": false, "skip_reason": "Conditional result was False"} TASK [gluster.infra/roles/backend_setup : Set PV data alignment for RAID] ****** task path: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vg_create.yml:24 ok: [gfs2.gluster.private] => {"ansible_facts": {"pv_dataalign": "3072K\n"}, "changed": false} ok: [gfs1.gluster.private] => {"ansible_facts": {"pv_dataalign": "3072K\n"}, "changed": false} ok: [gfs3.gluster.private] => {"ansible_facts": {"pv_dataalign": "3072K\n"}, "changed": false} TASK [gluster.infra/roles/backend_setup : Set VG physical extent size for RAID] *** task path: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vg_create.yml:34 ok: [gfs2.gluster.private] => {"ansible_facts": {"vg_pesize": "3072K\n"}, "changed": false} ok: [gfs1.gluster.private] => {"ansible_facts": {"vg_pesize": "3072K\n"}, "changed": false} ok: [gfs3.gluster.private] => {"ansible_facts": {"vg_pesize": "3072K\n"}, "changed": false} TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** task path: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vg_create.yml:46 failed: [gfs1.gluster.private] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"ansible_loop_var": "item", "changed": false, "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Device /dev/sdb not found."} failed: [gfs3.gluster.private] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"ansible_loop_var": "item", "changed": false, "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Device /dev/sdb not found."} failed: [gfs2.gluster.private] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"ansible_loop_var": "item", "changed": false, "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Device /dev/sdb not found."} NO MORE HOSTS LEFT ************************************************************* NO MORE HOSTS LEFT ************************************************************* PLAY RECAP ********************************************************************* gfs1.gluster.private : ok=10 changed=0 unreachable=0 failed=1 skipped=16 rescued=0 ignored=0 gfs2.gluster.private : ok=11 changed=1 unreachable=0 failed=1 skipped=16 rescued=0 ignored=0 gfs3.gluster.private : ok=10 changed=0 unreachable=0 failed=1 skipped=16 rescued=0 ignored=0 0 / 0 Reply

4 9

Wrong CPU?
by Christian Reiss 19 Nov '19

19 Nov '19

Hey folks, running an AMD Ryzen CPU here: processor : 0 vendor_id : AuthenticAMD cpu family : 23 model : 49 model name : AMD EPYC 7282 16-Core Processor However, libvirt is detecting this as EPYC-IBPB without the ssbd flags? <cpu> <arch>x86_64</arch> <model>EPYC-IBPB</model> <vendor>AMD</vendor> <microcode version='137367580'/> <counter name='tsc' frequency='2799999000'/> <topology sockets='1' cores='16' threads='2'/> <feature name='ht'/> <feature name='osxsave'/> <feature name='cmt'/> <feature name='clwb'/> <feature name='umip'/> <feature name='xsaves'/> <feature name='mbm_total'/> <feature name='mbm_local'/> <feature name='cmp_legacy'/> <feature name='extapic'/> <feature name='ibs'/> <feature name='skinit'/> <feature name='wdt'/> <feature name='tce'/> <feature name='topoext'/> <feature name='perfctr_core'/> <feature name='perfctr_nb'/> <feature name='invtsc'/> <feature name='wbnoinvd'/> <pages unit='KiB' size='4'/> <pages unit='KiB' size='2048'/> <pages unit='KiB' size='1048576'/> </cpu> [root@node01 ~]# grep ssbd /var/cache/libvirt/qemu/capabilities/*.xml <property name='ssbd' type='boolean' value='false'/> <property name='virt-ssbd' type='boolean' value='false'/> <property name='ssbd' type='boolean' value='false'/> <property name='virt-ssbd' type='boolean' value='false'/> But the flag is there: [root@node01 ~]# grep ssbd /proc/cpuinfo | tail -n1 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc art rep_good nopl xtopology nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 cpb cat_l3 cdp_l3 hw_pstate sme retpoline_amd ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif umip overflow_recov succor smca I tried adding "options kvm_amd avic=1" as well as "options kvm_amd avic=0" to /etc/modprobe.d/kvm.conf (always with reboots), adding mitigations=off to grub.. I can't think of any other solution. I just can't get the oVirt engine running with the ssbd flag. Seems cpu can do this, oVirt can do this, libvirt does not detect the cpu correctly or at least ignores it. But the hosted engine demands it. I am at a loss. Any help is oh-so-greatly appreciated. -Chris. -- Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon support(a)alpha-labs.net \ / Campaign X against HTML WEB alpha-labs.net / \ in eMails GPG Retrieval https://gpg.christian-reiss.de GPG ID ABCD43C5, 0x44E29126ABCD43C5 GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5 "It's better to reign in hell than to serve in heaven.", John Milton, Paradise lost.

3 6

[ANN] oVirt 4.3.7 Fourth Release Candidate is now available for testing
by Sandro Bonazzola 19 Nov '19

19 Nov '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.7 Fourth Release Candidate for testing, as of November 19th, 2019. This update is a release candidate of the seventh in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) * oVirt Node 4.3 (available for x86_64 only) has been built consuming CentOS 7.7 Release See the release notes [1] for known issues, new features and bugs fixed. While testing this release candidate please note that oVirt node now includes: - ansible 2.9.1 - GlusterFS 6.6 Notes: - oVirt Appliance is already available - oVirt Node is already available Additional Resources: * Read more about the oVirt 4.3.7 release highlights: http://www.ovirt.org/release/4.3.7/ * 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.3.7/ [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

FOSDEM 2020 Virtualization & IaaS Devroom CfP
by Piotr Kliczewski 18 Nov '19

18 Nov '19

Friendly reminder that there are 2 weeks before the submission deadline. Room day update: This year Virt and IaaS room will be on the 2nd of February. See you all at FOSDEM!

1 0

Gluster setup
by rob.downer＠orbitalsystems.co.uk 18 Nov '19

18 Nov '19

I have set up a 3 node system. Gluster has its own backend network and I have tried entering the FQDN hosts via ssh as follows... gfs1.gluster.private 10.10.45.11 gfs2.gluster.private 10.10.45.12 gfs3.gluster.private 10.10.45.13 I entered at /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 gfs1.gluster.private 10.10.45.11 gfs2.gluster.private 10.10.45.12 gfs3.gluster.private 10.10.45.13 but on the CLI host gfs1.gluster.private returns [root@ovirt1 etc]# host gfs1.gluster.private Host gfs1.gluster.private not found: 3(NXDOMAIN) [root@ovirt1 etc]# I guess this is the wrong hosts file, resolver.conf lists files first for lookup...

4 9

Re: SSBD issues on live cluster
by Strahil 16 Nov '19

16 Nov '19

Copy the long xml and save it to a file. Then edit and remove the requirement for the mitigations. Then set the following alias: alias virsh='virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf' Then : virsh undefine HostedEngine virsh define <file> virsh start HostedEngine Maybe it will work :) Best Regards, Strahil NikolovOn Nov 15, 2019 15:30, Christian Reiss <email(a)christian-reiss.de> wrote: > > On 15/11/2019 13:30, thomas(a)hoberg.net wrote: > > Since there is no guarantee that the oVirt node image and the hosted-engine image are aligned, I'd recommend disabling all mitigations during the host's boot (only got a list of the Intel flags, sorry: Not rich enough for EPYC) and see if that sails through. And if you have no mitigation risk issues, to keep the base CPU definition as low as you can stand (your VMs applications could miss out on some nice instruction extensions or other features if you go rock-bottom). > > Hey, > > Ugh, I am at a loss. I added > > --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< > GRUB_CMDLINE_LINUX='crashkernel=auto > rd.lvm.lv=onn/ovirt-node-ng-4.3.6-0.20190926.0+1 rd.lvm.lv=onn/swap > mitigations=off rhgb quiet' > --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< > > > to /etc/default/grub, created a new grub.cfg and rebooted. > > --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< > [root@node01 ~]# cat /proc/cmdline > BOOT_IMAGE=/ovirt-node-ng-4.3.6-0.20190926.0+1/vmlinuz-3.10.0-1062.1.1.el7.x86_64 > root=/dev/onn/ovirt-node-ng-4.3.6-0.20190926.0+1 ro crashkernel=auto > rd.lvm.lv=onn/swap mitigations=off rhgb quiet > rd.lvm.lv=onn/ovirt-node-ng-4.3.6-0.20190926.0+1 > img.bootid=ovirt-node-ng-4.3.6-0.20190926.0+1 > --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< > > > Even after clearing the cache and restarting libvirt the issue is still > > --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< > [root@node01 ~]# cat > /var/cache/libvirt/qemu/capabilities/3c76bc41d59c0c7314b1ae8e63f4f765d2cf16abaeea081b3ca1f5d8732f7bb1.xml > | grep ssb > <property name='ssbd' type='boolean' value='false'/> > <property name='virt-ssbd' type='boolean' value='false'/> > <property name='ssbd' type='boolean' value='false'/> > <property name='virt-ssbd' type='boolean' value='false'/> > --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< > > > and flags are still set (duh) > > --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< > [root@node01 ~]# grep ssbd /proc/cpuinfo | tail -n1 > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt > pdpe1gb rdtscp lm constant_tsc art rep_good nopl xtopology nonstop_tsc > extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 > sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy > svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs > skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 cpb > cat_l3 cdp_l3 hw_pstate sme retpoline_amd ssbd ibrs ibpb stibp vmmcall > fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb > sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total > cqm_mbm_local clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save > tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold > avic v_vmsave_vmload vgif umip overflow_recov succor smca > --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< > > > Deploying the oVirt hosted engine still works up to the final point, > when it stops with the usual > > --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< > 2019-11-15 14:43:54,758+0100 INFO (jsonrpc/6) [api.virt] FINISH > getStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': > [{'status': 'Down', 'exitMessage': 'the CPU is incompatible with host > CPU: Host CPU does not provide required features: virt-ssbd', > 'statusTime': '4294738860', 'vmId': > 'd116b296-9ae7-4ff3-80b4-73dc228a7b64', 'exitReason': 1, 'exitCode': > 1}]} from=::1,46514, vmId=d116b296-9ae7-4ff3-80b4-73dc228a7b64 (api:54) > --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< > > > I can see that during the final stages (up to this point the engine VM > is up and running) in vdsm.log there is a (super long) line: > > --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< > 2019-11-15 13:36:10,248+0100 INFO (jsonrpc/4) [api.virt] FINISH create > return={'status': {'message': 'Done', 'code': 0}, 'vmList': {'status': > 'WaitForLaunch', 'maxMemSize': 65536, 'acpiEnable': 'true', > 'emulatedMachine': 'pc-i440fx-rhel7.6.0', 'numOfIoThreads': '1', 'vmId': > 'd116b296-9ae7-4ff3-80b4-73dc228a7b64', 'memGuaranteedSize': 1024, > 'timeOffset': '0', 'smpThreadsPerCore': '1', 'cpuType': 'EPYC', > 'guestDiskMapping': {}, 'arch': 'x86_64', 'smp': '4', 'guestNumaNodes': > [{'nodeIndex': 0, 'cpus': '0,1,2,3', 'memory': '16384'}], u'xml': > u'<?xml version=\'1.0\' encoding=\'UTF-8\'?>\n<domain > xmlns:ovirt-tune="http://ovirt.org/vm/tune/1.0" > xmlns:ovirt-vm="http://ovirt.org/vm/1.0" > type="kvm"><name>HostedEngine</name><uuid>d116b296-9ae7-4ff3-80b4-73dc228a7b64</uuid><memory>16777216</memory><currentMemory>16777216</currentMemory><iothreads>1</iothreads><maxMemory > slots="16">67108864</maxMemory><vcpu current="4">64</vcpu><sysinfo > type="smbios"><system><entry name="manufacturer">oVirt</entry><entry > name="product">OS-NAME:</entry><entry > name="version">OS-VERSION:</entry><entry > name="serial">HOST-SERIAL:</entry><entry > name="uuid">d116b296-9ae7-4ff3-80b4-73dc228a7b64</entry></system></sysinfo><clock > offset="variable" adjustment="0"><timer name="rtc" > tickpolicy="catchup"/><timer name="pit" tickpolicy="delay"/><timer > name="hpet" present="no"/></clock><features><acpi/></features><cpu > match="exact"><model>EPYC</model><feature name="ibpb" > policy="require"/><feature name="virt-ssbd" policy="require"/><topology > cores="4" threads="1" sockets="16"/><numa><cell id="0" cpus="0,1,2,3" > memory="16777216"/></numa></cpu><cputune/><devices><input type="mouse" > bus="ps2"/><channel type="unix"><target type="virtio" > name="ovirt-guest-agent.0"/><source mode="bind" > path="/var/lib/libvirt/qemu/channels/d116b296-9ae7-4ff3-80b4-73dc228a7b64.ovirt-guest-agent.0"/></channel><channel > type="unix"><target type="virtio" name="org.qemu.guest_agent.0"/><source > mode="bind" > path="/var/lib/libvirt/qemu/channels/d116b296-9ae7-4ff3-80b4-73dc228a7b64.org.qemu.guest_agent.0"/></channel><sound > model="ich6"><alias > name="ua-05ce597b-8e43-4360-81ac-2ca13cb4f9d5"/></sound><graphics > type="vnc" port="-1" autoport="yes" passwd="*****" > passwdValidTo="1970-01-01T00:00:01" keymap="en-us"><listen > type="network" network="vdsm-ovirtmgmt"/></graphics><controller > type="scsi" model="virtio-scsi" index="0"><driver iothread="1"/><alias > name="ua-30edc108-3218-43dc-ad43-129ce392930e"/></controller><video><model > type="qxl" vram="32768" heads="1" ram="65536" vgamem="16384"/><alias > name="ua-31187f25-275b-490d-922b-15712b6fabb6"/></video><console > type="unix"><source > path="/var/run/ovirt-vmconsole-console/d116b296-9ae7-4ff3-80b4-73dc228a7b64.sock" > mode="bind"/><target type="serial" port="0"/><alias > name="ua-7a643a8e-6871-4d63-a38e-632f03566e63"/></console><graphics > type="spice" port="-1" autoport="yes" passwd="*****" > passwdValidTo="1970-01-01T00:00:01" tlsPort="-1"><channel name="main" > mode="secure"/><channel name="inputs" mode="secure"/><channel > name="cursor" mode="secure"/><channel name="playback" > mode="secure"/><channel name="record" mode="secure"/><channel > name="display" mode="secure"/><channel name="smartcard" > mode="secure"/><channel name="usbredir" mode="secure"/><listen > type="network" network="vdsm-ovirtmgmt"/></graphics><controller > type="virtio-serial" index="0" ports="16"><alias > name="ua-833fb61c-213a-4871-b99a-3863958ce070"/></controller><rng > model="virtio"><backend model="random">/dev/urandom</backend><alias > name="ua-91c1c22f-5d21-458b-b1a1-a700ea8b5e5c"/></rng><memballoon > model="virtio"><stats period="5"/><alias > name="ua-943f5866-0165-40bf-a4b6-658072a1d7f5"/></memballoon><controller > type="usb" model="piix3-uhci" index="0"/><serial type="unix"><source > path="/var/run/ovirt-vmconsole-console/d116b296-9ae7-4ff3-80b4-73dc228a7b64.sock" > mode="bind"/><target port="0"/></serial><channel type="spicevmc"><target > type="virtio" name="com.redhat.spice.0"/></channel><interface > type="bridge"><model type="virtio"/><link state="up"/><source > bridge="ovirtmgmt"/><driver queues="4" name="vhost"/><alias > name="ua-03c1177f-98be-4bed-8dd0-1f1895a0a0c6"/><mac > address="00:16:3e:3b:5d:da"/><mtu size="1500"/><filterref > filter="vdsm-no-mac-spoofing"/><bandwidth/></interface><disk type="file" > device="cdrom" snapshot="no"><driver name="qemu" type="raw" > error_policy="report"/><source file="" > startupPolicy="optional"><seclabel model="dac" type="none" > relabel="no"/></source><target dev="hdc" bus="ide"/><readonly/><alias > name="ua-acc9e0f3-ab5b-4637-876a-96242a52a470"/></disk><disk > snapshot="no" type="file" device="disk"><target dev="vda" > bus="virtio"/><source > file="/rhev/data-center/00000000-0000-0000-0000-000000000000/b77c80b7-a2a5-4627-a48e-8b8a49583c5d/images/e070502c-780b-45a5-98d1-6f6db9a48967/e4066d0d-2a83-4802-8976-09f2a18baf23"><seclabel > model="dac" type="none" relabel="no"/></source><driver name="qemu" > iothread="1" io="threads" type="raw" error_policy="stop" > cache="none"/><alias > name="ua-e070502c-780b-45a5-98d1-6f6db9a48967"/><serial>e070502c-780b-45a5-98d1-6f6db9a48967</serial></disk><lease><key>e4066d0d-2a83-4802-8976-09f2a18baf23</key><lockspace>b77c80b7-a2a5-4627-a48e-8b8a49583c5d</lockspace><target > offset="LEASE-OFFSET:e4066d0d-2a83-4802-8976-09f2a18baf23:b77c80b7-a2a5-4627-a48e-8b8a49583c5d" > path="LEASE-PATH:e4066d0d-2a83-4802-8976-09f2a18baf23:b77c80b7-a2a5-4627-a48e-8b8a49583c5d"/></lease></devices><pm><suspend-to-disk > enabled="no"/><suspend-to-mem enabled="no"/></pm><os><type arch="x86_64" > machine="pc-i440fx-rhel7.6.0">hvm</type><smbios mode="sysinfo"/><bios > useserial="yes"/></os><metadata><ovirt-tune:qos/><ovirt-vm:vm><ovirt-vm:minGuaranteedMemoryMb > type="int">1024</ovirt-vm:minGuaranteedMemoryMb><ovirt-vm:clusterVersion>4.3</ovirt-vm:clusterVersion><ovirt-vm:custom/><ovirt-vm:device > mac_address="00:16:3e:3b:5d:da"><ovirt-vm:custom/></ovirt-vm:device><ovirt-vm:device > devtype="disk" > name="vda"><ovirt-vm:poolID>00000000-0000-0000-0000-000000000000</ovirt-vm:poolID><ovirt-vm:volumeID>e4066d0d-2a83-4802-8976-09f2a18baf23</ovirt-vm:volumeID><ovirt-vm:shared>exclusive</ovirt-vm:shared><ovirt-vm:imageID>e070502c-780b-45a5-98d1-6f6db9a48967</ovirt-vm:imageID><ovirt-vm:domainID>b77c80b7-a2a5-4627-a48e-8b8a49583c5d</ovirt-vm:domainID></ovirt-vm:device><ovirt-vm:launchPaused>false</ovirt-vm:launchPaused><ovirt-vm:resumeBehavior>auto_resume</ovirt-vm:resumeBehavior></ovirt-vm:vm></metadata></domain>', > 'smpCoresPerSocket': '4', 'kvmEnable': 'true', 'bootMenuEnable': > 'false', 'devices': [], 'custom': {}, 'maxVCpus': '64', 'statusTime': > '4357530330', 'vmName': 'HostedEngine', 'maxMemSlots': 16}} > from=::1,40284, vmId=d116b296-9ae7-4ff3-80b4-73dc228a7b64 (api:54) > > [...] > > <feature name="virt-ssbd" policy="require"/> > --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< > > > There is sets "<feature name="virt-ssbd" policy="require"/>", which is > added in the xml, ever since it will break. > > > Ayee. > > > -- > Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon > support(a)alpha-labs.net \ / Campaign > X against HTML > WEB alpha-labs.net / \ in eMails > > GPG Retrieval https://gpg.christian-reiss.de > GPG ID ABCD43C5, 0x44E29126ABCD43C5 > GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5 > > "It's better to reign in hell than to serve in heaven.", > John Milton, Paradise lost. > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/HW2A4TLFFLKAI…

1 0

Ovirt instance having RTO in every 10 minutes
by Crazy Ayansh 15 Nov '19

15 Nov '19

Hi Team, I am using ovirt hosted engine 4.3.6.6-1 the newest one but it seems to me it's not stable as my hosted engine VM stopped pining in every 10 minutes and my web console get disconnected every time. [image: image.png] See in the above snapshot in every 10 minutes Data Center status get Non responsive. could any one help out here. Thanks Shashank

2 1

SSBD issues on live cluster
by Christian Reiss 15 Nov '19

15 Nov '19

Hey folks, new hardware arrived \o/ Installation as HCI was a bliss, with gluster et all. Deploying the hosted engine also worked until it came to the very last point: Health checks, which failed. vdsm.log: --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< 2019-11-15 09:54:02,588+0100 INFO (jsonrpc/4) [api.virt] FINISH getStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': [{'status': 'Down', 'exitMessage': 'the CPU is incompatible with host CPU: Host CPU does not provide required features: virt-ssbd', 'statusTime': '4344202670', 'vmId': '50ac6250-4c24-40fd-894c-bc248c4f6fa2', 'exitReason': 1, 'exitCode': 1}]} from=::1,37492, vmId=50ac6250-4c24-40fd-894c-bc248c4f6fa2 (api:54) --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< But: --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< [root@node01 vdsm]# cat /proc/cpuinfo | grep flags | tail -n 1 | grep -i --color ssb flags : fpu vme [...] ssbd [...] --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< Cpu is a --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< processor : 1 vendor_id : AuthenticAMD cpu family : 23 model : 49 model name : AMD EPYC 7282 16-Core Processor --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< --- --- 8< Anyone willing to shed some light on this issue? Thanks in advance! -Chris. -- Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon support(a)alpha-labs.net \ / Campaign X against HTML WEB alpha-labs.net / \ in eMails GPG Retrieval https://gpg.christian-reiss.de GPG ID ABCD43C5, 0x44E29126ABCD43C5 GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5 "It's better to reign in hell than to serve in heaven.", John Milton, Paradise lost.

2 8

Re: Gluster setup
by Strahil 15 Nov '19

15 Nov '19

In /etc/hosts you first enter the IP then FQDN, and last shortname (aliases). Fix the /etc/hosts file ! Best Regards, Strahil NikolovOn Nov 15, 2019 14:15, rob.downer(a)orbitalsystems.co.uk wrote: > > I have set up a 3 node system. > > Gluster has its own backend network and I have tried entering the FQDN hosts via ssh as follows... > gfs1.gluster.private 10.10.45.11 > gfs2.gluster.private 10.10.45.12 > gfs3.gluster.private 10.10.45.13 > > I entered at /etc/hosts > > 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 > ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 > gfs1.gluster.private 10.10.45.11 > gfs2.gluster.private 10.10.45.12 > gfs3.gluster.private 10.10.45.13 > > but on the CLI > > host gfs1.gluster.private > > returns > > [root@ovirt1 etc]# host gfs1.gluster.private > Host gfs1.gluster.private not found: 3(NXDOMAIN) > [root@ovirt1 etc]# > > I guess this is the wrong hosts file, resolver.conf lists files first for lookup... > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ILABGNZFOH5BP…

1 0

Re: Gluster Questions
by Strahil 15 Nov '19

15 Nov '19

Ovirt can use VDO for deduplication and compression, but I think it was related to ZFS. Best Regards, Strahil NikolovOn Nov 15, 2019 11:27, markus.falb(a)mafalb.at wrote: > > ... > > > Running a 3 node HCI cluster (in testing stages) I would love to hear > > your input. All nodes are exactly identical and have a local storage of > > 8tb in SSDs made out of a RAID6. > > ... > > > There is the option of compression & dedup, coming from ZFS this is a > > memory hog and kind of insane. What are your thoughts on compression & > > dedup at this time? > > > > The effective size of the compressed drive is suggested 10-fold of the > > original sizes. Seems a big crazy high; any suggestions here? > > is ovirt using VDO for dedup and compression? > > https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infras… > > best regards, markus > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/H3WIKBQGE75EX…

1 0

Gluster Questions
by Christian Reiss 15 Nov '19

15 Nov '19

Hey folks, Running a 3 node HCI cluster (in testing stages) I would love to hear your input. All nodes are exactly identical and have a local storage of 8tb in SSDs made out of a RAID6. Gluster was setup to match this (Raid6, cluster of 256k). There is the option of compression & dedup, coming from ZFS this is a memory hog and kind of insane. What are your thoughts on compression & dedup at this time? The effective size of the compressed drive is suggested 10-fold of the original sizes. Seems a big crazy high; any suggestions here? Thanks for your input! -Chris. -- Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon support(a)alpha-labs.net \ / Campaign X against HTML WEB alpha-labs.net / \ in eMails GPG Retrieval https://gpg.christian-reiss.de GPG ID ABCD43C5, 0x44E29126ABCD43C5 GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5 "It's better to reign in hell than to serve in heaven.", John Milton, Paradise lost.

2 1

Import VMs from VMware vCenter to oVirt with different CPU manufacturer
by wodel youchi 14 Nov '19

14 Nov '19

Hi, We have a VMware vCenter platform based on Intel CPUs and we are planing to migrate to oVirt. Is it possible to migrate VMs from Intel Xeon based CPU platform to AMD Epyc based platform? Regards.

2 1

External VM vdsbroker parsing error
by Marcus van Dam 14 Nov '19

14 Nov '19

Hi, I am running a two node oVirt cluster, based on the "High-Availability oVirt-Cluster with iSCSI-Storage" document published by Linbit. Although a older document, I am happy with the setup. With this setup, I notice a flood of failed VM imports in the engine logs. This setup is based on a separate Qemu VM running the oVirt-Engine. Which seems to be the origin of the error (posted below). Is there anything I can do to either ignore this instance and not fill the logs, or fix the import error? Thanks! - Marcus ---- %< ---- SNIP ---- %< ----- %< ---- SNIP ---- %< ----- 2019-11-14 14:50:27,155+01 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.FullListAdapter] (EE-ManagedThreadFactory-engineScheduled-Thread-38) [2e46652f] Failed during parsing configuration of VM 133789fc-b329-40b8-bac3-e3ff8c37b1f9 (<domain type='kvm' id='2'> <name>oVirtm</name> <uuid>133789fc-b329-40b8-bac3-e3ff8c37b1f9</uuid> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu placement='static'>2</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-rhel7.6.0'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'> <timer name='kvmclock' present='yes'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <pm> <suspend-to-mem enabled='no'/> <suspend-to-disk enabled='no'/> </pm> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source dev='/dev/drbd/by-res/kvm/0'/> <backingStore/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/etc/ovirtm/seed.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='none'> <alias name='usb'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:75:3c:7d'/> <source bridge='ovirtmgmt'/> <target dev='vnet1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/4'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/4'> <source path='/dev/pts/4'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-2-oVirtm/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <video> <model type='vga' vram='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='none'/> <rng model='virtio'> <backend model='random'>/dev/urandom</backend> <alias name='rng0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </rng> </devices> <seclabel type='dynamic' model='selinux' relabel='yes'> <label>system_u:system_r:svirt_t:s0:c624,c838</label> <imagelabel>system_u:object_r:svirt_image_t:s0:c624,c838</imagelabel> </seclabel> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+107:+107</label> <imagelabel>+107:+107</imagelabel> </seclabel> </domain> ), error is: {}: java.lang.NullPointerException 2019-11-14 14:50:27,155+01 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.FullListAdapter] (EE-ManagedThreadFactory-engineScheduled-Thread-38) [2e46652f] Exception:: java.lang.NullPointerException

1 0

Do I need to use self hosted engine with a GlusterFs three node setup
by donagh.moran＠oracle.com 14 Nov '19

14 Nov '19

Every piece of documentation I read regarding the setup of Gluster seems to suggest using at least one of the the nodes to host the engine. Is this a requirement of can I use an engine that is deployed on a VM on another server in the same network? Any info would be much appreciated.

2 4

Gluster Network Issues....
by rob.downer＠orbitalsystems.co.uk 14 Nov '19

14 Nov '19

I have set up 3 SuperMicro's with Ovirt Node and all pretty sweet. FQDN set up for LAN and also after setup I have enabled a second NIC with FQDN for a Gluster network. The issue is the second ports seem to be unavailable for network access by ping or login.... if you login on root the system says that the ports are available for login on the bash shell after login and node check comes back fine. I have IPMI set up on the systems as well for access. am I missing something ? I realise Gluster should be on a seperate LAN and will put it on a 10BGe network but I'm just testing. I have the lastest stable build. Any help would be appreciated.

1 0

Hosted-Engine wizard disappeared after cockpit idle session timeout
by wodel youchi 14 Nov '19

14 Nov '19

Hi, I got this behavior once and I didn't tested again. I started the hosted-engine deployment using cockpit webui, the process went smoothly, the LocalHosttedEngine VM was created, at that time I left the console for sometime. When I get back the cockpit console was closed due to idle session timeout, I reconnect, and the hosted-engine wizard had disappeared and I didn't find a way to get it back, the only choice was to start the process again even if the console was showing that the host was registered with a hosted engine Manager, so I couldn't continue the deployment (the storage phase). I had to stop the LocalHosttedEngine VM, delete it's temporary disk, then restart the deployment again and this time I stick with cockpit webui to get it done. Regards.

2 1

Warning: out of sync hosts ovirt-node3 ?
by wangyu13476969128＠126.com 14 Nov '19

14 Nov '19

In the ovirt-engine web interface, compute-->clusters, there is a cluster with the following information: Warning: out of sync hosts ovirt-node3 ? What is the cause ? How can I solve this problem ?

1 0

engine manager VM not launching
by bepassionatenow＠gmail.com 14 Nov '19

14 Nov '19

Good evening/morning, I can't launch the Engine Manager after the initial install through Cockpit. It initially started fine but I could never login. Cockpit showed that the VM was not set to auto-restart. I don't see how to change that and the button to "run" won't work. Spinning box in the top right corner is causing issues (won't register properly). Any help would be greatly appreciated. Thanks! Daniel

1 0

Windows Server 2019 crash dxgkrnl.sys
by gregor 13 Nov '19

13 Nov '19

Hello, during the Installation of Windows Server 2019 after the first reboot the VM crashed and inside the ntbtlog.txt I found that dxgkrnl.sys can not be loaded. Environment: oVirt 4.3.6.7-1.el7 CPU: Intel-Westmere Memory: 4096MB Operation System VM config: Windows 2019 x64 HDD: VirtIO-SCSI VirtIO driver: virtio-win-0.1.171_servers_amd64.vfd Does anybody has an hint how to solve this problem and use Windows Server 2019? Besides: It's possible to install and use Windows Server 2019 in VirtualBox 6.*. We have to install it in the meantime there to have a alternative solution because it took now about two days to find a solution. We tried different settings for VGA and drivers IDE ... and many more. best regards gregor

2 1

oVirt change IP's & add new ISO share
by Jonathan Mathews 13 Nov '19

13 Nov '19

Good Day I have to change the IP addresses of the oVirt Engine, hosts and storage to a new IP range. Please, can you advise the best way to do this and if there is anything I would need to change in the database? I have also run into an issue where someone has removed the ISO share/data on the storage, so I am unable to remove, activate, detach or even add a new ISO share. Please, can you advise the best wat to resolve this? Please see the below engine logs: 2019-10-30 11:39:13,918 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DetachStorageDomainVDSCommand] (org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Failed in 'DetachStorageDomainVDS' method 2019-10-30 11:39:13,942 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VDSM command failed: Storage domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',) 2019-10-30 11:39:13,943 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (org.ovirt.thread.pool-8-thread-27) [58f6cfb8] IrsBroker::Failed::DetachStorageDomainVDS: IRSGenericException: IRSErrorException: Failed to DetachStorageDomainVDS, error = Storage domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',), code = 358 2019-10-30 11:39:13,951 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DetachStorageDomainVDSCommand] (org.ovirt.thread.pool-8-thread-27) [58f6cfb8] FINISH, DetachStorageDomainVDSCommand, log id: 5547e2df 2019-10-30 11:39:13,951 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMGetAllTasksInfoVDSCommand] (org.ovirt.thread.pool-8-thread-38) [58f6cfb8] -- executeIrsBrokerCommand: Attempting on storage pool '5849b030-626e-47cb-ad90-3ce782d831b3' 2019-10-30 11:39:13,951 ERROR [org.ovirt.engine.core.bll.storage.DetachStorageDomainFromPoolCommand] (org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Command 'org.ovirt.engine.core.bll.storage.DetachStorageDomainFromPoolCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException: IRSGenericException: IRSErrorException: Failed to DetachStorageDomainVDS, error = Storage domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',), code = 358 (Failed with error StorageDomainDoesNotExist and code 358) 2019-10-30 11:39:13,952 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksInfoVDSCommand] (org.ovirt.thread.pool-8-thread-38) [58f6cfb8] START, HSMGetAllTasksInfoVDSCommand(HostName = host01, VdsIdVDSCommandParametersBase:{runAsync='true', hostId='291a3a19-7467-4783-a6f7-2b2dd0de9ad3'}), log id: 6cc238fb 2019-10-30 11:39:13,952 INFO [org.ovirt.engine.core.bll.storage.DetachStorageDomainFromPoolCommand] (org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Command [id=cec030b7-4a62-43a2-9ae8-de56a5d71ef8]: Compensating CHANGED_STATUS_ONLY of org.ovirt.engine.core.common.businessentities.StoragePoolIsoMap; snapshot: EntityStatusSnapshot:{id='StoragePoolIsoMapId:{storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3', storageId='42b7d819-ce3a-4a18-a683-f4817c4bdb06'}', status='Inactive'}. 2019-10-30 11:39:13,975 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-27) [58f6cfb8] Correlation ID: 28ac658, Job ID: b31e0f44-2d82-47bf-90d9-f69e399d994f, Call Stack: null, Custom Event ID: -1, Message: Failed to detach Storage Domain iso to Data Center Default. (User: admin@internal) 2019-10-30 11:42:46,711 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMGetAllTasksInfoVDSCommand] (org.ovirt.thread.pool-8-thread-25) [31e89bba] START, SPMGetAllTasksInfoVDSCommand( IrsBaseVDSCommandParameters:{runAsync='true', storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3', ignoreFailoverLimit='false'}), log id: 59192768 2019-10-30 11:42:48,825 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand] (org.ovirt.thread.pool-8-thread-34) [31e89bba] Failed in 'ActivateStorageDomainVDS' method 2019-10-30 11:42:48,855 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-34) [31e89bba] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VDSM command failed: Storage domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',) 2019-10-30 11:42:48,856 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (org.ovirt.thread.pool-8-thread-34) [31e89bba] IrsBroker::Failed::ActivateStorageDomainVDS: IRSGenericException: IRSErrorException: Failed to ActivateStorageDomainVDS, error = Storage domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',), code = 358 2019-10-30 11:42:48,864 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand] (org.ovirt.thread.pool-8-thread-34) [31e89bba] FINISH, ActivateStorageDomainVDSCommand, log id: 518fdcf 2019-10-30 11:42:48,865 ERROR [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-8-thread-34) [31e89bba] Command 'org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException: IRSGenericException: IRSErrorException: Failed to ActivateStorageDomainVDS, error = Storage domain does not exist: (u'42b7d819-ce3a-4a18-a683-f4817c4bdb06',), code = 358 (Failed with error StorageDomainDoesNotExist and code 358) 2019-10-30 11:42:48,865 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMGetAllTasksInfoVDSCommand] (org.ovirt.thread.pool-8-thread-25) [31e89bba] -- executeIrsBrokerCommand: Attempting on storage pool '5849b030-626e-47cb-ad90-3ce782d831b3' 2019-10-30 11:42:48,865 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksInfoVDSCommand] (org.ovirt.thread.pool-8-thread-25) [31e89bba] START, HSMGetAllTasksInfoVDSCommand(HostName = host02, VdsIdVDSCommandParametersBase:{runAsync='true', hostId='3673a0e1-721d-40ba-a179-b1f13a9aec43'}), log id: 47ef923b 2019-10-30 11:42:48,866 INFO [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand] (org.ovirt.thread.pool-8-thread-34) [31e89bba] Command [id=68bf0e1e-6a0b-41cb-9cad-9eb2bf87c5ee]: Compensating CHANGED_STATUS_ONLY of org.ovirt.engine.core.common.businessentities.StoragePoolIsoMap; snapshot: EntityStatusSnapshot:{id='StoragePoolIsoMapId:{storagePoolId='5849b030-626e-47cb-ad90-3ce782d831b3', storageId='42b7d819-ce3a-4a18-a683-f4817c4bdb06'}', status='Inactive'}. 2019-10-30 11:42:48,888 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-34) [31e89bba] Correlation ID: 5b208434, Job ID: dff5f615-9dc4-4d79-a37e-5c6e99a2cc6b, Call Stack: null, Custom Event ID: -1, Message: Failed to activate Storage Domain iso (Data Center Default) by admin@internal Thanks Jonathan

3 4

DHCP Client in Guest VM does not work on ovirtmgmt
by ccesario＠blueit.com.br 13 Nov '19

13 Nov '19

Hello, Is there any special config to usage dhcp client on Guest VM using ovirtmgmt/ovirtmgmt vnic profile ? Currently I have a VM using the ovirtmgmt/ovirtmgmt NIC profile and this interface is configured as DHCP client, and this does not work when using ovirtmgmt/ovirtmgmt as NIC profile. But if I assign manual IP address from the same range of DHCP server the comunication it works. And If usage other NIC profile in other VLAN with other DHCP server it works. It seems ovirtmgmt/ovirtmgmt profile filter the DHCP protocol. Could someone has idea to allow DHCP protocol works on ovirtmgmt/ovirtmgmt NIC profile? Best regards Carlos

7 24

Tesla P4 and /sys/class/mdev_bus/
by Fabrice Bacchella 13 Nov '19

13 Nov '19

I have a Tesla P4 installed on a HPE ProLiant DL360 Gen10 on a CentOS 7.7. The setup was running fine since at least February. I made a successful upgrade from oVirt 4.2 to 4.3 and CentOS 7.6 to CentOS 7.7. I was using in oVirt in a pass-througth setting. I made a minor upgrade a few days ago. And since the VM is unable to see the Tesla P4. I think that the main problem is with mdev. vdsm-client Host hostdevListByCaps | grep mdev return nothing. There is no directory /sys/class/mdev_bus. I tried a full modload: modprobe nvidia_vgpu_vfio nvidia vfio_mdev mdev vfio_iommu_type1 vfio nvidia nvidia-modeset nvidia-drm nvidia-uvm vfio-pci. But it does nothing. Why did my kernel think the P4 is not mdev-compatible any more ? How can I check that ? I think it break when upgrading my kernel from kernel-3.10.0-1062.1.2.el7.x86_64 to kernel-3.10.0-1062.4.1.el7.x86_64. I tried with both the nouveau driver and the nvidia driver.

2 2

Re: Do I need to use self hosted engine with a GlusterFs three node setup
by Strahil 13 Nov '19

13 Nov '19

I remember creating my oVirt setup in 2 stages: 1. Using cockpit to deploy the gluster cluster 2. Using cockpit to deploy HCI on the created gluster clustet. If that's not changed you can only deploy the gluster clustet, thrn deploy the engine somewhere else and then connect the engine (add storage domain) to the gluster cluster, which also can be your oVirt compute nodes (making them at the end HyperConverged oVirt Cluster). Of course , that was an year ago - so it could be different. Best Regards, Strahil NikolovOn Nov 13, 2019 14:16, donagh.moran(a)oracle.com wrote: > > Hi Vojtech > > Thanks for the info, I have been looking for a method of creating the gluster cluster via cockpit on one of my three hosts but the only way I can see is via the hosted engine setup. Is it a case that we need to configure the hosts to use gluster storage with the cli commands prior to adding it to a pre-existing non hosted engine? > > Donagh > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IIEY3Z3GDGH4V…

1 0

[ANN] oVirt 4.3.7 Third Release Candidate is now available for testing
by Sandro Bonazzola 13 Nov '19

13 Nov '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.7 Third Release Candidate for testing, as of November 13th, 2019. This update is a release candidate of the seventh in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) * oVirt Node 4.3 (available for x86_64 only) has been built consuming CentOS 7.7 Release See the release notes [1] for known issues, new features and bugs fixed. While testing this release candidate please note that oVirt node now includes: - ansible 2.9.0 - GlusterFS 6.6 Notes: - oVirt Appliance is already available - oVirt Node is already available Additional Resources: * Read more about the oVirt 4.3.7 release highlights: http://www.ovirt.org/release/4.3.7/ * 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.3.7/ [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 3

Re: Do I need to use self hosted engine with a GlusterFs three node setup
by Strahil 13 Nov '19

13 Nov '19

You don't need to host the engine on the gluster cluster. I know people you have hosted the engine on a bare metal (pacemaker cluster) , so feel free to experiment. The only requirement is that tge engine needs to be able to communicate with the hosts (I'm not sure if layer 2 connectivity is necessary). Best Regards, Strahil Nikolov Best Regards, Strahil NikolovOn Nov 12, 2019 16:00, donagh.moran(a)oracle.com wrote: > > Every piece of documentation I read regarding the setup of Gluster seems to suggest using at least one of the the nodes to host the engine. Is this a requirement of can I use an engine that is deployed on a VM on another server in the same network? Any info would be much appreciated. > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/LN4CTUMQSTJX4…

2 1

Re: restore
by suporte＠logicworks.pt 13 Nov '19

13 Nov '19

yes you are right. I miss that. Sorry Thanks a lot De: "Staniforth, Paul" <P.Staniforth(a)leedsbeckett.ac.uk> Para: suporte(a)logicworks.pt, "users" <users(a)ovirt.org> Enviadas: Terça-feira, 12 De Novembro de 2019 17:49:18 Assunto: Re: restore As you did a full backup including the data warehouse you need engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --provision-dwh-db --restore-permissions see https://www.ovirt.org/documentation/admin-guide/chap-Backups_and_Migration.… Backups and Migration | oVirt Chapter 12: Backups and Migration Backing Up and Restoring the oVirt Engine Backing up oVirt Engine - Overview. Use the engine-backup tool to take regular backups of the oVirt Engine. The tool backs up the engine database and configuration files into a single file and can be run without interrupting the ovirt-engine service.. Syntax for the engine-backup Command www.ovirt.org Regards, Paul S. From: suporte(a)logicworks.pt <suporte(a)logicworks.pt> Sent: 12 November 2019 17:39 To: users <users(a)ovirt.org> Subject: [ovirt-users] restore Hi, I did a backup of engine like this # engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name In a newly installed machine try to restore it: # yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm # yum update # yum install ovirt-engine # engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --restore-permissions but get this error: Start of engine-backup with mode 'restore' scope: all archive file: file_name log file: log_file_name Preparing to restore: - Unpacking file 'file_name' Restoring: - Files Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' Restoring: FATAL: Can't connect to database 'ovirt_engine_history'. Please see '/usr/bin/engine-backup --help'. I'm running ovirt Version:4.3.4.3-1.el7 If I run # engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --no-restore-permissions still the same error Any idea? Many Thanks -- Jose Ferradeira http://www.logicworks.pt To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/

2 2

External networks issue after upgrading to 4.3.6
by ada per 12 Nov '19

12 Nov '19

After upgrading to the latest stable version the external networks lost all functionality. Under providers-->ovn-network-provider the test runs successfully. But when im creating an external provider network, attaching it to a router as a LAN setting up dhcp lease it is not reachable from other VMs in the same network. Hosts and hosted engine can't seem to ping it either. I tried disabling firewalls on both hosted engines, VMs and host and still nothing. When configuring Logical networks or VLANs they work perfectly tje one problem is the external networks. I have another environment running on a previous version of ovirt and it works perfectly there. I think its a bug. Thanks for your help

4 16

Re: Migrate VM from oVirt to oVirt
by Strahil 12 Nov '19

12 Nov '19

You will need a storage that will be your 'USB stick' . For example you can attach NFS-based storage domain, migrate the disks of the VM to that storage. Then power off that VM, set the storage to maintenance and then detach it from first oVirt engine. Then you attach and activate that NFS storage in your new oVirt engine. After Activation, there will be an 'Import VMs/templates' tab . Click on it and import the VM in a cluster. Last step is to migrate your VM's disks from that NFS to their permanent storage. Best Regards, Strahil NikolovOn Nov 12, 2019 04:39, adrianquintero(a)gmail.com wrote: > > Hello, > What would be the procedure to migrate a VM from oVirt to oVirt? > > Migrate from oVirt 4.2 running on Site A to oVirt 4.3 Site B. > > thanks! > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/4OTOXXGYWL2SM…

1 0

restore
by suporte＠logicworks.pt 12 Nov '19

12 Nov '19

Hi, I did a backup of engine like this # engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name In a newly installed machine try to restore it: # yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm # yum update # yum install ovirt-engine # engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --restore-permissions but get this error: Start of engine-backup with mode 'restore' scope: all archive file: file_name log file: log_file_name Preparing to restore: - Unpacking file 'file_name' Restoring: - Files Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' Restoring: FATAL: Can't connect to database 'ovirt_engine_history'. Please see '/usr/bin/engine-backup --help'. I'm running ovirt Version:4.3.4.3-1.el7 If I run # engine-backup --mode=restore --file=file_name --log=log_file_name --provision-db --no-restore-permissions still the same error Any idea? Many Thanks -- Jose Ferradeira http://www.logicworks.pt

2 1

Fwd: [moVirt] Do I need to use a self hosted engine with a GlusterFs three node setup
by Tomas Jelinek 12 Nov '19

12 Nov '19

forwarding to the correct list ---------- Forwarded message --------- From: <donagh.moran(a)oracle.com> Date: Tue, Nov 12, 2019 at 3:03 PM Subject: [moVirt] Do I need to use a self hosted engine with a GlusterFs three node setup To: <movirt(a)ovirt.org> Every piece of documentation I read regarding the setup of Gluster seems to suggest using at least one of the the nodes to host the engine. Is this a requirement of can I use an engine that is deployed on a VM on another server in the same network? Any info would be much appreciated. _______________________________________________ moVirt mailing list -- movirt(a)ovirt.org To unsubscribe send an email to movirt-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/movirt@ovirt.org/message/7ZA5XNMLS3QQ…

1 0

Does ovirt support sshfs?
by TomK 12 Nov '19

12 Nov '19

Hi All, Does ovirt support sshfs for mount locally accessible LUN's instead of NFS? -- Thx, TK.

2 1

SHE with multipath on multiple iSCSI targets
by Francesco Castellano 12 Nov '19

12 Nov '19

Dear sirs, we're trying to install an SHE oVirt 4.3.6 using an iSCSI SAN that provides us multiple targets (8) over 4 different portals. Following 5.1 of "RHV installation using Cockpit" we set up iscsi and multipath ahead with a 90GB LUN to be used for the engine VM. Unfortunately, even if the node OS sees correctly the LUN, e.g.: # multipath -ll > 36000d31004235a000000000000000018 dm-34 COMPELNT,Compellent Vol > size=90G features='1 queue_if_no_path' hwhandler='0' wp=rw > `-+- policy='service-time 0' prio=1 status=active > |- 16:0:0:3 sdu 65:64 active ready running > |- 24:0:0:3 sdt 65:48 active ready running > |- 17:0:0:3 sds 65:32 active ready running > |- 25:0:0:3 sdv 65:80 active ready running > |- 15:0:0:3 sdx 65:112 active ready running > |- 29:0:0:3 sdw 65:96 active ready running > |- 28:0:0:3 sdy 65:128 active ready running > |- 20:0:0:3 sdz 65:144 active ready running > `- 21:0:0:3 sdaa 65:160 active ready running # lsscsi -ist | grep 36000d31004235a000000000000000018 > [15:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a43,t,0x0 > /dev/sdx 36000d31004235a000000000000000018 96.6GB > [16:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a43,t,0x0 > /dev/sdu 36000d31004235a000000000000000018 96.6GB > [17:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a44,t,0x0 > /dev/sds 36000d31004235a000000000000000018 96.6GB > [20:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235243,t,0x0 > /dev/sdz 36000d31004235a000000000000000018 96.6GB > [21:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235244,t,0x0 > /dev/sdaa 36000d31004235a000000000000000018 96.6GB > [24:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a48,t,0x0 > /dev/sdt 36000d31004235a000000000000000018 96.6GB > [25:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235a49,t,0x0 > /dev/sdv 36000d31004235a000000000000000018 96.6GB > [28:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235248,t,0x0 > /dev/sdy 36000d31004235a000000000000000018 96.6GB > [29:0:0:3] disk iqn.2002-03.com.compellent:5000d31004235249,t,0x0 > /dev/sdw 36000d31004235a000000000000000018 96.6GB > # iscsiadm -m session | grep -E '[a2]4[3489]' | sort -k 3.8 > tcp: [1] 10.201.204.10:3260,0 iqn.2002-03.com.compellent:5000d31004235a43 > (non-flash) > tcp: [2] 10.201.204.10:3260,0 iqn.2002-03.com.compellent:5000d31004235a43 > (non-flash) > tcp: [3] 10.201.204.10:3260,0 iqn.2002-03.com.compellent:5000d31004235a44 > (non-flash) > tcp: [6] 10.201.204.20:3260,0 iqn.2002-03.com.compellent:5000d31004235243 > (non-flash) > tcp: [7] 10.201.204.20:3260,0 iqn.2002-03.com.compellent:5000d31004235244 > (non-flash) > tcp: [10] 10.201.205.10:3260,0 > iqn.2002-03.com.compellent:5000d31004235a48 (non-flash) > tcp: [11] 10.201.205.10:3260,0 > iqn.2002-03.com.compellent:5000d31004235a49 (non-flash) > tcp: [14] 10.201.205.20:3260,0 > iqn.2002-03.com.compellent:5000d31004235248 (non-flash) > tcp: [15] 10.201.205.20:3260,0 > iqn.2002-03.com.compellent:5000d31004235249 (non-flash) > during the engine deploy neither via cockpit nor with "hosted-engine --deploy" it was able to see any LUN. Having a lot of portals (4) and each having 4 targets (two of which being independents path to the LUN), we chose a portal to discover, it proposed us 4 targets, and we had to choose a target to log in, but in the end, no LUN was proposed. After a few attempts, we found that, if we logged out from any targets (and clean up the open-iscsi database), after the login in an appropriate target, the installer proposed us the LUN, and we successfully deployed the SHE. But unfortunately, such an installation doesn't track effectively all the 8 paths over 8 different targets, but just the one chosen during the installation (this is different, for example, with respect to other LUNs for data domains that we attached afterwards). Thus we miss the HA we aimed to for the engine data domain. I said this, because when I ask for /ovirt-engine/api/storagedomains, whilst a second LUN has 8 children with different targets below storage_domain/${another data domain}/storage/volume_group/logical_units/logical_unit/, for the hosted_storage I just have one. My questions are: a) is there a way to add the other targets/paths consistently (even through the REST interface)? b) is there another installation, or recovery, procedure to get the engine data domain in high availability on our iSCSI topology? Thank you so much for your suggestions, they are really appreciated, Best regards, Francesco Castellano

3 5

Quick question regarding FQDN
by Christian Reiss 12 Nov '19

12 Nov '19

Hey folks, for production use quality it is recommended to have backend (storage) and front end seperated. Let' assume: - 85.0.0.0/24 public IP block - 10.100.0.0/24 private IPs for DC internal usage - 10.200.0.0/24 private IPs for storage only LAN and running, as per recommendation 3 nodes: - node01: - fqdn: node01.dc-example.com - fqdn storage: node02.storage.example.com - no public IP - 10.100.0.1 primary IP - 10.200.0.1 storage IP - node02: - fqdn: node02.dc-example.com - fqdn storage: node02.storage.example.com - no public IP - 10.100.0.2 primary IP - 10.200.0.2 storage IP - node03: - fqdn: node03.dc-example.com - fqdn storage: node02.storage.example.com - no public IP - 10.100.0.3 primary IP - 10.200.0.3 storage IP The storage network is its own physical network with 10gig that only connects those three servers. How can I specify which IP to use for storage, which for frontend traffic? I am assuming this as the controller and all admins should be able to reach the nodes via frontend, which is not the storage one. Okay, I am lost. Whats the real solution here? Or is "frontend" no-ip, just VM traffic and "backend" is the 10gig storage "Only" where all the FQDN reside? Thanks for clarification, -Chris. -- Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon support(a)alpha-labs.net \ / Campaign X against HTML WEB alpha-labs.net / \ in eMails GPG Retrieval https://gpg.christian-reiss.de GPG ID ABCD43C5, 0x44E29126ABCD43C5 GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5 "It's better to reign in hell than to serve in heaven.", John Milton, Paradise lost.

4 3

I want to configure an web server
by Istiaque Islam 12 Nov '19

12 Nov '19

Hi there, I have installed oVirt on a server and related ISO and Data domains. I can create Virtual Machines and that machine get access to internet to download things. What I want to do now : 1. create an web server using centos and access that webserver from anywhere with internet connection 2. Then I shall configure a domain name for that webserver hosted in oVirt Virtual Machine. My Question : How to configure the virtual machine in oVirt so that when I enter my specified domain name/IP it will hit that particular virtual machine? As it is a virtual machine, it will not get any public IP, so how should i configure the virtual machine set up so that it can be used as an web server. Thanks in advance. -- With Regards, *Mohammed Istiaque Islam* *Contact no *: *+8801745723593* Email : jisan6347(a)gmail.com LinkedIn Profile : Profile_Linkedin_Istiaque <http://www.linkedin.com/in/mohammed-istiaque-islam-59541866>

3 2

Re: When I log in ovirt-engine , it show "Unable to log in because the user account is disabled or locked. Contact the system administrator."
by wangyu13476969128＠126.com 12 Nov '19

12 Nov '19

It's OK now. Thank you very much !

1 0

Re: When I log in ovirt-engine , it show "Unable to log in because the user account is disabled or locked. Contact the system administrator."
by Strahil 11 Nov '19

11 Nov '19

Login via ssh on the engine and unlock your user via ovirt-aaa-jdbc-tool tool. Best Regards, Strahil NikolovOn Nov 11, 2019 11:05, wangyu13476969128(a)126.com wrote: > > When I log in ovirt-engine，the username and password is correct. > But the error show "Unable to log in because the user account is disabled or locked. Contact the system administrator." > How can I solve this problem ? > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TGLVOMEDV2TGK…

1 0

Re: After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5?
by Yedidyah Bar David 11 Nov '19

11 Nov '19

On Mon, Nov 11, 2019 at 12:26 PM Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > > Thanks, > I should have been clearer, what I meant was could you install 4.3.5 and restore to that, then run engine-setup --offline? Of course, this should work. The only point is that once 4.3.6 is released, it's not that easy to install 4.3.5, because yum generally tries to install the latest versions of stuff - and in theory, there might be issues with installing stuff from 4.3.6 repo with a 4.3.5 engine, so if you want an exact replicate of a 4.3.5 engine, you have to check all relevant packages, not just the engine. > > Regards, > Paul S. > ________________________________ > From: Yedidyah Bar David <didi(a)redhat.com> > Sent: 11 November 2019 10:19 > To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> > Cc: wangyu13476969128(a)126.com <wangyu13476969128(a)126.com>; users <users(a)ovirt.org> > Subject: Re: [ovirt-users] Re: After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5? > > On Mon, Nov 11, 2019 at 12:12 PM Staniforth, Paul > <P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > > > I haven't tried it but doesn't engine-setup --offline stop it upgrading minor releases. > > It prevents only the packager component. > > If you already have 4.3.6 installed, which was the original question, > then engine-setup will still update the database schema. And if it > didn't, the 4.3.6 engine might fail working correctly with a 3.4.5.5 > database. In particular: > > The documentation for engine-backup always stated that you must run > engine-setup immediately after restore. But at some points in time, > and under certain conditions, this was actually optional. You could > have done a restore, and immediately start the engine, and it would > have worked. But this isn't the case if your restored db is older than > the installed engine. Then, you must run engine-setup before starting > the engine. > > Best regards, > > > > > Regards, > > Paul S. > > ________________________________ > > From: Yedidyah Bar David <didi(a)redhat.com> > > Sent: 11 November 2019 07:57 > > To: wangyu13476969128(a)126.com <wangyu13476969128(a)126.com> > > Cc: users <users(a)ovirt.org> > > Subject: [ovirt-users] Re: After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5? > > > > On Tue, Oct 29, 2019 at 11:55 AM <wangyu13476969128(a)126.com> wrote: > > > > > > The current version of ovirt-engine in production environment is 4.3.5.5. > > > In order to prevent the ovirt-engine machine from being down, the management interface cannot be used, according to the relevant link: > > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fovirt.org… > > > > > > I backed it up using the command: > > > engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name > > > > > > I have prepared another machine as a spare machine. Once the ovirt-engine is down in the production environment, the standby machine can be UP and the standby machine can manage the ovirt-nodes. > > > > > > According to the relevant links: > > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fovirt.org… > > > > > > The ovirt-engine is installed on the standby machine. > > > > > > After I have executed these three commands: > > > 1. yum install https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fresources.… > > > > > > 2. yum update > > > > > > 3. yum install ovirt-engine > > > > > > I found that the ovirt-engine version of the standby machine is 4.3.6 > > > > > > So my question is: > > > > > > 1. The ovirt-engine version of the standby machine is 4.3.6, and the production environment ovirt-engine version is 4.3.5.5, which command is used on the production environment ovirt-engine machine: > > > engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name > > > > > > Files obtained after using the backup command on the ovirt-engine in the production environment are restored using these two files under the standby computer. Will the information on the ovirt-engine management interface of the standby computer be consistent with the ovirt-engine of the production environment (eg data center, host, virtual machine, etc.)? > > > > In principle it should be ok. After you restore with above command, > > you should run 'engine-setup', and this will update your restored > > database schema to 4.3.6. > > This is not routinely tested explicitly, though, but I expect that > > people often do this, perhaps even unknowingly, when they restore from > > a backup taken with a somewhat-old version. > > > > > > > > 2. Can the ovirt-engine of the standby machine be installed with version 4.3.5.5? How do I need to modify the following three commands to get the backup machine to install the version 4.3.5.5? > > > 1. yum install https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fresources.… > > > 2. yum update > > > 3. yum install ovirt-engine > > > > In theory you can change last one to 'yum install > > ovirt-engine-4.3.5.5'. I didn't try that, and you are quite likely to > > run into complex dependencies you'll have to satisfy by yourself. > > > > I think the best solution for you, if you care about active and > > standby to be identical, is to upgrade your active one as well, and > > keep them same version going forward. > > > > I'd also like to note that maintaining a standby engine and using it > > the way you intend to, is not in the scope of oVirt. People do similar > > things, but have to manually work around this and be careful. One very > > important issue is that if for any reason you allow both of them to be > > up at the same time, and manage the same hosts, they will not know > > about each other, and you'll see lots of confusion and errors. > > > > You might also want to check: > > > > 1. Hosted-engine setup with more than one host as hosted-engine host. > > There, you only have a single engine vm, but it can run on any of your > > hosts. You still have a single VM disk/image, and if that's corrupted, > > you have no HA and have to somehow reinstall/restore/etc. > > > > 2. https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > > > > Best regards, > > -- > > Didi > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org > > To unsubscribe send an email to users-leave(a)ovirt.org > > Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > > oVirt Code of Conduct: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > > List Archives: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi… > > To view the terms under which this email is distributed, please go to:- > > http://leedsbeckett.ac.uk/disclaimer/email/ > > > > -- > Didi > > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/ -- Didi

1 0

Guest Agent Warning
by ccesario＠blueit.com.br 11 Nov '19

11 Nov '19

Hello, Does someone has idea about fix/remove the warning message "The latest guest agent needs to be installed and running on the guest" from my VMs ? I already has the qemu agent running and updated on VMS. I already tried restart the VM and HOST but the warning persist. Any tip? My Env. ====== https://pasteboard.co/IDsJZE1.png Warning message ============== https://pasteboard.co/IDsLcNS.png Qemu agent ========== https://pasteboard.co/IDsMmdPp.png Best regards Carlos

4 9

Re: After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5?
by Yedidyah Bar David 11 Nov '19

11 Nov '19

On Mon, Nov 11, 2019 at 12:12 PM Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> wrote: > > I haven't tried it but doesn't engine-setup --offline stop it upgrading minor releases. It prevents only the packager component. If you already have 4.3.6 installed, which was the original question, then engine-setup will still update the database schema. And if it didn't, the 4.3.6 engine might fail working correctly with a 3.4.5.5 database. In particular: The documentation for engine-backup always stated that you must run engine-setup immediately after restore. But at some points in time, and under certain conditions, this was actually optional. You could have done a restore, and immediately start the engine, and it would have worked. But this isn't the case if your restored db is older than the installed engine. Then, you must run engine-setup before starting the engine. Best regards, > > Regards, > Paul S. > ________________________________ > From: Yedidyah Bar David <didi(a)redhat.com> > Sent: 11 November 2019 07:57 > To: wangyu13476969128(a)126.com <wangyu13476969128(a)126.com> > Cc: users <users(a)ovirt.org> > Subject: [ovirt-users] Re: After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5? > > On Tue, Oct 29, 2019 at 11:55 AM <wangyu13476969128(a)126.com> wrote: > > > > The current version of ovirt-engine in production environment is 4.3.5.5. > > In order to prevent the ovirt-engine machine from being down, the management interface cannot be used, according to the relevant link: > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fovirt.org… > > > > I backed it up using the command: > > engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name > > > > I have prepared another machine as a spare machine. Once the ovirt-engine is down in the production environment, the standby machine can be UP and the standby machine can manage the ovirt-nodes. > > > > According to the relevant links: > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fovirt.org… > > > > The ovirt-engine is installed on the standby machine. > > > > After I have executed these three commands: > > 1. yum install https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fresources.… > > > > 2. yum update > > > > 3. yum install ovirt-engine > > > > I found that the ovirt-engine version of the standby machine is 4.3.6 > > > > So my question is: > > > > 1. The ovirt-engine version of the standby machine is 4.3.6, and the production environment ovirt-engine version is 4.3.5.5, which command is used on the production environment ovirt-engine machine: > > engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name > > > > Files obtained after using the backup command on the ovirt-engine in the production environment are restored using these two files under the standby computer. Will the information on the ovirt-engine management interface of the standby computer be consistent with the ovirt-engine of the production environment (eg data center, host, virtual machine, etc.)? > > In principle it should be ok. After you restore with above command, > you should run 'engine-setup', and this will update your restored > database schema to 4.3.6. > This is not routinely tested explicitly, though, but I expect that > people often do this, perhaps even unknowingly, when they restore from > a backup taken with a somewhat-old version. > > > > > 2. Can the ovirt-engine of the standby machine be installed with version 4.3.5.5? How do I need to modify the following three commands to get the backup machine to install the version 4.3.5.5? > > 1. yum install https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fresources.… > > 2. yum update > > 3. yum install ovirt-engine > > In theory you can change last one to 'yum install > ovirt-engine-4.3.5.5'. I didn't try that, and you are quite likely to > run into complex dependencies you'll have to satisfy by yourself. > > I think the best solution for you, if you care about active and > standby to be identical, is to upgrade your active one as well, and > keep them same version going forward. > > I'd also like to note that maintaining a standby engine and using it > the way you intend to, is not in the scope of oVirt. People do similar > things, but have to manually work around this and be careful. One very > important issue is that if for any reason you allow both of them to be > up at the same time, and manage the same hosts, they will not know > about each other, and you'll see lots of confusion and errors. > > You might also want to check: > > 1. Hosted-engine setup with more than one host as hosted-engine host. > There, you only have a single engine vm, but it can run on any of your > hosts. You still have a single VM disk/image, and if that's corrupted, > you have no HA and have to somehow reinstall/restore/etc. > > 2. https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > > Best regards, > -- > Didi > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > oVirt Code of Conduct: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > List Archives: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi… > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/ -- Didi

2 1

Supporting larger than 8TiB Lun's iSCSI RHV/oVirt
by Green, Jacob Allen /C 11 Nov '19

11 Nov '19

I have a question regarding the information in the following screenshot. According to https://access.redhat.com/articles/906543 there is an 8TiB limit I assume this is per LUN? Also if I want to go past 8TiB per LUN is there some configuration I need to edit somewhere? And is there a problem with going past 8TiB per LUN? I think it more manageable to simply increase LUN sizes if you have the storage, instead of adding additional LUN’s to your storage domain, however I may not fully understand the problems with increasing LUN sizes. Thank you. [cid:image001.png@01D5948E.D0101740] Jacob.

2 1

After importing the ovirt-engine 4.3.5 backup file into ovirt-engine 4.3.6, will the information of the ovirt-engine 4.3.6 management interface be the same as ovirt-engine 4.3.5?
by wangyu13476969128＠126.com 11 Nov '19

11 Nov '19

The current version of ovirt-engine in production environment is 4.3.5.5. In order to prevent the ovirt-engine machine from being down, the management interface cannot be used, according to the relevant link: https://ovirt.org/documentation/admin-guide/chap-Backups_and_Migration.html I backed it up using the command: engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name I have prepared another machine as a spare machine. Once the ovirt-engine is down in the production environment, the standby machine can be UP and the standby machine can manage the ovirt-nodes. According to the relevant links: https://ovirt.org/documentation/install-guide/chap-Installing_oVirt.html The ovirt-engine is installed on the standby machine. After I have executed these three commands: 1. yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm 2. yum update 3. yum install ovirt-engine I found that the ovirt-engine version of the standby machine is 4.3.6 So my question is: 1. The ovirt-engine version of the standby machine is 4.3.6, and the production environment ovirt-engine version is 4.3.5.5, which command is used on the production environment ovirt-engine machine: engine-backup --scope=all --mode=backup --file=file_name --log=log_file_name Files obtained after using the backup command on the ovirt-engine in the production environment are restored using these two files under the standby computer. Will the information on the ovirt-engine management interface of the standby computer be consistent with the ovirt-engine of the production environment (eg data center, host, virtual machine, etc.)? 2. Can the ovirt-engine of the standby machine be installed with version 4.3.5.5? How do I need to modify the following three commands to get the backup machine to install the version 4.3.5.5? 1. yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm 2. yum update 3. yum install ovirt-engine

3 2

When I log in ovirt-engine , it show "Unable to log in because the user account is disabled or locked. Contact the system administrator."
by wangyu13476969128＠126.com 11 Nov '19

11 Nov '19

When I log in ovirt-engine，the username and password is correct. But the error show "Unable to log in because the user account is disabled or locked. Contact the system administrator." How can I solve this problem ?

2 1

Long post about gluster issue after 6.5 to 6.6 upgrade and recovery steps
by Strahil Nikolov 10 Nov '19

10 Nov '19

Hello Colleagues, I want to share my experience and especially how I have recovered after a situation where gluster refuses to heal several files of my oVirt Lab. Most probably the situation was caused by the fact that I didn't check if all files were healed before I started the upgrade on the next node , which in a 'replica 2 arbiter1' setup has caused multiple files missing/conflicting and heal fails to happen. Background:1. I have powered off my HostedEngine VM and made a snapshot of the gluster volume2. Started the update , but without screen - I messed it up and decided to revert from the snapshot3. Powered off the volume , restored from snapshot and then started (and again snapshoted the volume)4. Upgrade of the HostedEngine was successfull5. Upgraded the arbiter (ovirt3)6. I forgot to check the heal status on the arbiter and upgraded ovirt1/gluster1 (which maybe was the reason for the issue)7. After gluster1 was healed I saw that some files are left for healing , but expected it will finish till ovirt2/gluster2 is patched8. Sadly my assumption was not right and after the reboot of ovirt2/gluster2 I noticed that some files never heal. Symptoms:2 files per volume never heal (used 'full' mode) even after I 'stat'-ed every file/dir in the volume.Ovirt Dashboard reported multiple errors (50+) that it cannot update the OVF metadata for volume/VM. Here are my notes while I was recovering from the situation. As this is my LAB, I shutdown all VMs (including the HostedEngine) as downtime was not an issue: Heals never complete: # gluster volume heal data_fast4 info Brick gluster1:/gluster_bricks/data_fast4/data_fast4 Status: Connected Number of entries: 0 Brick gluster2:/gluster_bricks/data_fast4/data_fast4 <gfid:d21a6512-eaf6-4859-90cf-eeef2cc0cab8> <gfid:95bc2cd2-8a1e-464e-a384-6b128780d370> Status: Connected Number of entries: 2 Brick ovirt3:/gluster_bricks/data_fast4/data_fast4 <gfid:d21a6512-eaf6-4859-90cf-eeef2cc0cab8> <gfid:95bc2cd2-8a1e-464e-a384-6b128780d370> Status: Connected Number of entries: 2 Mount to get the gfid to path relationship: mount -t glusterfs -o aux-gfid-mount gluster1:/data_fast4 /mnt # getfattr -n trusted.glusterfs.pathinfo -e text /mnt/.gfid/d21a6512-eaf6-4859-90cf-eeef2cc0cab8 getfattr: Removing leading '/' from absolute path names # file: mnt/.gfid/d21a6512-eaf6-4859-90cf-eeef2cc0cab8 trusted.glusterfs.pathinfo="(<REPLICATE:data_fast4-replicate-0> <POSIX(/gluster_bricks/data_fast4/data_fast4):ovirt2.localdomain:/gluster_bricks/data_fast4/data_fast4/.glusterfs/d2/1a/d21a651 2-eaf6-4859-90cf-eeef2cc0cab8> <POSIX(/gluster_bricks/data_fast4/data_fast4):ovirt3.localdomain:/gluster_bricks/data_fast4/data_fast4/.glusterfs/d2/1a/d21a6512-eaf6-4859-90cf-eeef2cc0cab8>)" The local brick (that is supposed to be healed) is missing some data: # ls -l /gluster_bricks/data_fast4/data_fast4/.glusterfs/d2/1a/d21a6512-eaf6-4859-90cf-eeef2cc0cab8 ls: няма достъп до /gluster_bricks/data_fast4/data_fast4/.glusterfs/d2/1a/d21a6512-eaf6-4859-90cf-eeef2cc0cab8: Няма такъв файл или директория Remote is OK: # ssh gluster2 'ls -l /gluster_bricks/data_fast4/data_fast4/.glusterfs/d2/1a/d21a6512-eaf6-4859-90cf-eeef2cc0cab8' -rw-r--r--. 2 vdsm kvm 436 9 ное 19,34 /gluster_bricks/data_fast4/data_fast4/.glusterfs/d2/1a/d21a6512-eaf6-4859-90cf-eeef2cc0cab8 Arbiter is also OK: # ssh ovirt3 'ls -l /gluster_bricks/data_fast4/data_fast4/.glusterfs/d2/1a/d21a6512-eaf6-4859-90cf-eeef2cc0cab8' -rw-r--r--. 2 vdsm kvm 0 9 ное 19,34 /gluster_bricks/data_fast4/data_fast4/.glusterfs/d2/1a/d21a6512-eaf6-4859-90cf-eeef2cc0cab8 Rsync the file/directory from a good brick to broken one: # rsync -avP gluster2:/gluster_bricks/data_fast4/data_fast4/.glusterfs/d2/1a/ /gluster_bricks/data_fast4/data_fast4/.glusterfs/d2/1a/ # ls -l /gluster_bricks/data_fast4/data_fast4/.glusterfs/d2/1a/d21a6512-eaf6-4859-90cf-eeef2cc0cab8 -rw-r--r--. 1 vdsm kvm 436 9 ное 19,34 /gluster_bricks/data_fast4/data_fast4/.glusterfs/d2/1a/d21a6512-eaf6-4859-90cf-eeef2cc0cab8 After a full heal we see our problematic file: # gluster volume heal data_fast4 full Launching heal operation to perform full self heal on volume data_fast4 has been successful Use heal info commands to check status. # gluster volume heal data_fast4 info Brick gluster1:/gluster_bricks/data_fast4/data_fast4 Status: Connected Number of entries: 0 Brick gluster2:/gluster_bricks/data_fast4/data_fast4 /578bca3d-6540-41cd-8e0e-9e3047026484/images/58e197a6-12df-4432-a643-298d40e44130/535ec7f7-f4d1-4d1e-a988-c1e95b4a38ca.meta Status: Connected Number of entries: 1 Brick ovirt3:/gluster_bricks/data_fast4/data_fast4 /578bca3d-6540-41cd-8e0e-9e3047026484/images/58e197a6-12df-4432-a643-298d40e44130/535ec7f7-f4d1-4d1e-a988-c1e95b4a38ca.meta Status: Connected Number of entries: 1 This time the file is missing on both gluster1 (older version) and arbiter: # cat /gluster_bricks/data_fast4/data_fast4/578bca3d-6540-41cd-8e0e-9e3047026484/images/58e197a6-12df-4432-a643-298d40e44130/535ec7f7-f4d1-4d1e-a988-c1e95b4a38ca.meta CTIME=1558265783 DESCRIPTION={"Updated":true,"Size":256000,"Last Updated":"Sat Nov 09 19:24:08 EET 2019","Storage Domains":[{"uuid":"578bca3d-6540-41cd-8e0e-9e3047026484"}],"Disk Description":"OVF_STORE"} DISKTYPE=OVFS DOMAIN=578bca3d-6540-41cd-8e0e-9e3047026484 FORMAT=RAW GEN=0 IMAGE=58e197a6-12df-4432-a643-298d40e44130 LEGALITY=LEGAL MTIME=0 PUUID=00000000-0000-0000-0000-000000000000 SIZE=262144 TYPE=PREALLOCATED VOLTYPE=LEAF EOF # ssh gluster2 cat /gluster_bricks/data_fast4/data_fast4/578bca3d-6540-41cd-8e0e-9e3047026484/images/58e197a6-12df-4432-a643-298d40e44130/535ec7f7-f4d1-4d1e-a988-c1e95b4a38ca.meta CTIME=1558265783 DESCRIPTION={"Updated":true,"Size":256000,"Last Updated":"Sat Nov 09 19:34:33 EET 2019","Storage Domains":[{"uuid":"578bca3d-6540-41cd-8e0e-9e3047026484"}],"Disk Description":"OVF_STORE"} DISKTYPE=OVFS DOMAIN=578bca3d-6540-41cd-8e0e-9e3047026484 FORMAT=RAW GEN=0 IMAGE=58e197a6-12df-4432-a643-298d40e44130 LEGALITY=LEGAL MTIME=0 PUUID=00000000-0000-0000-0000-000000000000 SIZE=262144 TYPE=PREALLOCATED VOLTYPE=LEAF EOF # ssh ovirt3 cat /578bca3d-6540-41cd-8e0e-9e3047026484/images/58e197a6-12df-4432-a643-298d40e44130/535ec7f7-f4d1-4d1e-a988-c1e95b4a38ca.meta cat: /578bca3d-6540-41cd-8e0e-9e3047026484/images/58e197a6-12df-4432-a643-298d40e44130/535ec7f7-f4d1-4d1e-a988-c1e95b4a38ca.meta: Няма такъв файл или директория As we miss the same file on both a brick and arbiter we take another approach: First remove on gluster1 the file to another name: # mv /gluster_bricks/data_fast4/data_fast4/578bca3d-6540-41cd-8e0e-9e3047026484/images/58e197a6-12df-4432-a643-298d40e44130/535ec7f7-f4d1-4d1e-a988-c1e95b4a38ca.meta /gluster_bricks/data_fast4 /data_fast4/578bca3d-6540-41cd-8e0e-9e3047026484/images/58e197a6-12df-4432-a643-298d40e44130/535ec7f7-f4d1-4d1e-a988-c1e95b4a38ca.meta_old Then we copy the file from gluster2 (good brick) # rsync -avP gluster2:/gluster_bricks/data_fast4/data_fast4/578bca3d-6540-41cd-8e0e-9e3047026484/images/58e197a6-12df-4432-a643-298d40e44130/535ec7f7-f4d1-4d1e-a988-c1e95b4a38ca.meta /gluster_ bricks/data_fast4/data_fast4/578bca3d-6540-41cd-8e0e-9e3047026484/images/58e197a6-12df-4432-a643-298d40e44130/535ec7f7-f4d1-4d1e-a988-c1e95b4a38ca.meta receiving incremental file list 535ec7f7-f4d1-4d1e-a988-c1e95b4a38ca.meta 436 100% 425.78kB/s 0:00:00 (xfr#1, to-chk=0/1) sent 43 bytes received 571 bytes 1,228.00 bytes/sec total size is 436 speedup is 0.71 Run full heal: # gluster volume heal data_fast4 full Launching heal operation to perform full self heal on volume data_fast4 has been successful Use heal info commands to check status # gluster volume heal data_fast4 info Brick gluster1:/gluster_bricks/data_fast4/data_fast4 Status: Connected Number of entries: 0 Brick gluster2:/gluster_bricks/data_fast4/data_fast4 Status: Connected Number of entries: 0 Brick ovirt3:/gluster_bricks/data_fast4/data_fast4 Status: Connected Number of entries: 0 And ofcourse umount /mnt I did the above for all oVirt Storage domains and rebooted all nodes (simultaneously) after stopping the whole stack. This one should not be neccessary , but I wanted to be sure that after power outage the cluster will be operational again: systemctl stop ovirt-ha-agent ovirt-ha-broker vdsmd supervdsmd sanlock glusterd/usr/share/glusterfs/scripts/stop-all-gluster-processes.sh Verification:After the reboot , I have tried to set each oVirt storage domain in 'Maintenance' which confirms that engine can update the OVMF meta and then set it back to Active. Without downtime , this will not be possible. I hope this long post will help anyone . PS: I have collected some data for some of the files, that I have ommited as this e-mail is very long. Best Regards,Strahil Nikolov

1 0

oVirt orb python3/fedora 31 support
by Baptiste Agasse 08 Nov '19

08 Nov '19

Hi all, I was an happy user of oVirt orb on my laptop to do some testing (New features, foreman integration tests , ansible modules/playbooks/roles tests...) and it worked realy well, thanks guys ! Last week I've upgraded my laptop to fedora 31 and I have to uninstall ovirt-orb/lago related stuff to be able upgrade to this fedora version (related to python2 dependencies packages missing on fedora 31). Is there any planned python3/fedora 31 support for ovirt-orb/lago-ovirt/lago ? If not there is any simple replacement solution to spin up a light ovirt env to this kind of tests ? Have a nice day. Baptiste

2 1

Network usage data report 0%
by ccesario＠blueit.com.br 08 Nov '19

08 Nov '19

Hello, In Administration Portal and VM Portal the all VMs reports 0% network usage. Even the Hosted Ovirt Engine. It is following the screenshost https://pasteboard.co/IE6gvCg.png https://pasteboard.co/IE6hyuUV.png The other metrics are OK, only network that re reporting 0 My env. https://pasteboard.co/IE6i8AO.png Regards Carlos

2 5

Re: oVirt and Netapp question
by Vrgotic, Marko 08 Nov '19

08 Nov '19

Second attempt 😊 From: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com> Date: Monday, 4 November 2019 at 14:01 To: "users(a)ovirt.org" <users(a)ovirt.org> Subject: oVirt and Netapp question Dear oVirt, Few months ago our production environment oVirt with main Shared storage via NFS Netapp is live. We have been deploying VMs with thin provisioned HDD 40GB based template, CentOS 7. The Netapp NFS v4 storage volume is 7TB in size, also Thin Provisioned. First attached screenshot shows the space allocation of the production volume from Netapp side. Is there anyone in oVirt community who would be able to tell me the meaning of the 5.31 TB Over Provisioned Space? [A screenshot of a cell phone Description automatically generated] Second attached is the info of the production volume from oVirt side: [A screenshot of a social media post Description automatically generated] What I want to understand is the way how is oVirt reading the volume usage and Netapp and where is the difference. Is the Over Allocated Space something that is just logically used/reserved and will be intelligently re-allocated/re-used as the actual Data Space Used grows or am I looking at oVIrt actually hitting Critical Space Action Blocker and will have to resize the volume? If there is anyone from Netapp or with good Netapp experience that is able to help understanding the data above better, thank you in advance? Kindly awaiting your reply. ----- kind regards/met vrindelijke groet Marko Vrgotic ActiveVideo

2 5

Re: Quick generic Questions
by Christian Reiss 08 Nov '19

08 Nov '19

Hello all, thank you all for your overwhelming support and information. Waking up to a plethora of answers is a great way to start the day. This goes out to all: Thank you! -Christian. On 07/11/2019 18:38, Staniforth, Paul wrote: > Hello Christian, > > here are some useful links > > https://www.ovirt.org/documentation/gluster-hyperconverged/Gluster_Hypercon… > > > https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infras… > > You need to have at least 1 device for the O/S node install and at least > 1 device for the bricks, so ideally mirror 2 for the O/S and raid the > rest + spare. > > a) Yes the the oVirt node installer has a hyperconverged/gluster mode. > > b) The storage will be shared between all 3 nodes and distributed to > bricks on all 3 nodes. > > c) The VM can start and migrate on / to all nodes if all requirements > are met (mem/cpu/networks) as the storage is shared. > > d) I don't think so > > e) storage network should not die VMs will probably be paused and if > nodes lose access to storage on the master storage domain I think the > engine will restart them depending on fencing policy. > The gluster network should be a separate from the front-end network and > use bonds for resilience. > > f) yes you can add more shared storage domains using ISCSI, FC, NFS > external gluster storage with ISCSI it may be better to use multipath > connections rather than a bond. > > > > Regards, > Paul S. > > > ------------------------------------------------------------------------ > *From:* Christian Reiss <email(a)christian-reiss.de> > *Sent:* 07 November 2019 13:29 > *To:* users <users(a)ovirt.org> > *Subject:* [ovirt-users] Quick generic Questions > Hey folks, > > I am looking at setting up a hyperconverged cluster with 3 nodes (and > oVirt 4.3). Before setting up I have some generic questions that I would > love to get hints or even an answer on. > > First off, the Servers are outfittet with 24 (SSD) drives each in a > HW-RAID. Due to wear-leveling and speed I am looking at RAID10. So I > would end up with one giant sda device. > > a) Partitioning > Using oVirt node installer which will use the full size of /dev/sda is > this still the right solution to Hyperconverged given the gluster issue? > If I understood it correctly gluster is using empty drives or partitions > so a fully utilized drive is of no use here. Does oVirt node installer > have a hyperconverged/ gluster mode? > > b) Storage Location > In this 3 node cluster, creating a VM on node01 will the data for node01 > always end up in the local node01 server? > > c) Starting VMs > Can a VM be migrated or launched from node03 if the data resides on > node01 and node02 (copies 2 with arbiter). > > d) Efficiency / High IO Load > If node01 has high IO Load would additional data be loaded from the > other node which has the copy to even the load? I am aware Virtuozzo > does this. > > e) Storage Network dies > What would happen with node01, node02 and node03 are operational but > only the storage network dies (frontend is still alive as are the nodes). > > f) external isci/ FreeNAS > We have a FreeNAS system with tons of space and fast network > connectivity. Can oVirt handle storage import like remote iscsi target > and run VMs on the ovirt nodes but store data there? > > Thank you for your time to clear this up. > I have found many approaches out there that either are old (oVirt 3) or > even contradict themselves (talk about RAID level...) > > Cheers! > -Christian. > > -- > Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon > support(a)alpha-labs.net \ / Campaign > X against HTML > WEB alpha-labs.net / \ in eMails > > GPG Retrieval > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgpg.chris… > GPG ID ABCD43C5, 0x44E29126ABCD43C5 > GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5 > > "It's better to reign in hell than to serve in heaven.", > John Milton, Paradise lost. > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > oVirt Code of Conduct: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > List Archives: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi… > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/ > -- Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon support(a)alpha-labs.net \ / Campaign X against HTML WEB alpha-labs.net / \ in eMails GPG Retrieval https://gpg.christian-reiss.de GPG ID ABCD43C5, 0x44E29126ABCD43C5 GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5 "It's better to reign in hell than to serve in heaven.", John Milton, Paradise lost.

1 0

Users and VM permissions matrix
by Colin Coe 08 Nov '19

08 Nov '19

Hi all I've been tasked with creating a matrix of users/groups and VMs so we can easily see who has access to what (via SPCIE console). Google has given me a couple of hints but I can get it over the line. --- users_service = connection.system_service().users_service() users = users_service.list() for user in users: username = user.user_name.split('@')[0] # Follow the link to the permissions of the user: perms = connection.follow_link(user.permissions) for perm in perms: if perm.vm: print(username) permissions_service = connection.system_service().permissions_service() print(perm.vm.id) --- The problem is with permissions, the output from above is: --- user1 1b645daf-de26-4f33-9e3b-6a12eadd4618 user2 9c79e763-f78d-4bf9-b8ca-20fe197fd80c user3 f9d00b30-8003-41c3-95a1-10e0c452fa63 user4 1bbadf96-ef95-4ece-b5f3-1fa112aa3571 user5 e9085627-324e-48d3-bc04-52ff7798ddd0 --- I can't work out how to get the actual permissions rather that the ID. Any ideas? Thanks

2 3

Quick generic Questions
by Christian Reiss 07 Nov '19

07 Nov '19

Hey folks, I am looking at setting up a hyperconverged cluster with 3 nodes (and oVirt 4.3). Before setting up I have some generic questions that I would love to get hints or even an answer on. First off, the Servers are outfittet with 24 (SSD) drives each in a HW-RAID. Due to wear-leveling and speed I am looking at RAID10. So I would end up with one giant sda device. a) Partitioning Using oVirt node installer which will use the full size of /dev/sda is this still the right solution to Hyperconverged given the gluster issue? If I understood it correctly gluster is using empty drives or partitions so a fully utilized drive is of no use here. Does oVirt node installer have a hyperconverged/ gluster mode? b) Storage Location In this 3 node cluster, creating a VM on node01 will the data for node01 always end up in the local node01 server? c) Starting VMs Can a VM be migrated or launched from node03 if the data resides on node01 and node02 (copies 2 with arbiter). d) Efficiency / High IO Load If node01 has high IO Load would additional data be loaded from the other node which has the copy to even the load? I am aware Virtuozzo does this. e) Storage Network dies What would happen with node01, node02 and node03 are operational but only the storage network dies (frontend is still alive as are the nodes). f) external isci/ FreeNAS We have a FreeNAS system with tons of space and fast network connectivity. Can oVirt handle storage import like remote iscsi target and run VMs on the ovirt nodes but store data there? Thank you for your time to clear this up. I have found many approaches out there that either are old (oVirt 3) or even contradict themselves (talk about RAID level...) Cheers! -Christian. -- Christian Reiss - email(a)christian-reiss.de /"\ ASCII Ribbon support(a)alpha-labs.net \ / Campaign X against HTML WEB alpha-labs.net / \ in eMails GPG Retrieval https://gpg.christian-reiss.de GPG ID ABCD43C5, 0x44E29126ABCD43C5 GPG fingerprint = 9549 F537 2596 86BA 733C A4ED 44E2 9126 ABCD 43C5 "It's better to reign in hell than to serve in heaven.", John Milton, Paradise lost.

4 3

Re: Quick generic Questions
by Strahil 07 Nov '19

07 Nov '19

On Nov 7, 2019 15:29, Christian Reiss <email(a)christian-reiss.de> wrote: > > Hey folks, > > I am looking at setting up a hyperconverged cluster with 3 nodes (and > oVirt 4.3). Before setting up I have some generic questions that I would > love to get hints or even an answer on. > > First off, the Servers are outfittet with 24 (SSD) drives each in a > HW-RAID. Due to wear-leveling and speed I am looking at RAID10. So I > would end up with one giant sda device. Go with RAID 0 , or RAID5/6 as you will have the same data on all nodes (3 copies in total) . > a) Partitioning > Using oVirt node installer which will use the full size of /dev/sda is > this still the right solution to Hyperconverged given the gluster issue? > If I understood it correctly gluster is using empty drives or partitions > so a fully utilized drive is of no use here. Does oVirt node installer > have a hyperconverged/ gluster mode? The cockpit installer can prepare the gluster infrastructure and then the oVirt cluster > b) Storage Location > In this 3 node cluster, creating a VM on node01 will the data for node01 > always end up in the local node01 server? Nope , all data is replicated on all 3 nodes (or on 2 nodes when using 'replica 2 arbiter1' volumes). > c) Starting VMs > Can a VM be migrated or launched from node03 if the data resides on > node01 and node02 (copies 2 with arbiter). As gluster is a shared storage, the VMs can migrate on any host that has access to the storage (in your case any of the 3 nodes). > d) Efficiency / High IO Load > If node01 has high IO Load would additional data be loaded from the > other node which has the copy to even the load? I am aware Virtuozzo > does this. Gluster Clients (in this case oVirt node) reads from all 3 nodes simultaneously for better I/O. Same is valid for writes. > e) Storage Network dies > What would happen with node01, node02 and node03 are operational but > only the storage network dies (frontend is still alive as are the nodes). Nodes will become unoperational and all VMs will be paused until storage is restored. > f) external isci/ FreeNAS > We have a FreeNAS system with tons of space and fast network > connectivity. Can oVirt handle storage import like remote iscsi target > and run VMs on the ovirt nodes but store data there? Yep. > Thank you for your time to clear this up. > I have found many approaches out there that either are old (oVirt 3) or > even contradict themselves (talk about RAID level...) > > Cheers! > -Christian

1 0

Re: DHCP Client in Guest VM does not work on ovirtmgmt
by Strahil 07 Nov '19

07 Nov '19

All my VMs are using DHCP over ovirtmgmt network. So, yes it should be possible. Are yoiu sure that your hosts' network is in sync ? Best Regards, Strahil NikolovOn Nov 7, 2019 00:21, Dominik Holler <dholler(a)redhat.com> wrote: > > The output of "tcpdump -i ovirtmgmt -pvn port 67 and port 68" in https://pastebin.com/a2DEyL0e looks like the DHCP reply does not reach the ovirtmgmt bridge. > Is the ovirtmgmt bridge / network attachment on the host able to receive configuration by DHCP? > > On Wed, Nov 6, 2019 at 7:08 PM <ccesario(a)blueit.com.br> wrote: >> >> Hi Ales, have you any new tip about this? >> >> regards, >> Carlos >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/BM7J3AREZ2X6Y…

1 0

CPU Pinning topology
by Fabrice Bacchella 07 Nov '19

07 Nov '19

I'm trying to understand the field "CPU Pinning topology" in the "Ressource Allocation" tab, that looks it needed by High Performance VM. I have this hardware: # lscpu Architecture: x86_64 CPU(s): 48 On-line CPU(s) list: 0-47 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 2 NUMA node(s): 2 And I want to run a 22 vCPU vm on it, so no SMT, and 11 vCPU mapped to each socket. The only explanation I found about this field content was here: https://rhv.bradmin.org/ovirt-engine/docs/Virtual_Machine_Management_Guide/… and I can wrap my head around it. Do I need to given explicit mapping for all the 22 vCPU ? And dig in lscpu -e or numactl -H to find how each pCPU is identified ?

2 1

Can ovirt-node support multiple network cards ？
by wangyu13476969128＠126.com 07 Nov '19

07 Nov '19

Can ovirt-node support multiple network cards ？ I download ovirt-node-ng-installer-4.3.5-2019073010.el7.iso from ovirt site. And install on a Dell R730 Server. The version of ovirt-engine is 4.3.5.5. I found that the logic network ovirtmgmt can only point to one network card interface. Can ovirt-node support multiple network cards ？ If yes , please tell me the method.

5 15

Fw: Upgrade 4.2.6 to 4.3.x
by Srivathsa Puliyala 07 Nov '19

07 Nov '19

++ users(a)ovirt.org ________________________________ From: Srivathsa Puliyala Sent: Wednesday, November 6, 2019 11:38 AM To: users-owner(a)ovirt.org <users-owner(a)ovirt.org> Subject: Upgrade 4.2.6 to 4.3.x Hi, I am trying to follow the documentation for the ovirt-engine upgrade (https://www.ovirt.org/documentation/upgrade-guide/appe-Upgrading_to_oVirt_E…) but unable to find the package. Could anyone please help on this? ################# No package ovirt-fast-forward-upgrade available. Error: Nothing to do ################# FYI: ovirt engine is running on CentOS Linux 7 (Core) Thank you. Srivathsa

2 1

Re: Cannot enable maintenance mode
by Martin Perina 07 Nov '19

07 Nov '19

Hi Bruno, how have you rebooted the host? Have you used Stop/Start/Restart functions from Power Management menu in host detail in webadmin? Regards, Martin On Tue, Nov 5, 2019 at 2:29 AM Bruno Martins <bruno.o.martins(a)gfi.world> wrote: > Hi Lukas, > > Thanks for your message! > > In my cluster, I have all the VM's running under "HOST2". > The issue I'm having is that I can't enable maintenance mode on "HOST1", > in order to re-add it to oVirt Manager (SSL certificate replacement stuff). > I did it successfully on "HOST2", but the other one seems to ignore my > actions, with that message in the logs... > > Cheers, > > Bruno > > From: Lukas Svaty <lsvaty(a)redhat.com> > Sent: 16 de outubro de 2019 10:49 > To: Bruno Martins <bruno.o.martins(a)gfi.world> > Cc: users(a)ovirt.org > Subject: Re: [ovirt-users] Re: Cannot enable maintenance mode > > Did you > > "Consider manual intervention" > > such as > > "stopping" or "migrating Vms" > > which are running on that host? > > If you are trying to put host to maintenance, it will migrate all the VMs > somewhere else, thus... you might have problem with migrations (try to > migrate them to other destination host) or power them off. > > On Wed, Oct 16, 2019 at 9:15 AM Bruno Martins <mailto: > bruno.o.martins(a)gfi.world> wrote: > Hey guys, > > There are really no options left here? Is there something else I should > check? > > Thank you! > > -----Original Message----- > From: Bruno Martins <mailto:bruno.o.martins@gfi.world> > Sent: 3 de outubro de 2019 22:41 > To: Benny Zlotnik <mailto:bzlotnik@redhat.com> > Cc: mailto:users@ovirt.org > Subject: [ovirt-users] Re: Cannot enable maintenance mode > > Hello Benny, > > I did. No luck, still... > > Cheers! > > -----Original Message----- > From: Benny Zlotnik <mailto:bzlotnik@redhat.com> > Sent: 2 de outubro de 2019 19:19 > To: Bruno Martins <mailto:bruno.o.martins@gfi.world> > Cc: mailto:users@ovirt.org > Subject: Re: [ovirt-users] Re: Cannot enable maintenance mode > > Did you try the "Confirm Host has been rebooted" button? > > On Wed, Oct 2, 2019 at 9:17 PM Bruno Martins <mailto: > bruno.o.martins(a)gfi.world> wrote: > > > > Hello guys, > > > > No ideas for this issue? > > > > Thanks for your cooperation! > > > > Kind regards, > > > > -----Original Message----- > > From: Bruno Martins <mailto:bruno.o.martins@gfi.world> > > Sent: 29 de setembro de 2019 16:16 > > To: mailto:users@ovirt.org > > Subject: [ovirt-users] Cannot enable maintenance mode > > > > Hello guys, > > > > I am being unable to put a host from a two nodes cluster into > maintenance mode in order to remove it from the cluster afterwards. > > > > This is what I see in engine.log: > > > > 2019-09-27 16:20:58,364 INFO > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (org.ovirt.thread.pool-6-thread-45) [4cc251c9] Correlation ID: 4cc251c9, > Job ID: 65731fbb-db34-49a9-ab56-9fba59bc0ee0, Call Stack: null, Custom > Event ID: -1, Message: Host CentOS-H1 cannot change into maintenance mode - > not all Vms have been migrated successfully. Consider manual intervention: > stopping/migrating Vms: Non interactive user (User: admin). > > > > Host has been rebooted multiple times. vdsClient shows no VM's running. > > > > What else can I do? > > > > Kind regards, > > > > Bruno Martins > > _______________________________________________ > > Users mailing list -- mailto:users@ovirt.org To unsubscribe send an > > email to mailto:users-leave@ovirt.org Privacy > > Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/X5FJWFW7 > > GXNW6YWRPFWOKA6VU3RH4WD3/ > > _______________________________________________ > > Users mailing list -- mailto:users@ovirt.org To unsubscribe send an > > email to mailto:users-leave@ovirt.org Privacy > > Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/DD5DW6KK > > OOHGL3WFEKIIIS57BN3VWMAQ/ > > _______________________________________________ > Users mailing list -- mailto:users@ovirt.org To unsubscribe send an email > to mailto:users-leave@ovirt.org Privacy Statement: > https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/64GZQKZA7LX7K… > _______________________________________________ > Users mailing list -- mailto:users@ovirt.org To unsubscribe send an email > to mailto:users-leave@ovirt.org Privacy Statement: > https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/JJPEC7RDG3AUS… > > > -- > LUKAS SVATY > RHV QE > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/YZB2L7MK6SGQI… > -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

2 1

How to pass parameters between VDSM Hooks domxml in single run
by Vrgotic, Marko 06 Nov '19

06 Nov '19

Dear oVIrt, A while ago we discussed on ways to change/update content of parameters of domxml in certain action. As I mentioned before, we have added the VDSMHook 60_nsupdate which removes the DNS record entries when a VM is destroyed: … domxml = hooking.read_domxml() name = domxml.getElementsByTagName('name')[0] name = " ".join(name.nodeValue for name in name.childNodes if name.nodeType == name.TEXT_NODE) nsupdate_commands = """server {server_ip} update delete {vm_name}.example.com a update delete {vm_name}. example.com aaaa update delete {vm_name}. example.com txt send """.format(server_ip="172.16.1.10", vm_name=name) … The goal: However, we did not want to execute remove dns records when VM is only migrated. Since its considered a “destroy” action we took following approach. * In state “before_vm_migrate_source add hook which will write flag “is_migration” to domxml * Once VM is scheduled for migration, this hook should add the flag “is_migration” to domxml * Once 60_nsupdate is triggered, it will check for the flag and if there, skip executing dns record action, but only remove the flag “is_migration” from domxml of the VM … domxml = hooking.read_domxml() migration = domxml.createElement("is_migration") domxml.getElementsByTagName("domain")[0].appendChild(migration) logging.info("domxml_updated {}".format(domxml.toprettyxml())) hooking.write_domxml(domxml) … When executing first time, we observed that flag “ <name>hookiesvm</name> <uuid>fcfa66cb-b251-43a3-8e2b-f33b3024a749</uuid> <metadata xmlns:ns0="http://ovirt.org/vm/tune/1.0" xmlns:ns1="http://ovirt.org/vm/1.0"> <ns0:qos/> <ovirt-vm:vm xmlns:ovirt-vm="http://ovirt.org/vm/1.0"> <ovirt-vm:clusterVersion>4.3</ovirt-vm:clusterVersion> <ovirt-vm:destroy_on_reboot type="bool">False</ovirt-vm:destroy_on_reboot> <ovirt-vm:launchPaused>false</ovirt-vm:launchPaused> <ovirt-vm:memGuaranteedSize type="int">1024</ovirt-vm:memGuaranteedSize> <ovirt-vm:minGuaranteedMemoryMb type="int">1024</ovirt-vm:minGuaranteedMemoryMb> ...skipping... <address bus="0x00" domain="0x0000" function="0x0" slot="0x09" type="pci"/> </rng> </devices> <seclabel model="selinux" relabel="yes" type="dynamic"> <label>system_u:system_r:svirt_t:s0:c169,c575</label> <imagelabel>system_u:object_r:svirt_image_t:s0:c169,c575</imagelabel> </seclabel> <seclabel model="dac" relabel="yes" type="dynamic"> <label>+107:+107</label> <imagelabel>+107:+107</imagelabel> </seclabel> <is_migration/> </domain> is added to domxml, but was present once 60_nsupdate hook was executed. The question: How do we make sure that, when domxml is updated, that the update is visible/usable by following hook, in single run? How to pass these changes between hooks? Kindly awaiting your reply. — — — Met vriendelijke groet / Kind regards, Marko Vrgotic

2 6

Ansible setup host network fails on comparing sorted dictionaries
by Vrgotic, Marko 06 Nov '19

06 Nov '19

Dear oVirt, While deploying ovirt_infra , the role oivrt.networks fails on Setup Host Networks, with following error: TypeError: '<' not supported between instances of 'dict' and 'dict' Full output: TASK [ovirt.infra/roles/ovirt.networks : Setup host networks] ****************************************************************************************************************** The full traceback is: Traceback (most recent call last): File "/var/folders/40/w2c8fp151854mddz_4n3czwm0000gn/T/ansible_ovirt_host_network_payload_s0fx52mx/__main__.py", line 396, in main (nic is None or host_networks_module.has_update(nics_service.service(nic.id))) File "/var/folders/40/w2c8fp151854mddz_4n3czwm0000gn/T/ansible_ovirt_host_network_payload_s0fx52mx/__main__.py", line 289, in has_update update = self.__compare_options(get_bond_options(bond.get('mode'), bond.get('options')), getattr(nic.bonding, 'options', [])) File "/var/folders/40/w2c8fp151854mddz_4n3czwm0000gn/T/ansible_ovirt_host_network_payload_s0fx52mx/__main__.py", line 247, in __compare_options return sorted(get_dict_of_struct(opt) for opt in new_options) != sorted(get_dict_of_struct(opt) for opt in old_options) TypeError: '<' not supported between instances of 'dict' and 'dict' failed: [localhost] (item={'name': 'ovirt-staging-hv-02.avinity.tv', 'check': True, 'save': True, 'bond': {'name': 'bond28', 'mode': 4, 'interfaces': ['p2p1', 'p2p2']}, 'networks': [{'name': 'backbone', 'boot_protocol': 'static', 'address': '172.17.28.212', 'netmask': '255.255.255.0', 'version': 'v4'}]}) => { "ansible_loop_var": "item", "changed": false, "invocation": { "module_args": { "bond": { "interfaces": [ "p2p1", "p2p2" ], "mode": 4, "name": "bond28" }, "check": true, "fetch_nested": false, "interface": null, "labels": null, "name": "ovirt-staging-hv-02.avinity.tv", "nested_attributes": [], "networks": [ { "address": "172.17.28.212", "boot_protocol": "static", "name": "backbone", "netmask": "255.255.255.0", "version": "v4" } ], "poll_interval": 3, "save": true, "state": "present", "sync_networks": false, "timeout": 180, "wait": true } }, "item": { "bond": { "interfaces": [ "p2p1", "p2p2" ], "mode": 4, "name": "bond28" }, "check": true, "name": "ovirt-staging-hv-02.avinity.tv", "networks": [ { "address": "172.17.28.212", "boot_protocol": "static", "name": "backbone", "netmask": "255.255.255.0", "version": "v4" } ], "save": true }, "msg": "'<' not supported between instances of 'dict' and 'dict'" } Read vars_file 'vars/engine_vars.yml' Read vars_file 'vars/secrets.yml' Read vars_file 'vars/ovirt_infra_vars.yml' Looking further into ovirt_host_network.py I found that issue is reported after following is executed: return sorted(get_dict_of_struct(opt) for opt in new_options) != sorted(get_dict_of_struct(opt) for opt in old_options) It seemed to be failing due to not getting the key value to sort the dicts, so I added sorting based on name, to test, and it worked in single test run: return sorted((get_dict_of_struct(opt) for opt in new_options), key=lambda x: x["name"]) != sorted((get_dict_of_struct(opt) for opt in old_options), key=lambda x: x["name"]) After rerun of the play, with changes above: TASK [ovirt.infra/roles/ovirt.networks : Setup host networks] ****************************************************************************************************************** task path: /Users/mvrgotic/Git/ovirt-engineering/roles/ovirt.infra/roles/ovirt.networks/tasks/main.yml:25 Using module file /Users/mvrgotic/.local/share/virtualenvs/ovirt-engineering-JaxzXThh/lib/python3.7/site-packages/ansible/modules/cloud/ovirt/ovirt_host_network.py Pipelining is enabled. <127.0.0.1> ESTABLISH LOCAL CONNECTION FOR USER: mvrgotic <127.0.0.1> EXEC /bin/sh -c '/Users/mvrgotic/.local/share/virtualenvs/ovirt-engineering-JaxzXThh/bin/python3 && sleep 0' changed: [localhost] => (item={'name': 'ovirt-staging-hv-02.avinity.tv', 'check': True, 'save': True, 'bond': {'name': 'bond28', 'mode': 4, 'interfaces': ['p2p1', 'p2p2']}, 'networks': [{'name': 'backbone', 'boot_protocol': 'static', 'address': '172.17.28.212', 'netmask': '255.255.255.0', 'version': 'v4'}]}) => { "ansible_loop_var": "item", "changed": true, "host_nic": { "ad_aggregator_id": 6, "bonding": { "ad_partner_mac": { "address": "44:31:92:7c:b3:11" }, "options": [ { "name": "mode", "type": "Dynamic link aggregation (802.3ad)", "value": "4" }, { "name": "xmit_hash_policy", "value": "2" } ], "slaves": [ { "href": "/ovirt-engine/api/hosts/aa1f7a65-a867-436a-9a7f-264068f4bdea/nics/01703220-570c-44f5-9729-6717ceead304", "id": "01703220-570c-44f5-9729-6717ceead304" }, { "href": "/ovirt-engine/api/hosts/aa1f7a65-a867-436a-9a7f-264068f4bdea/nics/e879c1c6-065d-4742-b282-fcdb477f95a7", "id": "e879c1c6-065d-4742-b282-fcdb477f95a7" } ] }, "boot_protocol": "static", "bridged": false, "custom_configuration": false, "host": { "href": "/ovirt-engine/api/hosts/aa1f7a65-a867-436a-9a7f-264068f4bdea", "id": "aa1f7a65-a867-436a-9a7f-264068f4bdea" }, "href": "/ovirt-engine/api/hosts/aa1f7a65-a867-436a-9a7f-264068f4bdea/nics/abce07fa-cb7f-46f2-b967-69d1feaa4075", "id": "abce07fa-cb7f-46f2-b967-69d1feaa4075", "ip": { "address": "172.17.28.212", "netmask": "255.255.255.0", "version": "v4" }, "ipv6": { "gateway": "::", "version": "v6" }, "ipv6_boot_protocol": "none", "mac": { "address": "b4:96:91:3f:47:1c" }, "mtu": 9000, "name": "bond28", "network": { "href": "/ovirt-engine/api/networks/f3ef80cf-bf3a-4fa5-aed9-7d9e7455f804", "id": "f3ef80cf-bf3a-4fa5-aed9-7d9e7455f804" }, "network_labels": [], "properties": [], "speed": 10000000000, "statistics": [], "status": "up" }, "id": "abce07fa-cb7f-46f2-b967-69d1feaa4075", "invocation": { "module_args": { "bond": { "interfaces": [ "p2p1", "p2p2" ], "mode": 4, "name": "bond28" }, "check": true, "fetch_nested": false, "interface": null, "labels": null, "name": "ovirt-staging-hv-02.avinity.tv", "nested_attributes": [], "networks": [ { "address": "172.17.28.212", "boot_protocol": "static", "id": "3e40ff7d-5384-45f1-b036-13e6f91aff56", "name": "backbone", "netmask": "255.255.255.0", "version": "v4" } ], "poll_interval": 3, "save": true, "state": "present", "sync_networks": false, "timeout": 180, "wait": true } }, "item": { "bond": { "interfaces": [ "p2p1", "p2p2" ], "mode": 4, "name": "bond28" }, "check": true, "name": "ovirt-staging-hv-02.avinity.tv", "networks": [ { "address": "172.17.28.212", "boot_protocol": "static", "name": "backbone", "netmask": "255.255.255.0", "version": "v4" } ], "save": true } } Read vars_file 'vars/engine_vars.yml' Read vars_file 'vars/secrets.yml' Read vars_file 'vars/ovirt_infra_vars.yml' Changes resulted in applying configuration exactly as intended. Not sure it this was the actual intention, but please let me know if the made change was as initially intended for sorted compare to work. My pipenv setup: Python 3.7 ansible==2.8.6 asn1crypto==1.1.0 bcrypt==3.1.7 cffi==1.13.1 cryptography==2.8 dnspython==1.16.0 ipaddress==1.0.23 Jinja2==2.10.3 jmespath==0.9.4 lxml==4.4.1 MarkupSafe==1.1.1 netaddr==0.7.19 ovirt-engine-sdk-python==4.3.3 paramiko==2.6.0 passlib==1.7.1 pyasn1==0.4.5 pycparser==2.19 pycurl==7.43.0.3 PyNaCl==1.3.0 PyYAML==5.1.2 six==1.12.0 Ansible vars and play: ================================= host_networks: - name: ovirt-staging-hv-02.avinity.tv check: true save: true bond: name: bond28 mode: 4 interfaces: - p2p1 - p2p2 networks: - name: backbone boot_protocol: static address: 172.17.28.212 netmask: 255.255.255.0 version: v4 ================================= - name: Setup host networks ovirt_host_network: auth: "{{ ovirt_auth }}" name: "{{ item.name }}" state: "{{ item.state | default(omit) }}" check: "{{ item.check | default(omit) }}" save: "{{ item.save | default(omit) }}" bond: "{{ item.bond | default(omit) }}" networks: "{{ item.networks | default(omit) }}" labels: "{{ item.labels | default(omit) }}" interface: "{{ item.interface | default(omit) }}" with_items: - "{{ host_networks | default([]) }}" tags: - host_networks - networks ====================================

2 3

[feedback needed] oVirt master test
by Sandro Bonazzola 05 Nov '19

05 Nov '19

Hi, as part of the 4.4 development we'd like to ask for testing current master. In order to ease the test, you can take: oVirt Node: https://resources.ovirt.org/pub/ovirt-master-snapshot/iso/ovirt-node-ng-ins… when this link won't be available anymore due to nightly build rotation you can take the latest from https://resources.ovirt.org/pub/ovirt-master-snapshot/iso/ovirt-node-ng-ins… oVirt appliance: https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el8/x86_64/ovirt-… as per oVirt Node, you can take the latest from https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el8/x86_64/ if above link doesn't work. The above 2 builds have been tested on a single host nested VM system with 70Gb disk, 8Gb of RAM and 4 cores for the node. Both oVirt Node and oVirt Engine appliance installation succeeded on 80GB NFS external storage with static IP addressing. We have a known issue on booting with more than 1 NIC that will be addressed soon, so please use a single NIC in your tests for now. Looking forward for your feedback, thanks. -- 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

[ANN] oVirt 4.3.7 First Release Candidate is now available for testing
by Sandro Bonazzola 05 Nov '19

05 Nov '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.7 First Release Candidate for testing, as of October 18th, 2019. This update is a release candidate of the seventh in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) * oVirt Node 4.3 (available for x86_64 only) has been built consuming CentOS 7.7 Release See the release notes [1] for known issues, new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available Additional Resources: * Read more about the oVirt 4.3.7 release highlights: http://www.ovirt.org/release/4.3.7/ * 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.3.7/ [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

5 8

Re: [ANN] oVirt 4.3.7 First Release Candidate is now available for testing
by Strahil 04 Nov '19

04 Nov '19

Hi Dominik, I think I found it - it seems that for some reason my gateway is missing in 'ip route'. Running 'ifdown ovirtmgmt; ifup ovirtmgmt' fixes it, which proves that network scripts read properly the ifcfg-ovirtmgmt file. Do you have any idea where to look for? Best Regards, Strahil NikolovOn Nov 2, 2019 17:17, Strahil <hunter86_bg(a)yahoo.com> wrote: > > I think I have a theory about ovirt1 , but I have to test it. > > 1. Ovirt1 has a team device controlled by NetworkManager , but in engine those interfaces are unused > 2. I guess that when I recently 'reinstalled' the host from UI, the old teamports' ifcfg-<DEVICENAME> was moved to ifcfg-<DEVICENAME>-1 and the original file was left empty. > 3. When the system rebooted, network.service rereads all ifcfg-* files and starts the team0 , but when NetworkManager reads the empty files - he alters the /etc/resolv.conf which leads to out-of-sync status. > > Still, this is only theory and as ovirt3 has no team device (plain gluster arbiter) - I'm not sure how close is this one. > > Best Regards, > Strahil Nikolov > > On Nov 2, 2019 09:50, Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: >> >> I saw the hint in the Cluster's tab and then on each host. I had to put the host back to maintenance in order to sync it again. >> >> Logs attached . >> >> Best Regards, >> Strahil Nikolov >> >> В четвъртък, 31 октомври 2019 г., 16:12:53 ч. Гринуич+2, Dominik Holler <dholler(a)redhat.com> написа: >> >> >> >> >> On Thu, Oct 31, 2019 at 10:06 AM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: >>> >>> >>> >>> Il giorno gio 31 ott 2019 alle ore 09:45 Strahil Nikolov <hunter86_bg(a)yahoo.com> ha scritto: >>>> >>>> Hi Sandro, >>>> >>>> I have just updated to latest release candidate (2 clusters in total - 1 AMD , 1 Intel). >>>> The only issue observed is that after patching every host's ovirtmgmt (I have another one that has none of the 4 roles which was OK) is out of sync and has to be synced before removing maintenance. >>>> >>>> Still the system was accessible. >>>> >>>> Can you guide me which log reports the out-of-sync in order to further investigate. >>> >>> >>> +Miguel Duarte de Mora Barroso , +Dominik Holler can you please help here? >>> >>> >> >> >> Do you remember if there was a hint shown as a tooltip if you hover the >> mouse pointer over ovirtmgmt in >> "Compute > Hosts > xxx > Network Interfaces > Setup Host Networks" >> ? >> >> Are you able to share the vdsm.log and engine.log after the ovirtmgmt? >> >>

3 3

Re: Disk encryption in oVirt
by Strahil 04 Nov '19

04 Nov '19

Hi, Maybe a gluster encryption will also cover your needs in a hyper converged setup? Best Regards, Strahil Nikolov On Oct 22, 2019 14:43, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > > Il giorno mar 22 ott 2019 alle ore 12:32 MIMMIK _ <dmarini(a)it.iliad.com> ha scritto: >> >> Is there a way to get a full disk encryption on virtual disks used by VMs in oVirt? > > > You can use encrypted file system managed from within the VM itself if the OS support it (dm-crypt with LUKS on GNU Linux, BitLocker) which is the most secure choice on this topic. > Encrypting the storage hosting the VM disks won't help once you access the storage for booting the VM, at that point disks will be accessible without encryption. > > > > >> >> >> Regards >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/3FMGDSRBHRWYR… > > > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA > > sbonazzo(a)redhat.com > > Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.

2 1

Re: oVirt/RHV 4.3.6: How to boot a Q35/UEFI VM from CD?
by Strahil 04 Nov '19

04 Nov '19

Hi, Can you give a try of the workaround in https://bugzilla.redhat.com/show_bug.cgi?id=1727987#c0 ? At least it works for RHEL 8 (and most probably CentOS 8). Best Regards, Strahil NikolovOn Nov 3, 2019 12:14, Mathieu Simon <mathieu.simon(a)gymneufeld.ch> wrote: > > Hi > > Am Sa., 2. Nov. 2019 um 08:51 Uhr schrieb Strahil Nikolov > <hunter86_bg(a)yahoo.com>: > > > Have you tried with another ISO ? > This is quite weird, still better than my initial testing but here it > goes. I've slimmed down my attempts to Q35 and UEFI (both on and off): > > - Server 2019 ISO boots into installer with or without SecureBoot > enabled (I clearly remember it didn't work in any combination I've > tried, but now it did, anyhow). The OS installes and boots with > SecureBoot enabled > - Server 2016 ISO fails to boot right at the windows bootloader*, > however I don't care for Server 2016 that much anymore at that point > in time, and it could well be that the ISO image could be of an older > revision > (MS does release updated images from time to time) > - Debian 10 boots of the CD, however it doesn't seem like NVRAM > changes are saved in oVirt / RHV guests yet. So at boot the OS doesn't > start and you have to once boot from file (EFI disk -> EFI -> debian > -> shimx64.efi) > After the boot you you have to copy all (or only shimx64.efi?) to > /boot/efi/EFI/BOOT as BOOTX64.EFI like Windows. Debian 10 has a > Microsoft-signed shim loader so SecureBoot actually works. > - Ubuntu 18.04 boots of the disc, installs and boots since their > installer puts a copy of shimx64.efi into /boot/efi/EFI/BOOT which is > where OVMF looks for a loader > > I'm I correctly guessing based on looking at the "VM devices" list per > VM that oVirt/RHV doesn't yet provide a way to provide a persistent > NVRAM image to guests? > Sso for the time being we're actually stuck on Linux systems to have a > EFI/BOOT/BOOTX64.EFI present? Is this the issue you wrote about? > (I've encountered this very same issue on plain KVM and Proxmox, in > both cases a small disk image is required per VM to make the content > of the NVRAM persistent across VM reboots) > > Regards > Mathieu > > * See screenshot uploaded here: https://imgur.com/a/ZsnbCOM > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PTQRSIUTCWI4V…

2 1

Re: Cannot enable maintenance mode
by Bruno Martins 04 Nov '19

04 Nov '19

Hi Lukas, Thanks for your message! In my cluster, I have all the VM's running under "HOST2". The issue I'm having is that I can't enable maintenance mode on "HOST1", in order to re-add it to oVirt Manager (SSL certificate replacement stuff). I did it successfully on "HOST2", but the other one seems to ignore my actions, with that message in the logs... Cheers, Bruno From: Lukas Svaty <lsvaty(a)redhat.com> Sent: 16 de outubro de 2019 10:49 To: Bruno Martins <bruno.o.martins(a)gfi.world> Cc: users(a)ovirt.org Subject: Re: [ovirt-users] Re: Cannot enable maintenance mode Did you "Consider manual intervention" such as "stopping" or "migrating Vms" which are running on that host? If you are trying to put host to maintenance, it will migrate all the VMs somewhere else, thus... you might have problem with migrations (try to migrate them to other destination host) or power them off. On Wed, Oct 16, 2019 at 9:15 AM Bruno Martins <mailto:bruno.o.martins@gfi.world> wrote: Hey guys, There are really no options left here? Is there something else I should check? Thank you! -----Original Message----- From: Bruno Martins <mailto:bruno.o.martins@gfi.world> Sent: 3 de outubro de 2019 22:41 To: Benny Zlotnik <mailto:bzlotnik@redhat.com> Cc: mailto:users@ovirt.org Subject: [ovirt-users] Re: Cannot enable maintenance mode Hello Benny, I did. No luck, still... Cheers! -----Original Message----- From: Benny Zlotnik <mailto:bzlotnik@redhat.com> Sent: 2 de outubro de 2019 19:19 To: Bruno Martins <mailto:bruno.o.martins@gfi.world> Cc: mailto:users@ovirt.org Subject: Re: [ovirt-users] Re: Cannot enable maintenance mode Did you try the "Confirm Host has been rebooted" button? On Wed, Oct 2, 2019 at 9:17 PM Bruno Martins <mailto:bruno.o.martins@gfi.world> wrote: > > Hello guys, > > No ideas for this issue? > > Thanks for your cooperation! > > Kind regards, > > -----Original Message----- > From: Bruno Martins <mailto:bruno.o.martins@gfi.world> > Sent: 29 de setembro de 2019 16:16 > To: mailto:users@ovirt.org > Subject: [ovirt-users] Cannot enable maintenance mode > > Hello guys, > > I am being unable to put a host from a two nodes cluster into maintenance mode in order to remove it from the cluster afterwards. > > This is what I see in engine.log: > > 2019-09-27 16:20:58,364 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-45) [4cc251c9] Correlation ID: 4cc251c9, Job ID: 65731fbb-db34-49a9-ab56-9fba59bc0ee0, Call Stack: null, Custom Event ID: -1, Message: Host CentOS-H1 cannot change into maintenance mode - not all Vms have been migrated successfully. Consider manual intervention: stopping/migrating Vms: Non interactive user (User: admin). > > Host has been rebooted multiple times. vdsClient shows no VM's running. > > What else can I do? > > Kind regards, > > Bruno Martins > _______________________________________________ > Users mailing list -- mailto:users@ovirt.org To unsubscribe send an > email to mailto:users-leave@ovirt.org Privacy > Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/X5FJWFW7 > GXNW6YWRPFWOKA6VU3RH4WD3/ > _______________________________________________ > Users mailing list -- mailto:users@ovirt.org To unsubscribe send an > email to mailto:users-leave@ovirt.org Privacy > Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/DD5DW6KK > OOHGL3WFEKIIIS57BN3VWMAQ/ _______________________________________________ Users mailing list -- mailto:users@ovirt.org To unsubscribe send an email to mailto:users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/64GZQKZA7LX7K… _______________________________________________ Users mailing list -- mailto:users@ovirt.org To unsubscribe send an email to mailto:users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/JJPEC7RDG3AUS… -- LUKAS SVATY RHV QE

1 0

Self-Hosted Engine + vxlan + networkd
by pavel＠gremwell.com 04 Nov '19

04 Nov '19

Dear oVirt Community, It appears that oVirt self-hosted engine does not support network configurations based on systemd-networkd? Am I correct? Does oVirt self-hosted engine deployment support VXLAN interface to configure "ovirtmgmt" on top of it? My setup: - three bare-metal servers: two of them are CentOS 7 based, clean installation. the third one is Ubuntu based served as a storage. - all three of them have public Internet connectivity, via basic Ethernet. - in order to emulate internal network, VXLAN was configured between those three. Mainly for testing purposes. - network configuration was done using systemd-networkd, internal communications worked fine. - DNS server was configured on this internal network. worked as direct/reverse resolver. Thus, the main host which I tried to convert to self-hosted engine following https://www.ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_… guide, has the following network interfaces (redacted): - eth0, static IPv4, connected to the Internet; - vxlan0, on top of eth0, has private IPv4, 192.168.200.1; - hosts names resolve via private VXLAN network using 192.168.200.254. I started deployment saying that: Engine FQDN:ovirt-e1.example.com Network Configuration:Static VM IP Address:192.168.200.250/24 Gateway Address:192.168.200.1 DNS Servers:192.168.200.254 hostname of this host on the management network: ovirt-h1.example.com Deployment fails with error "Host ovirt-h1.example.com installation failed. Failed to configure management network on the host." After failure the system (host) does not have "ovirtmgmt" bridge. The same situation was when the host moved from networkd configuration to "network-scripts" (with VXLAN support added). I suspect that the root cause of the problem is that ansible scenarios were not able to create "ovirtmgmt" bridge on top of vxlan0. No switching to VLAN-based management interface... (did not actually tried yet).

1 0

oVirt 4.3.6: volume start: engine: failed: Failed to find brick directory /gluster_bricks/engine/engine for volume engine. Reason : No such file or directory
by adrianquintero＠gmail.com 04 Nov '19

04 Nov '19

While trying to deploy using the WEB UI for single hyperconverged setup I run into this issue (ovirt 4.3.5, ovirt 4.3.6). mount point is "/gluster_bricks/engine" however "/gluster_bricks/engine/engine" is not created. Read a post about gluster 6.1 and having to add /gluster_bricks/engine/.glusterfs/indices manually, I tried it but it did not work, I could not deploy the hosted engine vm.

1 0

Re: Trying to add a LUN to a host and use that, instead of Gluster, as the datastore for my VM's.
by Strahil 03 Nov '19

03 Nov '19

You should be able to do that with the POSIX compliant domain ... If nit, it's better to open a bug so this behaviour is investigated further. Best Regards, Strahil NikolovOn Nov 2, 2019 00:38, TomK <tomkcpr(a)mdevsys.com> wrote: > > On 10/11/2019 12:10 AM, Strahil wrote: > > I'm not sure, but you can try with replica 1 gluster volume. > > Later that gluster volume can be changed to replica 2 arbiter 1 or even better replica 3 volume. > > > > Now that I see this I'm not sure we're on the same page. > > Thinking this might clarify a bit better. Let's take this scenario, > assume gluster is working perfectly: > > HOST01 > 4TB Local LUN /dev/sdb > 4TB Gluster FS (brick w/ host02,03) /dev/sdc > > > HOST02 > 4TB Local LUN /dev/sdb > 4TB Gluster FS (brick w/ host01,03) /dev/sdc > > > HOST03 > 4TB Local LUN /dev/sdb > 4TB Gluster FS (brick w/ host02,01) /dev/sdc > > > For each host I need the local LUN to be available for VM's with the > GlusterFS storage that's distributed across all three nodes. > > However, when I tried to add a local LUN, the host was removed from the > storage domain rendering it unavailable. Now when I took out the local > LUN, I was able to readd that host to the GlusterFS storage domain. > > So it appears I can't add a local LUN when a host is already > participating in a GlusterFS storage domain. > > > Cheers, > TK > > > > > > Best Regards, > > Strahil NikolovOn Oct 10, 2019 13:04, Tom <tk(a)mdevsys.com> wrote: > >> > >> I take it then theres no way to do so without NFS? > >> > >> Sent from my iPhone > >> > >>> On Oct 10, 2019, at 2:53 AM, Strahil <hunter86_bg(a)yahoo.com> wrote: > >>> > >>> You can create an NFS on that host and export to itself that local storage... > >>> > >>> Best Regards, > >>> Strahil NikolovOn Oct 9, 2019 07:43, TomK <tomkcpr(a)mdevsys.com> wrote: > >>>> > >>>> Manged to reverse it through the options. Had to deactivate the custom > >>>> local cluster. > >>>> > >>>> Now I have my GlusterFS back and want to try and add some local storage > >>>> to each host under the same DC, Cluster and Storage Domain. So > >>>> effectively I will have two storage locations. One on my GlusterFS and > >>>> the other on the local storage I've just defined. > >>>> > >>>> Appears I can't make them coexist with oVirt. Either the host is placed > >>>> in a separate cluster with local storage, or I move it back to the > >>>> GlusterFS. > >>>> > >>>> Appears I can't have two usable storage types under one host. Is this > >>>> correct? > >>>> > >>>> What I'm looking for is in the image and shared earlier. > >>>> > >>>> Cheers, > >>>> TK > >>>> > >>>>> On 10/8/2019 11:03 PM, TomK wrote: > >>>>> I'm working to reverse this scenario. > >>>>> > >>>>> My storage domain still exists. However I can't activate it. The > >>>>> Manage button is greyed out without clear indication as to why. > >>>>> Difficult to tell what my next move should be. > >>>>> > >>>>> Anyway to find out? > >>>>> > >>>>> Cheers, > >>>>> TK > >>>>> > >>>>>> On 10/7/2019 8:25 AM, TomK wrote: > >>>>>> Allright. > >>>>>> > >>>>>> So I followed this and configured local storage. It had some default > >>>>>> names that I changed. It would have been either the default name, or > >>>>>> one I choose. In either case it would be a different name then the > >>>>>> Gluster storage domain the host was a part of anyway. > >>>>>> > >>>>>> Once the process completed for both hosts, I noticed the Gluster > >>>>>> volume storage domain was offline and the gluster volume was gone. I > >>>>>> can't seem to add that back in anymore. I get: > >>>>>> > >>>>>> "Error while executing action DisconnectStorageServerConnection: Error > >>>>>> storage server disconnection" > >>>>>> > >>>>>> Guessing I can't have local storage in addition to Gluster on the same > >>>>>> hosts and available for VM's? > >>>>>> > >>>>>> Reason why I need that is that Gluster is slow but provides redundancy > >>>>>> and live migration. But I also wanted direct storage for VM's > >>>>>> requiring faster IO. So here's my sc

2 3

Recovery virtual disks from a added iscsi storage
by Kalil de A. Carvalho 03 Nov '19

03 Nov '19

Hello all. A had a big problem in my company. We had electircal problem and I'v lost access to my iscsi storage. After reinstall the hosted engine a added the storage, but no one virtual disk was faund there. It is possible to recovery it? Best regards. -- Atenciosamente, Kalil de A. Carvalho

2 1

Re: oVirt/RHV 4.3.6: How to boot a Q35/UEFI VM from CD?
by Strahil 03 Nov '19

03 Nov '19

I have successfully managed to boot and install RHEL & openSUSE with Secureboot, but UEFI variables are not saved and requires some workarounds (there is a bug opened for that) to work. What exactly is your problem? Best Regards, Strahil NikolovOn Oct 29, 2019 10:32, mathieu.simon(a)gymneufeld.ch wrote: > > Hi > > I've been experimenting with UEFI on RHV 4.3.6 using Windows Server 2019 but I guess posting on the oVirt list might reach a wider audience. > I've used UEFI guests on other KVM-based virtualizations, but I have been unable to detect a UEFI-bootable CD using Q35 VMs with or without SecureBoot in RHV 4.3.6 since it doesn't even propose to load the UEFI loader from within OVMF. It seems to show the CD-ROM drive, but I cannot boot from file the disc from OVMF: > > Are there any hints? (I've tried finding something more detailed in the Docs though) I'd like investigate UEFI and SecureBoot on oVirt/RHV even if it's still considered a tech preview. (I've been using KVM-based UEFI VM for years already on other platforms and distributions with no particular issues, rather advantages overall). > > Regards > Mathieu > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AVHRXTQ4TSZCY…

3 3

Re: [ANN] oVirt 4.3.7 First Release Candidate is now available for testing
by Strahil 02 Nov '19

02 Nov '19

I think I have a theory about ovirt1 , but I have to test it. 1. Ovirt1 has a team device controlled by NetworkManager , but in engine those interfaces are unused 2. I guess that when I recently 'reinstalled' the host from UI, the old teamports' ifcfg-<DEVICENAME> was moved to ifcfg-<DEVICENAME>-1 and the original file was left empty. 3. When the system rebooted, network.service rereads all ifcfg-* files and starts the team0 , but when NetworkManager reads the empty files - he alters the /etc/resolv.conf which leads to out-of-sync status. Still, this is only theory and as ovirt3 has no team device (plain gluster arbiter) - I'm not sure how close is this one. Best Regards, Strahil NikolovOn Nov 2, 2019 09:50, Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > > I saw the hint in the Cluster's tab and then on each host. I had to put the host back to maintenance in order to sync it again. > > Logs attached . > > Best Regards, > Strahil Nikolov > > В четвъртък, 31 октомври 2019 г., 16:12:53 ч. Гринуич+2, Dominik Holler <dholler(a)redhat.com> написа: > > > > > On Thu, Oct 31, 2019 at 10:06 AM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: >> >> >> >> Il giorno gio 31 ott 2019 alle ore 09:45 Strahil Nikolov <hunter86_bg(a)yahoo.com> ha scritto: >>> >>> Hi Sandro, >>> >>> I have just updated to latest release candidate (2 clusters in total - 1 AMD , 1 Intel). >>> The only issue observed is that after patching every host's ovirtmgmt (I have another one that has none of the 4 roles which was OK) is out of sync and has to be synced before removing maintenance. >>> >>> Still the system was accessible. >>> >>> Can you guide me which log reports the out-of-sync in order to further investigate. >> >> >> +Miguel Duarte de Mora Barroso , +Dominik Holler can you please help here? >> >> > > > Do you remember if there was a hint shown as a tooltip if you hover the > mouse pointer over ovirtmgmt in > "Compute > Hosts > xxx > Network Interfaces > Setup Host Networks" > ? > > Are you able to share the vdsm.log and engine.log after the ovirtmgmt? > >

1 0

How to change the CPU of the win10 virtual machine on ovirt-node from 2 cores to 8 cores?
by wangyu13476969128＠126.com 01 Nov '19

01 Nov '19

The version of The ovirt-engine is 4.3.5. I created a win10 virtual machine on ovirt-node, which is allocated 8 cores, and when using the virtual machine I found only 2 cores. I used the command "virsh edit win10" on ovirt-node to prepare to modify the CPU core. I was prompted to enter my username and password. I entered the username and password of the ovirt-engine web interface and ssh log in to the ovirt-node username root and password, but both prompt: Error: failed to connect to the hypervisor Error: authentication failed: authentication failed How can this problem be solved?

4 6

Re: Trying to add a LUN to a host and use that, instead of Gluster, as the datastore for my VM's.
by Strahil 01 Nov '19

01 Nov '19

I'm not sure, but you can try with replica 1 gluster volume. Later that gluster volume can be changed to replica 2 arbiter 1 or even better replica 3 volume. Best Regards, Strahil NikolovOn Oct 10, 2019 13:04, Tom <tk(a)mdevsys.com> wrote: > > I take it then theres no way to do so without NFS? > > Sent from my iPhone > > > On Oct 10, 2019, at 2:53 AM, Strahil <hunter86_bg(a)yahoo.com> wrote: > > > > You can create an NFS on that host and export to itself that local storage... > > > > Best Regards, > > Strahil NikolovOn Oct 9, 2019 07:43, TomK <tomkcpr(a)mdevsys.com> wrote: > >> > >> Manged to reverse it through the options. Had to deactivate the custom > >> local cluster. > >> > >> Now I have my GlusterFS back and want to try and add some local storage > >> to each host under the same DC, Cluster and Storage Domain. So > >> effectively I will have two storage locations. One on my GlusterFS and > >> the other on the local storage I've just defined. > >> > >> Appears I can't make them coexist with oVirt. Either the host is placed > >> in a separate cluster with local storage, or I move it back to the > >> GlusterFS. > >> > >> Appears I can't have two usable storage types under one host. Is this > >> correct? > >> > >> What I'm looking for is in the image and shared earlier. > >> > >> Cheers, > >> TK > >> > >>> On 10/8/2019 11:03 PM, TomK wrote: > >>> I'm working to reverse this scenario. > >>> > >>> My storage domain still exists. However I can't activate it. The > >>> Manage button is greyed out without clear indication as to why. > >>> Difficult to tell what my next move should be. > >>> > >>> Anyway to find out? > >>> > >>> Cheers, > >>> TK > >>> > >>>> On 10/7/2019 8:25 AM, TomK wrote: > >>>> Allright. > >>>> > >>>> So I followed this and configured local storage. It had some default > >>>> names that I changed. It would have been either the default name, or > >>>> one I choose. In either case it would be a different name then the > >>>> Gluster storage domain the host was a part of anyway. > >>>> > >>>> Once the process completed for both hosts, I noticed the Gluster > >>>> volume storage domain was offline and the gluster volume was gone. I > >>>> can't seem to add that back in anymore. I get: > >>>> > >>>> "Error while executing action DisconnectStorageServerConnection: Error > >>>> storage server disconnection" > >>>> > >>>> Guessing I can't have local storage in addition to Gluster on the same > >>>> hosts and available for VM's? > >>>> > >>>> Reason why I need that is that Gluster is slow but provides redundancy > >>>> and live migration. But I also wanted direct storage for VM's > >>>> requiring faster IO. So here's my scenario: > >>>> > >>>> host01 > >>>> /dev/sda OS > >>>> /dev/sdb 4TB (For Gluster) > >>>> /dev/sdc 4TB (For Local Storage) > >>>> > >>>> host02 > >>>> /dev/sda OS > >>>> /dev/sdb 4TB (For Gluster) > >>>> /dev/sdc 4TB (For Local Storage) > >>>> > >>>> I would like to have: > >>>> > >>>> 1) GlusterFS volume available to oVirt via the two /dev/sdb drives in > >>>> both physical hosts. > >>>> 2) Two locally attached LUN's, each separate and local to that > >>>> physical host. > >>>> > >>>> Is this possible? > >>>> > >>>> Cheers, > >>>> TK > >>>> > >>>>> On 10/6/2019 12:38 AM, Strahil wrote: > >>>>> Hi Tom, > >>>>> > >>>>> Have you checked > >>>>> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht… > >>>>> ? > >>>>> > >>>>> Best Regards, > >>>>> Strahil NikolovOn Oct 6, 2019 06:26, TomK <tomkcpr(a)mdevsys.com> wrote: > >>>>>> > >>>>>> Hey All, > >>>>>> > >>>>>> I've added a 4TB LUN to my physical storage and now I want to use that, > >>>>>> instead of GlusterFS as my datastore for VM's on that physical. How do > >>>>>> I do this? > >>>>>> > >>>>>> I've tried a number of options, including adding LUN's but appears I > >>>>>> can > >>>>>> only add them to VM's directly but not use them as my datastores > >>

2 1

Re: oVirt 4.3.5/6 HC: Reinstall fails from WEB UI
by Strahil 01 Nov '19

01 Nov '19

Ssh to host and check the status of : sanlock.service supervdsmd.service vdsmd.service ovirt-ha-broker.service ovirt-ha-agent.service For example if sanlock is working, but supervdsmd is not - try to restart it. If it fais, run: systemctl cat supervdsmd.service And execute the commands in sections: ExecStartPre ExecStart And report any issues, then follow the next service in the chain. Best Regards, Strahil NikolovOn Oct 16, 2019 23:52, adrianquintero(a)gmail.com wrote: > > Hi, > I am trying to re-install a host from the web UI in oVirt 4.3.5, but it always fails and goes to "Setting Host state to Non-Operational" > > From the engine.log I see the following WARN/ERROR: > 2019-10-16 16:32:57,263-04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-43) [491c8bd9] EVENT_ID: VDS_SET_NONOPERATIONAL_DOMAIN(522), Host host1.example.com cannot access the Storage Domain(s) attached to the Data Center Default-DC1. Setting Host state to Non-Operational. > 2019-10-16 16:32:57,271-04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-43) [491c8bd9] EVENT_ID: VDS_ALERT_FENCE_TEST_FAILED(9,001), Power Management test failed for Host host1.example.com.There is no other host in the data center that can be used to test the power management settings. > 2019-10-16 16:32:57,276-04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-43) [491c8bd9] EVENT_ID: CONNECT_STORAGE_POOL_FAILED(995), Failed to connect Host host1.example.com to Storage Pool Default-DC1 > 2019-10-16 16:35:06,151-04 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (EE-ManagedThreadFactory-engine-Thread-137245) [] Could not connect host 'host1.example.com' to pool 'Default-DC1': Error storage pool connection: (u"spUUID=7d3fb14c-ebf0-11e9-9ee5-00163e05e135, msdUUID=4b87a5de-c976-4982-8b62-7cffef4a22d8, masterVersion=1, hostID=1, domainsMap={u'8c2df9c6-b505-4499-abb9-0d15db80f33e': u'active', u'4b87a5de-c976-4982-8b62-7cffef4a22d8': u'active', u'5d9f7d05-1fcc-4f99-9470-4e57cd15f128': u'active', u'fe24d88e-6acf-42d7-a857-eaf1f8deb24a': u'active'}",) > 2019-10-16 16:35:06,248-04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [690baf86] EVENT_ID: VDS_SET_NONOPERATIONAL_DOMAIN(522), Host host1.example.com cannot access the Storage Domain(s) attached to the Data Center Default-DC1. Setting Host state to Non-Operational. > 2019-10-16 16:35:06,256-04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [690baf86] EVENT_ID: VDS_ALERT_FENCE_TEST_FAILED(9,001), Power Management test failed for Host host1.example.com.There is no other host in the data center that can be used to test the power management settings. > 2019-10-16 16:35:06,261-04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-91) [690baf86] EVENT_ID: CONNECT_STORAGE_POOL_FAILED(995), Failed to connect Host host1.example.com to Storage Pool Default-DC1 > 2019-10-16 16:37:46,011-04 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] Connection timeout for host 'host1.example.com', last response arrived 1501 ms ago. > 2019-10-16 16:41:57,095-04 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (EE-ManagedThreadFactory-engine-Thread-137527) [17f3aadd] Could not connect host 'host1.example.com' to pool 'Default-DC1': Error storage pool connection: (u"spUUID=7d3fb14c-ebf0-11e9-9ee5-00163e05e135, msdUUID=4b87a5de-c976-4982-8b62-7cffef4a22d8, masterVersion=1, hostID=1, domainsMap={u'8c2df9c6-b505-4499-abb9-0d15db80f33e': u'active', u'4b87a5de-c976-4982-8b62-7cffef4a22d8': u'active', u'5d9f7d05-1fcc-4f99-9470-4e57cd15f128': u'active', u'fe24d88e-6acf-42d7-a857-eaf1f8deb24a': u'active'}",) > 2019-10-16 16:41:57,199-04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-22) [508ddb44] EVENT_ID: VDS_SET_NONOPERATIONAL_DOMAIN(522), Host host1.example.com cannot access the Storage Domain(s) attached to the Data Center Default-DC1. Setting Host state to Non-Operational. > 2019-10-16 16:41:57,211-04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-22) [508ddb44] EVENT_ID: VDS_ALERT_FENCE_TEST_FAILED(9,001), Power Management test failed for Host host1.example.com.There is no other host in the data center that can be used to test the power management settings. > 2019-10-16 16:41:57,216-04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-22) [508ddb44] EVENT_ID: CONNECT_STORAGE_POOL_FAILED(995), Failed to connect Host host1.example.com to Storage Pool Default-DC1 > > Any ideas why this might be happening? > I have researched, however I have not been able to find a solution. > > thanks, > > Adrian > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/3XAKJ23DSQVGI…

4 9