> Am 07.03.2018 um 00:03 schrieb Arik Hadas <[email protected]>: > > > > On Wed, Mar 7, 2018 at 12:10 AM, Oliver Riesener > <[email protected] <mailto:[email protected]>> wrote: > Hi Arik, Hi Fabrice, > > i have tried the same procedure with 4.2.1, with same results. > > After commands: > > # mkdir /var/log/ovirt-engine/ova > # chown ovirt.ovirt /var/log/ovirt-engine/ova > > I can provide log files. See ansible script failed. > > /export/ovirt/export/xx is the correct directory where i have extracted the > *.ova file because the UI search for *.ovf file and didn’t recognize *.ova > files directly ? > > Thanks for providing the logs. > We don't support OVA directory with content (OVF, disks) that was created by > oVirt yet (it only works with content that was created by VMware). > The OVA tar file should not be extracted and the path to the OVA should > include the filename, e.g., /export/ovirt/export/xx/my.ova
With the fullname to *.ova, the VM is importable. yeah! > If you pack the directory's content into an OVA file, please note that the > OVF should be placed at the first entry. > > There is a bug about changing 'path' to something like 'path to ova file' in > the import dialog [1], I may add a validation for that as well until we'll > also support the OVA directory format. > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1547636 > <https://bugzilla.redhat.com/show_bug.cgi?id=1547636> At this point, path is ok, but *.ova should be **browsed** too. > > > Please see attachments: > > Cheers > Olri > > > > > >> Am 06.03.2018 um 19:25 schrieb Fabrice SOLER <[email protected] >> <mailto:[email protected]>>: >> >> Hi, >> >> I have deleted the VM amon and tried to import the OVA. It does not work. >> I think there is a problem in the ovf file (XML format) like I posted in the >> precedente mail : >> >> I constated that the ovf format is not the same when I made the export ova >> with vmware and ovirt. >> >> Export ova with vmware : >> >> [root@eple-rectorat-proto AntiVirus]# file AntiVirus.ovf >> AntiVirus.ovf: XML 1.0 document, ASCII text, with very long lines, with CRLF >> line terminators >> >> Export ova with ovirt : >> [root@ovirt-eple amon]# file vm.ovf >> vm.ovf: XML 1.0 document, ASCII text, with very long lines, with no line >> terminators >> >> With Ovirt there is no line terminators. >> >> Is that normal ? Is that why the OVA import does not work ? >> >> >> >> >> >> >> >> Le 06/03/2018 à 12:11, Oliver Riesener a écrit : >>> Hi Fabrice, >>> try to rename the already existing old VM to another name like amon-old. >>> The import the OVA machine again. >>> >>> On 06.03.2018 15:33, Fabrice SOLER wrote: >>>> Hello, >>>> >>>> I have upgraded the engine and the node, so the version is : >>>> 4.2.1.1.1-1.el7 >>>> To import, I made a "tar xvf file.ova". >>>> Then from the portal, I import the VM >>>> >>>> <fnoenhmgochfekoh.png> >>>> I saw that : >>>> >>>> <ieaciiocgjjgcbcg.png> >>>> >>>> After that the amon was removed as we can see in the events : >>>> >>>> <hljdjnbeojagoppc.png> >>>> >>>> It seems it does not work. Maybe the VM is hide somewhere ? >>>> >>>> Sincerely, >>>> >>>> >>>> <Fabrice SOLER.PNG> >>>> >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> [email protected] <mailto:[email protected]> >>>> http://lists.ovirt.org/mailman/listinfo/users >>>> <http://lists.ovirt.org/mailman/listinfo/users> >>> >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] <mailto:[email protected]> >>> http://lists.ovirt.org/mailman/listinfo/users >>> <http://lists.ovirt.org/mailman/listinfo/users> >> >> -- >> <Fabrice SOLER.PNG> > > > _______________________________________________ > Users mailing list > [email protected] <mailto:[email protected]> > http://lists.ovirt.org/mailman/listinfo/users > <http://lists.ovirt.org/mailman/listinfo/users>
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
