Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1568755

Summary: [RFE] Ability to specify a folder of OVAs in import-VMs dialog
Product: [oVirt] ovirt-engine Reporter: Arik <ahadas>
Component: BLL.VirtAssignee: Arik <ahadas>
Status: CLOSED CURRENTRELEASE QA Contact: Nisim Simsolo <nsimsolo>
Severity: low Docs Contact:
Priority: medium    
Version: 4.3.0CC: bugs, mperina, nsimsolo
Target Milestone: ovirt-4.2.6Keywords: FutureFeature
Target Release: ---Flags: rule-engine: ovirt-4.2?
rule-engine: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: Listing OVAs in a specified folder. Reason: Ease importing of VMs from OVA. Result: The user can provide a folder in import-VM dialog and as a result, will be provided with all the OVAs that reside in that folder.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-03 15:10:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1610758    
Bug Blocks:    
Attachments:
Description Flags
vdsm.log
none
engine.log
none
ovirt-query-ova-ansible, empty log (task hangs forever)
none
ovirt-query-ova-ansible log1
none
ovirt-query-ova-ansible log2 none

Description Arik 2018-04-18 08:57:45 UTC
It is still confusing that the import-VMs dialog requires specifying a path to a specific OVA file rather than to a folder that may contain few OVAs. This RFE is about supporting a folder as an input and then listing the OVAs that the given folder contains.

Comment 1 Nisim Simsolo 2018-05-28 08:57:06 UTC
Reassigned:
1. When specifying folder of OVAs in import dialog, the task hangs forever. Observing engine tasks also shows that ovirt-ova-query hangs forever.
2. In case of OVFs in the OVAs folder, the import dialog is showing only one VM available to import (which is the OVF VM) instead of all the available OVAs to import.

Verification builds:
rhvm-4.2.4-0.1.el7
libvirt-client-3.9.0-14.el7_5.5.x86_64
qemu-kvm-rhev-2.10.0-21.el7_5.3.x86_64
vdsm-4.20.28-1.el7ev.x86_64
sanlock-3.6.0-1.el7.x86_64
virt-v2v-1.36.10-6.10.rhvpreview.el7ev.x86_64

engine.log, vdsm.log and ovirt-query-ova-ansible.log attached

Comment 2 Nisim Simsolo 2018-05-28 09:01:15 UTC
Created attachment 1443036 [details]
vdsm.log

Comment 3 Nisim Simsolo 2018-05-28 09:02:04 UTC
Created attachment 1443038 [details]
engine.log

Comment 4 Nisim Simsolo 2018-05-28 09:05:04 UTC
Created attachment 1443048 [details]
ovirt-query-ova-ansible, empty log (task hangs forever)

Comment 5 Nisim Simsolo 2018-05-28 09:05:43 UTC
Created attachment 1443049 [details]
ovirt-query-ova-ansible log1

Comment 6 Nisim Simsolo 2018-05-28 09:06:10 UTC
Created attachment 1443050 [details]
ovirt-query-ova-ansible log2

Comment 8 Arik 2018-06-27 13:58:28 UTC
Seems that the output returned by ansible is limited by 64k...

Comment 9 Arik 2018-08-06 13:08:20 UTC
Should not be retested yet as it depends on bz 1610758

Comment 10 Nisim Simsolo 2018-08-28 15:19:54 UTC
Verified_upstream:
ovirt-engine-4.2.6.4-0.0.master.20180823141941.gitb3a5b18.el7
qemu-kvm-rhev-2.10.0-21.el7_5.5.x86_64
libvirt-client-3.9.0-14.el7_5.7.x86_64
vdsm-4.20.38-8.git9f3cc73.el7.x86_64

Comment 11 Raz Tamir 2018-08-28 19:30:29 UTC
QE verification bot: the bug was verified upstream