Check engine.log in /var/log/ovirt-engine on the engine sever/vm On Tue, Jul 28, 2020 at 7:16 PM Philip Brown <pbrown(a)medata.com&gt; wrote:

From what I have observed, OVA import seems to have two modes: If the OVA is a 'foreign' format, the ova file needs to be converted and that conversion effort is then logged into /var/log/vdsm/import on the oVirt node where in import runs. Import failures are then mostly an issue with the inability to either open the OVA file itself for writing or perhaps another temorary file just besides. Under the assumption that the conversion was running under the UID/GID of vdsm, I ensured that write permissions on file and directory were given to vdsm:kvm and at that point the conversion ran fine and spewed plenty of logging output to a file on that path. Now when the OVA came from an oVirt export, that log file doesn't seem to get created, at least I never saw something appear there, even after the import had successfully finished, as per GUI. But those OVA re-imports where completely buggy, mostly because the export files seem to be defect, an error I just reported in another post. For you with a VMware export, things might look more bright, once you sort out access rights and potentially fs capacity, as the conversion might require enough temporary space for two copies of the VM, since it seems to only be put into oVirt storage, after the conversion.

good news and bad news and more good news on my OVA import front. Devs are especially encouraged to read to the end :) Initial good news is, I managed to successfully upgrade ONE of my "node"s in my 4.3 cluster to 4.4.1 The bad news is: doing the exact same thing as before; copying the .OVA file to /root on a node, and attempting an import, doesnt work. and it fails even harder this time. It doesnt just pretend to load it and die at 99%. It fails to allow me to load it at all, with no visible errors? on the native 4.3 node, I do (import OVA) I put in the path as "/root" I press the load button, and it shows me the OVA file in there. BUT. on the 4.4.1 node running in the 4.3 cluster. I put in the path as "/root" I press the load button... and it shows me NO FILES. perms on /root on both nodes, is dr-xr-x--- root root so its not a perms issue. and its literally the same file and name. I just scp'd the file from the 4.4.1 node, to the 4.3 node. I was going to ask for suggestions, but then, one whacky thing I came up with myself. get the dialog to recognize the file, for the 4.3 node. So then it shows up in the first dialog. But then CHANGE the selected node to the 4.4.1 node, before pressing okay?? It takes a bug to fight a bug??. lol. but it started the import on the actual 4.4.1 node...and still failed. But I figured out that the important file is NOT in the engine VM, but in the node that is selected as involved in the import. So in /var/log/vdsm/import/XXXXX, I found a few errors. juggled things around... Forced "preallocate" instead of "thin provision". and.... it worked? ! yay. So, suggestion to devs to test more on the local import, rather than just the "import domain" thing. suggestion #2: I think that in ovirt 4.3, default perms on /root were okay. but in 4.4 a non-root user is used, so it fails to READ THE DIRECTORY. This error should really be passed up to the GUI.