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.
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.
engine.log, vdsm.log and ovirt-query-ova-ansible.log attached
Created attachment 1443036 [details]
Created attachment 1443038 [details]
Created attachment 1443048 [details]
ovirt-query-ova-ansible, empty log (task hangs forever)
Created attachment 1443049 [details]
Created attachment 1443050 [details]
Seems that the output returned by ansible is limited by 64k...
Should not be retested yet as it depends on bz 1610758
QE verification bot: the bug was verified upstream