Re: [ovirt-users] After the export, the import OVA failed

2018-03-12 Thread Fabrice SOLER 

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


I saw that :



After that the amon was removed as we can see in the events  :



It seems it does not work. Maybe the VM is hide somewhere ?

Sincerely,




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] After the export, the import OVA failed

2018-03-12 Thread Fabrice SOLER 

Hello,

I found this KB : https://bugzilla.redhat.com/show_bug.cgi?id=1529607
and put a description to the VM disk and the OVA export works ! :-)

Now, the import does not work :-(

The error is : */Failed to load VM configuration from OVA file: 
/data/ova/amon


/*I have tried two ways.
In first, I let the file ova.
Secondely I did  : tar xvf file.ova and specifiy the directory where the 
ovf file is.


In the engine log, I have found this :

2018-03-05 16:15:58,319-04 INFO 
[org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (default 
task-6) [e2a953ca-1460-4899-a958-7dbe37e40a21] Ansible playbook command 
has exited with value: 2
2018-03-05 16:15:58,319-04 ERROR 
[org.ovirt.engine.core.bll.GetVmFromOvaQuery] (default task-6) 
[e2a953ca-1460-4899-a958-7dbe37e40a21] Failed to query OVA info
2018-03-05 16:15:58,319-04 ERROR 
[org.ovirt.engine.core.bll.GetVmFromOvaQuery] (default task-6) 
[e2a953ca-1460-4899-a958-7dbe37e40a21] Query 'GetVmFromOvaQuery' failed: 
EngineException: Failed to query OVA info (Failed with error 
GeneralException and code 100)


I have found this KB : https://bugzilla.redhat.com/show_bug.cgi?id=1529965
The unique solution is a update ?

Sincerely
Fabrice
*//*

Le 05/03/2018 à 13:13, Fabrice SOLER a écrit :

Hello,

Thank for your answer, I have put all permissions for the directory 
and I always have errors.


Here are the ERROR in logs on the engine :

2018-03-05 13:03:18,525-04 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] FINISH, 
GetVolumeInfoVDSCommand, return: 
org.ovirt.engine.core.common.businessentities.storage.DiskImage@90e3c610, 
log id: 84f89c3
2018-03-05 13:03:18,529-04 ERROR 
[org.ovirt.engine.core.bll.CreateOvaCommand] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Command 
'org.ovirt.engine.core.bll.CreateOvaCommand' failed: null
2018-03-05 13:03:18,529-04 ERROR 
[org.ovirt.engine.core.bll.CreateOvaCommand] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] 
Exception: java.lang.NullPointerException

...
2018-03-05 13:03:18,533-04 ERROR 
[org.ovirt.engine.core.bll.exportimport.ExportOvaCommand] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Failed 
to create OVA file
2018-03-05 13:03:18,533-04 INFO 
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Command 
'ExportOva' id: 'c484392e-3540-4a11-97bf-3fecbc13e080' failed when 
attempting to perform the next operation, marking as FAILED 
'[d5d4381b-ec82-4927-91a4-74597cd2511d]'
2018-03-05 13:03:18,533-04 INFO 
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Command 
'ExportOva' id: 'c484392e-3540-4a11-97bf-3fecbc13e080' child commands 
'[d5d4381b-ec82-4927-91a4-74597cd2511d]' executions were completed, 
status 'FAILED'
2018-03-05 13:03:19,542-04 ERROR 
[org.ovirt.engine.core.bll.exportimport.ExportOvaCommand] 
(EE-ManagedThreadFactory-engineScheduled-Thread-98) 
[c99e94b0-a9dd-486f-9274-9aa17c9590a0] Ending command 
'org.ovirt.engine.core.bll.exportimport.ExportOvaCommand' with failure.
2018-03-05 13:03:19,543-04 INFO 
[org.ovirt.engine.core.bll.exportimport.ExportOvaCommand] 
(EE-ManagedThreadFactory-engineScheduled-Thread-98) 
[c99e94b0-a9dd-486f-9274-9aa17c9590a0] Lock freed to object 
'EngineLock:{exclusiveLocks='[3ae307cb-53d6-4d70-87b6-4e073c6f5eb6=VM]', 
sharedLocks=''}'
2018-03-05 13:03:19,550-04 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedThreadFactory-engineScheduled-Thread-98) 
[c99e94b0-a9dd-486f-9274-9aa17c9590a0] EVENT_ID: 
IMPORTEXPORT_EXPORT_VM_TO_OVA_FAILED(1,225), Failed to export Vm 
pfSense as a Virtual Appliance to path /ova/pfSense.ova on Host 
eple-rectorat-proto

...

Sincerely,
Fabrice

Le 05/03/2018 à 12:50, Arik Hadas a écrit :



On Mon, Mar 5, 2018 at 6:48 PM, Arik Hadas > wrote:




On Mon, Mar 5, 2018 at 6:29 PM, Fabrice SOLER
> wrote:

Hello,

I need to export my VM to OVA format from the administration
portail Ovirt. It fails with this message :

/Failed to export Vm CentOS as a Virtual Appliance to path
/data/CentOS.ova on Host eple-rectorat-proto/

My storage is local (not NFS or iSCSI), is there some
particulars permissions to put to the destination directory ?

No, the script that packs the OVA is executed with root permissions.

The path is the path to an export domain ?

Not necessarily.


Oh, and please share the (engine, ansible) logs if you want more eyes 
looking at that failure.


Sincerely,

Fabrice SOLER

-- 


___
Users mailing list

Re: [ovirt-users] After the export, the import OVA failed

2018-03-12 Thread Fabrice SOLER 

Hello,

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 ?

Sincerely,

Fabrice SOLER


Le 06/03/2018 à 10:33, Fabrice SOLER a écrit :

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


I saw that :



After that the amon was removed as we can see in the events  :



It seems it does not work. Maybe the VM is hide somewhere ?

Sincerely,




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] After the export, the import OVA failed

2018-03-06 Thread Oliver Riesener 

> Am 07.03.2018 um 00:03 schrieb Arik Hadas :
> 
> 
> 
> On Wed, Mar 7, 2018 at 12:10 AM, Oliver Riesener 
> > 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 
> 
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 > >:
>> 
>> 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
 
 
 I saw that :
 
 
 
 After that the amon was removed as we can see in the events  :
 
 
 
 It seems it does not work. Maybe the VM is hide somewhere ?
 
 Sincerely,
 
 
 
 
 
 ___
 Users mailing list
 Users@ovirt.org 
 http://lists.ovirt.org/mailman/listinfo/users 
 
>>> 
>>> 
>>> ___
>>> Users mailing list
>>> Users@ovirt.org 
>>> http://lists.ovirt.org/mailman/listinfo/users 
>>> 
>> 
>> -- 
>> 
> 
> 
> ___
> Users mailing list
> Users@ovirt.org 
> http://lists.ovirt.org/mailman/listinfo/users 
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] After the export, the import OVA failed

2018-03-06 Thread Arik Hadas 
On Wed, Mar 7, 2018 at 12:10 AM, Oliver Riesener <
oliver.riese...@hs-bremen.de> 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

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


>
> Please see attachments:
>
> Cheers
> Olri
>
>
>
>
>
> Am 06.03.2018 um 19:25 schrieb Fabrice SOLER  fr>:
>
> 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
>
> 
> I saw that :
>
> 
>
> After that the amon was removed as we can see in the events  :
>
> 
>
> It seems it does not work. Maybe the VM is hide somewhere ?
>
> Sincerely,
>
>
> 
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
> --
> 
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] After the export, the import OVA failed

2018-03-06 Thread Oliver Riesener 
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/ovaI 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 ? Please see attachments:CheersOlri

ovirt-4.2.1-failed-to-import-OVA.engine.log
Description: Binary data


ovirt-import-ova-ansible-20180306223007-ovn-elem.example.org-45e9a51.log
Description: Binary data


ovirt-query-ova-ansible-20180306222952-ovn-elem.example.org.log
Description: Binary data
Am 06.03.2018 um 19:25 schrieb Fabrice SOLER :
  

  
  
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
  
  
  I saw that :
  
  
  
  After that the amon was removed as we can see in the events  :
  
  
  
  It seems it does not work. Maybe the VM is hide somewhere ?
  
  Sincerely,
  
  
  



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

  
  
  
  
  ___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



-- 
  
  

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] After the export, the import OVA failed

2018-03-06 Thread Arik Hadas 
On Tue, Mar 6, 2018 at 10:23 PM, Fabrice SOLER  wrote:

> Hello,
>
> I have imported a VM with OVA created with VMware and it works !
>

That's great, but note that importing an OVA that was created by VMware is
totally different than importing an OVA that was created by oVirt
implementation-wise.


> So, the problem is in the export ! The vm.ovf has no line terminators,
> that why it does not work !
>
> * [root@ovirt-eple amon]# file vm.ovf*
> * vm.ovf: XML 1.0 document, ASCII text, with very long lines, with no line
> terminators*
>
> Is there somebody would know a solution ?
>

I'm afraid that's not the issue here - the OVF inside the OVA seems valid
(otherwise, the UI would have failed to "load" the configuration from the
OVA file).
You may be facing one of the various issues that were already resolved and
will be available in 4.2.2, but it's hard to tell without having the logs.
If you can share the engine+ansible logs, we will gladly look at them and
try to shed more light on the issue you're facing.
Otherwise, I would suggest to wait for 4.2.2 where the new OVA support is
much more mature.


>
> Sincerely,
> Fabrice SOLER
>
>
>
> Le 06/03/2018 à 14:25, Fabrice SOLER a écrit :
>
> 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
>
>
> I saw that :
>
>
>
> After that the amon was removed as we can see in the events  :
>
>
>
> It seems it does not work. Maybe the VM is hide somewhere ?
>
> Sincerely,
>
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
> --
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
> --
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] After the export, the import OVA failed

2018-03-06 Thread Fabrice SOLER 

Hello,

I have imported a VM with OVA created with VMware and it works !
So, the problem is in the export ! The vm.ovf has no line terminators, 
that why it does not work !

*/
/**/[root@ovirt-eple amon]# file vm.ovf/**/
/**/vm.ovf: XML 1.0 document, ASCII text, with very long lines, with no 
line terminators/**/

/*
Is there somebody would know a solution ?

Sincerely,
Fabrice SOLER


Le 06/03/2018 à 14:25, Fabrice SOLER a écrit :

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


I saw that :



After that the amon was removed as we can see in the events :



It seems it does not work. Maybe the VM is hide somewhere ?

Sincerely,




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



--


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



--
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] After the export, the import OVA failed

2018-03-06 Thread Fabrice SOLER 

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


I saw that :



After that the amon was removed as we can see in the events  :



It seems it does not work. Maybe the VM is hide somewhere ?

Sincerely,




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



--
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] After the export, the import OVA failed

2018-03-06 Thread Fabrice SOLER 

Hello,

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 ?

Sincerely,

Fabrice SOLER


Le 06/03/2018 à 10:33, Fabrice SOLER a écrit :

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


I saw that :



After that the amon was removed as we can see in the events  :



It seems it does not work. Maybe the VM is hide somewhere ?

Sincerely,




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



--
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] After the export, the import OVA failed

2018-03-06 Thread Oliver Riesener 

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


I saw that :



After that the amon was removed as we can see in the events  :



It seems it does not work. Maybe the VM is hide somewhere ?

Sincerely,




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] After the export, the import OVA failed

2018-03-06 Thread Fabrice SOLER 

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


I saw that :



After that the amon was removed as we can see in the events  :



It seems it does not work. Maybe the VM is hide somewhere ?

Sincerely,


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] After the export, the import OVA failed

2018-03-05 Thread Arik Hadas 
On Mon, Mar 5, 2018 at 11:01 PM, Fabrice SOLER <
fabrice.so...@ac-guadeloupe.fr> wrote:

> Hello,
>
> I found this KB : https://bugzilla.redhat.com/show_bug.cgi?id=1529607
> and put a description to the VM disk and the OVA export works ! :-)
>
> Now, the import does not work :-(
>
> The error is :
>
> *Failed to load VM configuration from OVA file: /data/ova/amon *I have
> tried two ways.
> In first, I let the file ova.
> Secondely I did  : tar xvf file.ova and specifiy the directory where the
> ovf file is.
>
> In the engine log, I have found this :
>
> 2018-03-05 16:15:58,319-04 INFO  
> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
> (default task-6) [e2a953ca-1460-4899-a958-7dbe37e40a21] Ansible playbook
> command has exited with value: 2
> 2018-03-05 16:15:58,319-04 ERROR [org.ovirt.engine.core.bll.GetVmFromOvaQuery]
> (default task-6) [e2a953ca-1460-4899-a958-7dbe37e40a21] Failed to query
> OVA info
> 2018-03-05 16:15:58,319-04 ERROR [org.ovirt.engine.core.bll.GetVmFromOvaQuery]
> (default task-6) [e2a953ca-1460-4899-a958-7dbe37e40a21] Query
> 'GetVmFromOvaQuery' failed: EngineException: Failed to query OVA info
> (Failed with error GeneralException and code 100)
>
> I have found this KB : https://bugzilla.redhat.com/show_bug.cgi?id=1529965
> The unique solution is a update ?
>

I highly suggest updating to the latest version, various issues related to
OVA export/import were recently fixed.


>
> Sincerely
> Fabrice
>
>
> Le 05/03/2018 à 13:13, Fabrice SOLER a écrit :
>
> Hello,
>
> Thank for your answer, I have put all permissions for the directory and I
> always have errors.
>
> Here are the ERROR in logs on the engine :
>
> 2018-03-05 13:03:18,525-04 INFO  [org.ovirt.engine.core.
> vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-23)
> [7dcef072] FINISH, GetVolumeInfoVDSCommand, return:
> org.ovirt.engine.core.common.businessentities.storage.DiskImage@90e3c610,
> log id: 84f89c3
> 2018-03-05 13:03:18,529-04 ERROR [org.ovirt.engine.core.bll.CreateOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Command
> 'org.ovirt.engine.core.bll.CreateOvaCommand' failed: null
> 2018-03-05 13:03:18,529-04 ERROR [org.ovirt.engine.core.bll.CreateOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Exception:
> java.lang.NullPointerException
> ...
> 2018-03-05 13:03:18,533-04 ERROR 
> [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Failed to
> create OVA file
> 2018-03-05 13:03:18,533-04 INFO  [org.ovirt.engine.core.bll.
> SerialChildCommandsExecutionCallback] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-23)
> [7dcef072] Command 'ExportOva' id: 'c484392e-3540-4a11-97bf-3fecbc13e080'
> failed when attempting to perform the next operation, marking as FAILED
> '[d5d4381b-ec82-4927-91a4-74597cd2511d]'
> 2018-03-05 13:03:18,533-04 INFO  [org.ovirt.engine.core.bll.
> SerialChildCommandsExecutionCallback] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-23)
> [7dcef072] Command 'ExportOva' id: 'c484392e-3540-4a11-97bf-3fecbc13e080'
> child commands '[d5d4381b-ec82-4927-91a4-74597cd2511d]' executions were
> completed, status 'FAILED'
> 2018-03-05 13:03:19,542-04 ERROR 
> [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [c99e94b0-a9dd-486f-9274-9aa17c9590a0] Ending command
> 'org.ovirt.engine.core.bll.exportimport.ExportOvaCommand' with failure.
> 2018-03-05 13:03:19,543-04 INFO  
> [org.ovirt.engine.core.bll.exportimport.ExportOvaCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [c99e94b0-a9dd-486f-9274-9aa17c9590a0] Lock freed to object
> 'EngineLock:{exclusiveLocks='[3ae307cb-53d6-4d70-87b6-4e073c6f5eb6=VM]',
> sharedLocks=''}'
> 2018-03-05 13:03:19,550-04 ERROR [org.ovirt.engine.core.dal.
> dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-98)
> [c99e94b0-a9dd-486f-9274-9aa17c9590a0] EVENT_ID:
> IMPORTEXPORT_EXPORT_VM_TO_OVA_FAILED(1,225), Failed to export Vm pfSense
> as a Virtual Appliance to path /ova/pfSense.ova on Host eple-rectorat-proto
> ...
>
> Sincerely,
> Fabrice
>
> Le 05/03/2018 à 12:50, Arik Hadas a écrit :
>
>
>
> On Mon, Mar 5, 2018 at 6:48 PM, Arik Hadas  wrote:
>
>>
>>
>> On Mon, Mar 5, 2018 at 6:29 PM, Fabrice SOLER <
>> fabrice.so...@ac-guadeloupe.fr> wrote:
>>
>>> Hello,
>>>
>>> I need to export my VM to OVA format from the administration portail
>>> Ovirt. It fails with this message :
>>>
>>> *Failed to export Vm CentOS as a Virtual Appliance to path
>>> /data/CentOS.ova on Host eple-rectorat-proto*
>>>
>>> My storage is local (not NFS or iSCSI), is there some particulars
>>> permissions to put to the destination directory ?
>>>
>> No, the script that packs the OVA is executed with root permissions.
>>
>>
>>> The path is the path to an export domain ?
>>>
>> Not

[ovirt-users] After the export, the import OVA failed

2018-03-05 Thread Fabrice SOLER 

Hello,

I found this KB : https://bugzilla.redhat.com/show_bug.cgi?id=1529607
and put a description to the VM disk and the OVA export works ! :-)

Now, the import does not work :-(

The error is : */Failed to load VM configuration from OVA file: 
/data/ova/amon


/*I have tried two ways.
In first, I let the file ova.
Secondely I did  : tar xvf file.ova and specifiy the directory where the 
ovf file is.


In the engine log, I have found this :

2018-03-05 16:15:58,319-04 INFO 
[org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (default 
task-6) [e2a953ca-1460-4899-a958-7dbe37e40a21] Ansible playbook command 
has exited with value: 2
2018-03-05 16:15:58,319-04 ERROR 
[org.ovirt.engine.core.bll.GetVmFromOvaQuery] (default task-6) 
[e2a953ca-1460-4899-a958-7dbe37e40a21] Failed to query OVA info
2018-03-05 16:15:58,319-04 ERROR 
[org.ovirt.engine.core.bll.GetVmFromOvaQuery] (default task-6) 
[e2a953ca-1460-4899-a958-7dbe37e40a21] Query 'GetVmFromOvaQuery' failed: 
EngineException: Failed to query OVA info (Failed with error 
GeneralException and code 100)


I have found this KB : https://bugzilla.redhat.com/show_bug.cgi?id=1529965
The unique solution is a update ?

Sincerely
Fabrice


Le 05/03/2018 à 13:13, Fabrice SOLER a écrit :

Hello,

Thank for your answer, I have put all permissions for the directory 
and I always have errors.


Here are the ERROR in logs on the engine :

2018-03-05 13:03:18,525-04 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] FINISH, 
GetVolumeInfoVDSCommand, return: 
org.ovirt.engine.core.common.businessentities.storage.DiskImage@90e3c610, 
log id: 84f89c3
2018-03-05 13:03:18,529-04 ERROR 
[org.ovirt.engine.core.bll.CreateOvaCommand] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Command 
'org.ovirt.engine.core.bll.CreateOvaCommand' failed: null
2018-03-05 13:03:18,529-04 ERROR 
[org.ovirt.engine.core.bll.CreateOvaCommand] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] 
Exception: java.lang.NullPointerException

...
2018-03-05 13:03:18,533-04 ERROR 
[org.ovirt.engine.core.bll.exportimport.ExportOvaCommand] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Failed 
to create OVA file
2018-03-05 13:03:18,533-04 INFO 
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Command 
'ExportOva' id: 'c484392e-3540-4a11-97bf-3fecbc13e080' failed when 
attempting to perform the next operation, marking as FAILED 
'[d5d4381b-ec82-4927-91a4-74597cd2511d]'
2018-03-05 13:03:18,533-04 INFO 
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
(EE-ManagedThreadFactory-engineScheduled-Thread-23) [7dcef072] Command 
'ExportOva' id: 'c484392e-3540-4a11-97bf-3fecbc13e080' child commands 
'[d5d4381b-ec82-4927-91a4-74597cd2511d]' executions were completed, 
status 'FAILED'
2018-03-05 13:03:19,542-04 ERROR 
[org.ovirt.engine.core.bll.exportimport.ExportOvaCommand] 
(EE-ManagedThreadFactory-engineScheduled-Thread-98) 
[c99e94b0-a9dd-486f-9274-9aa17c9590a0] Ending command 
'org.ovirt.engine.core.bll.exportimport.ExportOvaCommand' with failure.
2018-03-05 13:03:19,543-04 INFO 
[org.ovirt.engine.core.bll.exportimport.ExportOvaCommand] 
(EE-ManagedThreadFactory-engineScheduled-Thread-98) 
[c99e94b0-a9dd-486f-9274-9aa17c9590a0] Lock freed to object 
'EngineLock:{exclusiveLocks='[3ae307cb-53d6-4d70-87b6-4e073c6f5eb6=VM]', 
sharedLocks=''}'
2018-03-05 13:03:19,550-04 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedThreadFactory-engineScheduled-Thread-98) 
[c99e94b0-a9dd-486f-9274-9aa17c9590a0] EVENT_ID: 
IMPORTEXPORT_EXPORT_VM_TO_OVA_FAILED(1,225), Failed to export Vm 
pfSense as a Virtual Appliance to path /ova/pfSense.ova on Host 
eple-rectorat-proto

...

Sincerely,
Fabrice

Le 05/03/2018 à 12:50, Arik Hadas a écrit :



On Mon, Mar 5, 2018 at 6:48 PM, Arik Hadas > wrote:




On Mon, Mar 5, 2018 at 6:29 PM, Fabrice SOLER
> wrote:

Hello,

I need to export my VM to OVA format from the administration
portail Ovirt. It fails with this message :

/Failed to export Vm CentOS as a Virtual Appliance to path
/data/CentOS.ova on Host eple-rectorat-proto/

My storage is local (not NFS or iSCSI), is there some
particulars permissions to put to the destination directory ?

No, the script that packs the OVA is executed with root permissions.

The path is the path to an export domain ?

Not necessarily.


Oh, and please share the (engine, ansible) logs if you want more eyes 
looking at that failure.


Sincerely,

Fabrice SOLER

-- 


___
Users mailing list