May 2017 - Users - oVirt List Archives

Force-Shutdown a VM?
by Derek Atkins 08 May '17

08 May '17

Hi, I'm running ovirt-4.0.6 on EL7.3. I've got a stuck VM (Windows 10) that I'm trying to restart. Unfortunately it's "up" enough that ovirt is trying to perform a soft-shutdown, but it's not up enough to complete the task. If I login to the ovirt admin portal as the admin, select shutdown, I see the following engine log messages before I get an event "Shutdown of VM <vm-name> failed.": 2017-05-04 11:23:27,774 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-14) [3f629ae6] Correlation ID: 3f629ae6, Job ID: 1f5275cd-d2fe-44d5-a1cf-d1920e3f3378, Call Stack: null, Custom Event ID: -1, Message: VM shutdown initiated by admin@internal-authz on VM win10-64 (Host: ovirt-0). 2017-05-04 11:28:38,237 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler10) [4cf2f258] VM 'c9830039-9bf9-4c6a-8eae-da9c24aad899'(win10-64) moved from 'PoweringDown' --> 'Up' 2017-05-04 11:28:38,287 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler10) [4cf2f258] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Shutdown of VM win10-64 failed. So, how can I get out of this situation? How can I force-powerdown this VM so I can reboot it? Thanks, -derek -- Derek Atkins 617-623-3745 derek(a)ihtfp.com www.ihtfp.com Computer and Internet Security Consultant

5 13

Ovirt Installation on Centos 7.3 1704 is broken
by Oliver Dietzel 08 May '17

08 May '17

Collectd-disk and -write_http require an older version of collectd than offered by the repos (7.2.0-2 instead of 7.2.1-2 as offered by repo). Will there be updated versions of collectd-disk and -write_http? To reproduce try # yum -y install ovirt-engine on a fully updated Centos 7.3 1704 https://buildlogs.centos.org/rolling/7/isos/x86_64/CentOS-7-x86_64-Minimal-… ___________________________________________________________ Oliver Dietzel

3 3

Re: [ovirt-users] New oVirt Node 4.0.6.1 network problem with bond and many vlans - Network.service timeout failed
by Sandro Bonazzola 08 May '17

08 May '17

Il 04/Mag/2017 20:02, "Rogério Ceni Coelho" <rogeriocenicoelho(a)gmail.com> ha scritto: Hi oVirt admins, Yesterday, i install a new node 4.0.6.1 I would suggest to go with 4.1.1 nodes since 4.0 is not supported anymore. and after config network bond (1) + vlans ( about 50 ), network.service failed with timeout as above. All my old and working fine oVirt nodes run 4.0.5 and have the same 5 min timeout on systemd. When i try to run vms on this new server, some networks are ok and some not. I install oVirt Node with 4.0.3 on same server and this problem do not occur. How can i workaround or change timeout to network.service ? In time, there are any way to update oVirt Node to 4.0.5 from 4.0.3 install iso ? [root@prd-rbs-ovirt-kvm21-poa ~]# systemctl status network.service â— network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled) Active: failed (Result: timeout) since Thu 2017-05-04 11:29:43 BRT; 3h 12min ago Docs: man:systemd-sysv-generator(8) Process: 7574 ExecStart=/etc/rc.d/init.d/network start (code=killed, signal=TERM) May 04 11:29:12 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: Bringing up interface o_p_s_a_lb_758: [ OK ] May 04 11:29:18 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: Bringing up interface o_p_sites_a_755: [ OK ] May 04 11:29:23 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: Bringing up interface o_prod_app_757: [ OK ] May 04 11:29:28 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: Bringing up interface o_prod_db_756: [ OK ] May 04 11:29:38 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: Bringing up interface ovirtmgmt: [ OK ] *May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br <http://prd-rbs-ovirt-kvm21-poa.rbs.com.br> systemd[1]: network.service start operation timed out. Terminating.* May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: Failed to start LSB: Bring up/down networking. May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: Unit network.service entered failed state. May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: network.service failed. May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]: Bringing up interface paas_1305: [root@prd-rbs-ovirt-kvm21-poa ~]# [root@prd-rbs-ovirt-kvm21-poa ~]# systemctl restart network.service Job for network.service failed because a timeout was exceeded. See "systemctl status network.service" and "journalctl -xe" for details. [root@prd-rbs-ovirt-kvm21-poa ~]# systemctl status network.service â— network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled) Active: failed (Result: timeout) since Thu 2017-05-04 14:55:34 BRT; 4min 46s ago Docs: man:systemd-sysv-generator(8) Process: 40810 ExecStart=/etc/rc.d/init.d/network start (code=killed, signal=TERM) May 04 14:55:21 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: [ OK ] May 04 14:55:23 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: Bringing up interface o_hlg_db_766: RTNETLINK answers: File exists May 04 14:55:26 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: [ OK ] May 04 14:55:28 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: Bringing up interface o_p_s_a_lb_758: RTNETLINK answers: File exists May 04 14:55:31 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: [ OK ] May 04 14:55:33 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: Bringing up interface o_p_sites_a_755: RTNETLINK answers: File exists May 04 14:55:34 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: network.service start operation timed out. Terminating. May 04 14:55:34 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: Failed to start LSB: Bring up/down networking. May 04 14:55:34 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: Unit network.service entered failed state. May 04 14:55:34 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: network.service failed. [root@prd-rbs-ovirt-kvm21-poa ~]# _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

2 2

VM disk update failure
by Stefano Bovina 07 May '17

07 May '17

Hi, while trying to update a VM disk, a failure was returned (forcing me to add a new disk) Any advice on how to resolve this error? Thanks Installation info: ovirt-release35-006-1.noarch libgovirt-0.3.3-1.el7_2.1.x86_64 vdsm-4.16.30-0.el7.centos.x86_64 vdsm-xmlrpc-4.16.30-0.el7.centos.noarch vdsm-yajsonrpc-4.16.30-0.el7.centos.noarch vdsm-jsonrpc-4.16.30-0.el7.centos.noarch vdsm-python-zombiereaper-4.16.30-0.el7.centos.noarch vdsm-python-4.16.30-0.el7.centos.noarch vdsm-cli-4.16.30-0.el7.centos.noarch qemu-kvm-ev-2.3.0-29.1.el7.x86_64 qemu-kvm-common-ev-2.3.0-29.1.el7.x86_64 qemu-kvm-tools-ev-2.3.0-29.1.el7.x86_64 libvirt-client-1.2.17-13.el7_2.3.x86_64 libvirt-daemon-driver-storage-1.2.17-13.el7_2.3.x86_64 libvirt-python-1.2.17-2.el7.x86_64 libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.3.x86_64 libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.3.x86_64 libvirt-lock-sanlock-1.2.17-13.el7_2.3.x86_64 libvirt-glib-0.1.9-1.el7.x86_64 libvirt-daemon-driver-network-1.2.17-13.el7_2.3.x86_64 libvirt-daemon-driver-lxc-1.2.17-13.el7_2.3.x86_64 libvirt-daemon-driver-interface-1.2.17-13.el7_2.3.x86_64 libvirt-1.2.17-13.el7_2.3.x86_64 libvirt-daemon-1.2.17-13.el7_2.3.x86_64 libvirt-daemon-config-network-1.2.17-13.el7_2.3.x86_64 libvirt-daemon-driver-secret-1.2.17-13.el7_2.3.x86_64 libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.3.x86_64 libvirt-daemon-kvm-1.2.17-13.el7_2.3.x86_64 libvirt-daemon-driver-qemu-1.2.17-13.el7_2.3.x86_64 -------- engine.log 2017-05-02 09:48:26,505 INFO [org.ovirt.engine.core.bll.UpdateVmDiskCommand] (ajp--127.0.0.1-8702-6) [c3d7125] Lock Acquired to object EngineLock [exclusiveLocks= key: 25c0bcc0-0d3d-4ddc-b103-24ed2ac5aa05 value: VM_DISK_BOOT key: c5fb9190-d059-4d9b-af23-07618ff660ce value: DISK , sharedLocks= key: 25c0bcc0-0d3d-4ddc-b103-24ed2ac5aa05 value: VM ] 2017-05-02 09:48:26,515 INFO [org.ovirt.engine.core.bll.UpdateVmDiskCommand] (ajp--127.0.0.1-8702-6) [c3d7125] Running command: UpdateVmDiskCommand internal: false. Entities affected : ID: c5fb9190-d059-4d9b-af23-07618ff660ce Type: DiskAction group EDIT_DISK_PROPERTIES with role type USER 2017-05-02 09:48:26,562 INFO [org.ovirt.engine.core.bll.ExtendImageSizeCommand] (ajp--127.0.0.1-8702-6) [ae718d8] Running command: ExtendImageSizeCommand internal: true. Entities affected : ID: c5fb9190-d059-4d9b-af23-07618ff660ce Type: DiskAction group EDIT_DISK_PROPERTIES with role type USER 2017-05-02 09:48:26,565 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ExtendImageSizeVDSCommand] (ajp--127.0.0.1-8702-6) [ae718d8] START, ExtendImageSizeVDSCommand( storagePoolId = 715d1ba2-eabe-48db-9aea-c28c30359808, ignoreFailoverLimit = false), log id: 52aac743 2017-05-02 09:48:26,604 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ExtendImageSizeVDSCommand] (ajp--127.0.0.1-8702-6) [ae718d8] FINISH, ExtendImageSizeVDSCommand, log id: 52aac743 2017-05-02 09:48:26,650 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (ajp--127.0.0.1-8702-6) [ae718d8] CommandAsyncTask::Adding CommandMultiAsyncTasks object for command cb7958d9-6eae-44a9-891a- 7fe088a79df8 2017-05-02 09:48:26,651 INFO [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (ajp--127.0.0.1-8702-6) [ae718d8] CommandMultiAsyncTasks::AttachTask: Attaching task 769a4b18-182b-4048-bb34-a276a55ccbff to command cb7958d9-6eae-44a9-891a-7fe088a79df8. 2017-05-02 09:48:26,661 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (ajp--127.0.0.1-8702-6) [ae718d8] Adding task 769a4b18-182b-4048-bb34-a276a55ccbff (Parent Command UpdateVmDisk, Parameters Type org.ovirt.engine.core.common. asynctasks.AsyncTaskParameters), polling hasn't started yet.. 2017-05-02 09:48:26,673 INFO [org.ovirt.engine.core.dal. dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-6) [ae718d8] Correlation ID: c3d7125, Call Stack: null, Custom Event ID: -1, Message: VM sysinfo-73 sysinfo-73_Disk3 disk was updated by admin@internal. 2017-05-02 09:48:26,674 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (ajp--127.0.0.1-8702-6) [ae718d8] BaseAsyncTask::startPollingTask: Starting to poll task 769a4b18-182b-4048-bb34-a276a55ccbff. 2017-05-02 09:48:28,430 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (DefaultQuartzScheduler_Worker-48) [36cd2f7] Polling and updating Async Tasks: 1 tasks, 1 tasks to poll now 2017-05-02 09:48:28,435 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker. HSMGetAllTasksStatusesVDSCommand] (DefaultQuartzScheduler_Worker-48) [36cd2f7] Failed in HSMGetAllTasksStatusesVDS method 2017-05-02 09:48:28,436 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (DefaultQuartzScheduler_Worker-48) [36cd2f7] SPMAsyncTask::PollTask: Polling task 769a4b18-182b-4048-bb34-a276a55ccbff (Parent Command UpdateVmDisk, Parameters Type org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters) returned status finished, result 'cleanSuccess'. 2017-05-02 09:48:28,446 ERROR [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (DefaultQuartzScheduler_Worker-48) [36cd2f7] BaseAsyncTask::logEndTaskFailure: Task 769a4b18-182b-4048-bb34-a276a55ccbff (Parent Command UpdateVmDisk, Parameters Type org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters) ended with failure: -- Result: cleanSuccess -- Message: VDSGenericException: VDSErrorException: Failed to HSMGetAllTasksStatusesVDS, error = Could not acquire resource. Probably resource factory threw an exception.: (), code = 100, -- Exception: VDSGenericException: VDSErrorException: Failed to HSMGetAllTasksStatusesVDS, error = Could not acquire resource. Probably resource factory threw an exception.: (), code = 100 2017-05-02 09:48:28,448 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (DefaultQuartzScheduler_Worker-48) [36cd2f7] CommandAsyncTask::endActionIfNecessary: Al l tasks of command cb7958d9-6eae-44a9-891a-7fe088a79df8 has ended -> executing endAction 2017-05-02 09:48:28,449 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (DefaultQuartzScheduler_Worker-48) [36cd2f7] CommandAsyncTask::endAction: Ending action for 1 tasks (command ID: cb7958d9-6eae-44a9-891a-7fe088a79df8): calling endAction . 2017-05-02 09:48:28,450 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (org.ovirt.thread.pool-8-thread-6) [36cd2f7] CommandAsyncTask::endCommandAction [within thread] context: Attempting to endAction UpdateVmDisk, executionIndex: 0 2017-05-02 09:48:28,501 ERROR [org.ovirt.engine.core.bll.UpdateVmDiskCommand] (org.ovirt.thread.pool-8-thread-6) [c3d7125] Ending command with failure: org.ovirt.engine .core.bll.UpdateVmDiskCommand 2017-05-02 09:48:28,502 ERROR [org.ovirt.engine.core.bll.ExtendImageSizeCommand] (org.ovirt.thread.pool-8-thread-6) Ending command with failure: org.ovirt.engine.core.b ll.ExtendImageSizeCommand 2017-05-02 09:48:28,504 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (org.ovirt.thread.pool-8-thread-6) START, GetImageInfoVDSCommand( stora gePoolId = 715d1ba2-eabe-48db-9aea-c28c30359808, ignoreFailoverLimit = false, storageDomainId = 6a386652-629d-4045-835b-21d2f5c104aa, imageGroupId = c5fb9190-d059-4d9b- af23-07618ff660ce, imageId = 562f5b50-1d1a-457c-8b5f-cd8020611550), log id: 674a2581 2017-05-02 09:48:28,511 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (org.ovirt.thread.pool-8-thread-6) IrsBroker::getImageInfo::Failed gett ing image info imageId = 562f5b50-1d1a-457c-8b5f-cd8020611550 does not exist on domainName = VM01 , domainId = 6a386652-629d-4045-835b-21d2f5c104aa, error code: ImagePathError, message: Image path does not exist or cannot be accessed/created: (u'/rhev/data-center/mnt/blockSD/6a386652-629d-4045- 835b-21d2f5c104aa/images/c5fb9190-d059-4d9b-af23-07618ff660ce',) 2017-05-02 09:48:28,512 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (org.ovirt.thread.pool-8-thread-6) Command org.ovirt.engine.core. vdsbroker.irsbroker.GetImageInfoVDSCommand return value OneImageInfoReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=254, mMessage=Image path does not exist or cannot be accessed/created: (u'/rhev/data-center/mnt/blockSD/6a386652-629d-4045- 835b-21d2f5c104aa/images/c5fb9190-d059-4d9b-af23-07618ff660ce',)]] 2017-05-02 09:48:28,512 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (org.ovirt.thread.pool-8-thread-6) FINISH, GetImageInfoVDSCommand, log id: 674a2581 2017-05-02 09:48:28,533 ERROR [org.ovirt.engine.core.dal. dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-6) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Failed to extend size of the disk 'sysinfo-73_Disk3' to 20 GB, User: admin@internal. 2017-05-02 09:48:28,534 INFO [org.ovirt.engine.core.bll.UpdateVmDiskCommand] (org.ovirt.thread.pool-8-thread-6) Lock freed to object EngineLock [exclusiveLocks= key: 25c0bcc0-0d3d-4ddc-b103-24ed2ac5aa05 value: VM_DISK_BOOT key: c5fb9190-d059-4d9b-af23-07618ff660ce value: DISK , sharedLocks= key: 25c0bcc0-0d3d-4ddc-b103-24ed2ac5aa05 value: VM ] 2017-05-02 09:48:28,541 INFO [org.ovirt.engine.core.dal. dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-6) Correlation ID: c3d7125, Call Stack: null, Custom Event ID: -1, Message: VM sysinfo-73 sysinfo-73_Disk3 disk was updated by admin@internal. 2017-05-02 09:48:28,541 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (org.ovirt.thread.pool-8-thread-6) CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type UpdateVmDisk completed, handling the result. 2017-05-02 09:48:28,541 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (org.ovirt.thread.pool-8-thread-6) CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type UpdateVmDisk succeeded, clearing tasks.

2 3

[Ovirt 4.0] Multiple cluster and multiple storage possible ?
by TranceWorldLogic . 07 May '17

07 May '17

Hi, I am trying to setup ovirt as shown below. DataCenter1 ---------Cluster1 -----host1 ---- NFS1-Data Domain | |-----Cluster2 ------host2-----NFS2-Data Domain As you see in above case I am trying to attach both NFS partition to Datacente1 and I got various behaviour: 1> Once one data domain attached to data center other is failing to attached (e.g. let say NFS1-Data Domain is attached to DataCenter1 then after that NFS2-Data Domain failing to attach DataCenter1) 2> And sometime both data domain successfully got attached but after that host2 is not coming up by saying "host1 cannot access to NFS2-Data Domain and hence moving host1 to Non-Operational" host1 firewall rules are : -------------------------------------------------------------------------------------------------- # iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT icmp -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT tcp -- anywhere anywhere tcp dpt:54321 ACCEPT tcp -- anywhere anywhere tcp dpt:54322 ACCEPT tcp -- anywhere anywhere tcp dpt:sunrpc ACCEPT udp -- anywhere anywhere udp dpt:sunrpc ACCEPT tcp -- anywhere anywhere tcp dpt:ssh ACCEPT udp -- anywhere anywhere udp dpt:snmp ACCEPT tcp -- anywhere anywhere tcp dpt:websm ACCEPT tcp -- anywhere anywhere tcp dpt:16514 ACCEPT tcp -- anywhere anywhere multiport dports rockwell-csp2 ACCEPT tcp -- anywhere anywhere multiport dports rfb:6923 ACCEPT tcp -- anywhere anywhere multiport dports 49152:49216 ACCEPT tcp -- anywhere anywhere tcp dpt:sunrpc ACCEPT tcp -- anywhere anywhere tcp dpt:nfs ACCEPT udp -- anywhere anywhere udp dpt:nfs ACCEPT udp -- anywhere anywhere udp dpt:sunrpc ACCEPT udp -- anywhere anywhere udp dpt:892 ACCEPT tcp -- anywhere anywhere tcp dpt:892 ACCEPT tcp -- anywhere anywhere tcp dpt:ospf-lite REJECT all -- anywhere anywhere reject-with icmp-host-prohibited Chain FORWARD (policy ACCEPT) target prot opt source destination REJECT all -- anywhere anywhere PHYSDEV match ! --physdev-is-bridged reject-with icmp-host-prohibited Chain OUTPUT (policy ACCEPT) target prot opt source destination -------------------------------------------------------------------------------------------------- Please help me to understand this issue. 1> Do ovirt support multiple-cluster to multiple-storage data domain ? 2> Are those firewall rules correct or wrong ? 3> Can host1 access storage domain created on another cluster say host2 m/c ? (NFS technology) Thanks, ~Rohit

2 1

VM Template Error
by Bryan Sockel 07 May '17

07 May '17

Hi, Having an issue a template from a VM's. I am getting the following errors: engine.log 2017-05-02 09:40:10,059-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-24) [2ef2fce] EVENT_ID: USER_ADD_VM_TEMPLATE(48), Correlation ID: 176fdfa7-0467-48f5-9ecc-901e86768c28, Job ID: fed9a848-1971-495a-a391-be1fa4a67908, Call Stack: null, Custom Event ID: -1, Message: Creation of Template test from VM Windows-10-Template was initiated by admin@internal-authz. 2017-05-02 09:48:43,059-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-7-thread-20) [] EVENT_ID: USER_ADD_VM_TEMPLATE_FINISHED_FAILURE(52), Correlation ID: 176fdfa7-0467-48f5-9ecc-901e86768c28, Job ID: fed9a848-1971-495a-a391-be1fa4a67908, Call Stack: null, Custom Event ID: -1, Message: Failed to complete creation of Template test from VM Windows-10-Template. Events Log ID 10803 - VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: u'image=6aa525ad-e7f1-432b-959a-2223f7e77083, domain=e371d380-7194-4950-b901-5f2aed5dfb35' ID 10802 - VDSM vm-host-colo-2 command HSMGetAllTasksStatusesVDS failed: low level Image copy failed

4 7

[oVirt4.1] Does oVirt 4.1 support iSCSI offload?
by wodel youchi 07 May '17

07 May '17

Hi, We have two hypervisors, each one has a 10Gbe nic card with two ports, the cards support iSCSI offload. Does oVirt 4.1 support this? if yes how can someone use it on hosted-engine deployment? the VM engine will be in the SAN targeted by these cards. Regards. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

3 4

New oVirt Node install on oVirt Cluster 4.0.5 - How can I install oVirt Node with same 4.0.5 version ???
by Rogério Ceni Coelho 07 May '17

07 May '17

Hi oVirt Troopers, I have two segregated oVirt Clusters running 4.0.5 ( DEV and PROD enviroments). Now i need to install a new oVirt Node Server (Dell PowerEdge M620), but i see that does not exist an 4.0.5 iso on http://resources.ovirt.org/pub/ovirt-4.0/iso/ovirt-node-ng-installer/ , only 4.0.3 and 4.0.6. How can i install this new server and go to the same version of all 20 others ??? There is a way to install 4.0.3 and update to 4.0.5 only ? Thanks in advance.

3 4

command not found
by Brahim Rifahi 07 May '17

07 May '17

I am having issues installing oVirt on a CentOS 7 server. After logging in as sudo, I run the following series of commands: # yum -y update # yum install http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm <http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release35.rpm> # yum -y install ovirt-engine I then attempted to use the following command and received a “command not found” error.

2 1

Change DNS Server
by Kai Wagner 05 May '17

05 May '17

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Ck3WecahvXJaUfA9994GcjRewKPgnskLx Content-Type: multipart/mixed; boundary="R85rSQvBINNVM8UjrG2weAQEIeXGVwVMH"; protected-headers="v1" From: Kai Wagner <kwagner(a)suse.com> To: users(a)ovirt.org Message-ID: <282bf3c4-662c-c871-a495-cad2e540a311(a)suse.com> Subject: Change DNS Server --R85rSQvBINNVM8UjrG2weAQEIeXGVwVMH Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, where can I change the dns server for my hosts? I know the DNS entry is part of the ifcfg-* file, but I tried to change it there and after a reboot the old entry was restored from anywhere. Kai --=20 SUSE Linux GmbH, GF: Felix Imend=C3=B6rffer, Jane Smithard, Graham Norton= , HRB 21284 (AG N=C3=BCrnberg) --R85rSQvBINNVM8UjrG2weAQEIeXGVwVMH-- --Ck3WecahvXJaUfA9994GcjRewKPgnskLx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJY9dKrAAoJEB6MkVYW48RuWuMIAIPFlOXp+ah56n3MlF7t6zJq nlYYbS8JrIX9vo8T9+J4b0qX0RwR0g0TPxP2IzlmFZXTs3nc4r9dhOprFdS0XWKR 52z9S4Mx8BpWJ12HLAqlo5XjeXH/USS7Rc3oD+2t9ZJzA8/ljJ9pLATa/iGzDOcF 1aSHmB/cc+549xNVaOMpS4g8JJJPszmGUMYd3b2Mhquu2iAhhrLu2ZTBjvYhq6IC 6CM7PrDDVjJhi5T3MocHRamLPj6xkfAPEAKvZ3zV3frlpTptTJ4PmEzLcqZ7Tcm+ LTDq4r7gihudFvQ+oOrQKJFtOroZZ8GJ0pgLP86SrY5zlSXmFGkG3Ate64khEAc= =Lka2 -----END PGP SIGNATURE----- --Ck3WecahvXJaUfA9994GcjRewKPgnskLx--

2 3