Description of problem: Cannot import template from OVA file Version-Release number of selected component (if applicable): ovirt-engine-4.4.0-0.33.master.el8ev.noarch (Beta) vdsm-4.40.13-1.el8ev.x86_64 How reproducible: always Steps to Reproduce: 1. Export template to ova (4.3 environment) 2. copy to 4.4 hypervisor (/var/log) 3. Compute -> Templates - Import. Source = Virtual Appliance (OVA) 4. Select host and file path (/var/log), select template, move across, and select 'Next' 5. For the Template, select correct storage domain (not 'Hosted_storage') and select 'ok' Actual results: Error: "Failed to import Template rhel8-template to Data Center Default, Cluster Default" Expected results: Success - be able to create new VM's from the template. Additional info: from engine.log: 2020-05-22 09:59:09,719+10 ERROR [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-97) [81961035-01e6-440a-b4a4-489ee373ba96] Exception: Failed to execute call to start playbook. 2020-05-22 09:59:09,719+10 ERROR [org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-97) [81961035-01e6-440a-b4a4-489ee373ba96] Failed to extract OVA. Please check logs for more details: /var/log/ovirt-engine/ova/ovirt-import-ova-ansible-20200522095909-beef3.<domain>-81961035-01e6-440a-b4a4-489ee373ba96.log 2020-05-22 09:59:09,893+10 ERROR [org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-97) [81961035-01e6-440a-b4a4-489ee373ba96] Failed to extract OVA file 2020-05-22 09:59:10,968+10 ERROR [org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) [81961035-01e6-440a-b4a4-489ee373ba96] Ending command 'org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand' with failure. 2020-05-22 09:59:12,025+10 ERROR [org.ovirt.engine.core.bll.exportimport.ImportVmTemplateFromOvaCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-78) [81961035-01e6-440a-b4a4-489ee373ba96] Ending command 'org.ovirt.engine.core.bll.exportimport.ImportVmTemplateFromOvaCommand' with failure. The above log does not seem to exist
There's indeed just 2020-05-22 09:59:09,719+10 ERROR [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-97) [ 81961035-01e6-440a-b4a4-489ee373ba96] Exception: Failed to execute call to start playbook. 2020-05-22 09:59:09,719+10 ERROR [org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-97) [81961035-01e6-440a-b4a4-489ee373ba96] Failed to extract OVA. Please check logs for more details: /var/log/ovirt-engine/ova/ovirt-import-ova-ansible-20200522095909-beef3.gsslab.pek2.redhat.com-81961035-01e6-440a-b4a4-489ee373ba96.log Martin, it looks like ansible infrastructure issues. I'm not sure how to interpret ansible runner log
Looking on the version now 4.4 beta (4.4.0-0.33) is when we had many issues in OVA because of ansible-runner service. Please save the 4.3 OVA that we can have it if the bug persist, but on a newer engine version it should be resolved.
OK, moving to 4.4.1 and marking as TestOnly bug
Moving due 4.4.2 due to dependant bug is in 4.4.2, if both should be in 4.4.1 or 4.4.1-1 please align milestone and bug states.
If the imported VM runs on a new cluster this means it would most probably run on a new 4.4 environment (where the Default cluster is created with engine that includes [1]) or on a cluster that was upgraded from 4.3 to 4.4 version that includes the aforementioned patch. We can wait for the fix for bz 1853909 to provide a complete solution but as this bug was reported on a failure to import, which means import templates from OVAs would always fail, and now it is about failing to run the imported VMs on very particular clusters - I would say that we should treat those as two separate issues. So I'd suggest to scope it like that: (1) This bug: import template from OVA to a target cluster that is either (a) created in latest version; or (b) upgraded from 4.3/4.2 to latest version. (2) bz 1853909: will focus on running VMs that were created/imported to clusters which were created/upgraded in version 4.4 without [1]. Nisim, would that make sense? [1] https://gerrit.ovirt.org/#/c/108979/
Can be verified on 4.4.2 - keep the TestOnly (the fix for bz 1853909 should cover it)
querying OVA failed with: 2020-08-19 10:09:06,308+03 ERROR [org.ovirt.engine.core.bll.GetVmFromOvaQuery] (default task-59) [1f065af4-0fd4-48f4-925d-6a8326d7698e] Query 'GetVmFromOvaQuery' failed: EngineException: Failed to query OVA info (Failed with error GeneralException and code 100) adding https://bugzilla.redhat.com/show_bug.cgi?id=1869302 as depends on
Verified: ovirt-engine-4.4.2.3-0.6.el8ev vdsm-4.40.26-1.el8ev.x86_64 libvirt-daemon-6.0.0-25.module+el8.2.1+7154+47ffd890.x86_64 qemu-kvm-4.2.0-29.module+el8.2.1+7297+a825794d.x86_64 Verification scenario (using exported OVA from https://bugzilla.redhat.com/show_bug.cgi?id=1838877#c6): 1. Export template to ova (4.3 environment) 2. copy to 4.4 hypervisor (/var/log) 3. Compute -> Templates - Import. Source = Virtual Appliance (OVA) 4. Select host and file path (/var/log), select template, move across, and select 'Next' 5. For the Template, select correct storage domain (not 'Hosted_storage') and select 'ok'
This bugzilla is included in oVirt 4.4.2 release, published on September 17th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.