OLVM: Importing/Exporting Large OVA File Fail with "Timeout occurred while executing Ansible playbook." (Doc ID 2716944.1)

Last updated on MAY 07, 2024

Applies to:

Symptoms

When importing/exporting a large ova file(200Gb+), it fails with the below error in engine.log:

Importing error in engine.log:

INFO [org.ovirt.engine.core.bll.exportimport.ImportVmFromOvaCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-44) [466
4102e] Lock freed to object 'EngineLock:{exclusiveLocks='[956ef89d-fd95-4438-86e6-289cdadb40b1=VM, nova-innodb1=VM_NAME]', sharedLocks=''}'
ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-44)[4664102e] 
EVENT_ID: IMPORTEXPORT_IMPORT_VM_FAILED(1,153), Failed to import Vm <VM Name> to Data Center Default, Cluster Default

Exporting error in engine.log:

INFO [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (EE-ManagedThreadFactory-engine-Thread-2037077) [632c26b0-c1b1-4849-856e-99aa87c1639b] 
Running command: ExportVmToOvaCommand internal: false. Entities affected : ID: d0c81155-7020-457d-bf5a-77189c272787 Type: VMAction group IMPORT_EXPORT_VM with role type ADMIN
...
ERROR [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [4d63375] Ansible playbook execution failed: Timeout occurred while executing Ansible playbook.
ERROR [org.ovirt.engine.core.bll.CreateOvaCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [4d63375] Failed to create OVA. 
Please check logs for more details: /var/log/ovirt-engine/ova/ovirt-export-ova-ansible-20201210115209-tgvm3.msctrustgate.com-4d63375.log
ERROR [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [4d63375] Failed to create OVA file
ERROR [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [4d63375] Command 'ExportVmToOva' id: '0e6a1177-b828-4a69-b70a-095f0ee62843' with 
children [fbcebcff-7175-471e-afe3-c5f667709c01] failed when attempting to perform the next operation, marking as 'ACTIVE'
ERROR [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-33) [4d63375] EngineException: ENGINE (Failed with error ENGINE and code 5001): 
org.ovirt.engine.core.common.errors.EngineException: EngineException: ENGINE (Failed with error ENGINE and code 5001)

vdsm.log doesn't report related errors. 

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.