[ovirt-users] Failed to read VM '[Empty Name]' OVF, it may be corrupted

[Tomas Jelinek]

Hi Jon,

could you please attach the ovf files here? 
Somewhere in the export domain you should have files with .ovf extension which is an XML describing the VM. I'd say they will be corrupted.

Thanx, 
Tomas

----- Original Message -----
> From: "Jon Archer" <jon at rosslug.org.uk>
> To: users at ovirt.org
> Sent: Wednesday, March 18, 2015 12:36:14 AM
> Subject: [ovirt-users] Failed to read VM '[Empty Name]' OVF,	it may be corrupted
> 
> Hi all,
> 
> seing a strange issue here, I'm currently in the process of migrating
> from one ovirt setup to another and having trouble with the
> export/import process.
> 
> The new setup is a 3.5 install with hosted engine and glusterfs the old
> one is running on a nightly release (not too recent)
> 
> I have brought up an NFS export on the existing storage on the old
> setup, successfully exported a number of VM's and imported them onto the
> new system.
> 
> However I came to move the last 4 VM's and am seeing an issue where
> after attaching the export storage to the new setup I see no VMs in the
> export storage to import and see this in the log:
> 2015-03-17 23:30:56,742 INFO
> [org.ovirt.engine.core.vdsbroker.irsbroker.GetVmsInfoVDSCommand]
> (ajp--127.0.0.1-8702-8) START, GetVmsInfoVDSCommand( storagePoolId =
> 00000002-0002-0002-0002-000000000209, ignoreFailoverLimit = false,
> storageDomainId = 86f85b1d-a9ef-4106-a4bf-eae19722d28a, vmIdList =
> null), log id: e2a32ac
> 2015-03-17 23:30:56,766 INFO
> [org.ovirt.engine.core.vdsbroker.irsbroker.GetVmsInfoVDSCommand]
> (ajp--127.0.0.1-8702-8) FINISH, GetVmsInfoVDSCommand, log id: e2a32ac
> 2015-03-17 23:30:56,798 ERROR
> [org.ovirt.engine.core.utils.ovf.OvfManager] (ajp--127.0.0.1-8702-8)
> Error parsing OVF due to 2
> 2015-03-17 23:30:56,818 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ajp--127.0.0.1-8702-8) Correlation ID: null, Call Stack: null, Custom
> Event ID: -1, Message: Failed to read VM '[Empty Name]' OVF, it may be
> corrupted
> 2015-03-17 23:30:56,867 ERROR
> [org.ovirt.engine.core.utils.ovf.OvfManager] (ajp--127.0.0.1-8702-8)
> Error parsing OVF due to 2
> 2015-03-17 23:30:56,884 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ajp--127.0.0.1-8702-8) Correlation ID: null, Call Stack: null, Custom
> Event ID: -1, Message: Failed to read VM '[Empty Name]' OVF, it may be
> corrupted
> 2015-03-17 23:30:56,905 ERROR
> [org.ovirt.engine.core.utils.ovf.OvfManager] (ajp--127.0.0.1-8702-8)
> Error parsing OVF due to 2
> 2015-03-17 23:30:56,925 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ajp--127.0.0.1-8702-8) Correlation ID: null, Call Stack: null, Custom
> Event ID: -1, Message: Failed to read VM '[Empty Name]' OVF, it may be
> corrupted
> 2015-03-17 23:30:56,943 ERROR
> [org.ovirt.engine.core.utils.ovf.OvfManager] (ajp--127.0.0.1-8702-8)
> Error parsing OVF due to 2
> 2015-03-17 23:30:56,992 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ajp--127.0.0.1-8702-8) Correlation ID: null, Call Stack: null, Custom
> Event ID: -1, Message: Failed to read VM '[Empty Name]' OVF, it may be
> corrupted
> 2015-03-17 23:30:57,012 ERROR
> [org.ovirt.engine.core.utils.ovf.OvfManager] (ajp--127.0.0.1-8702-8)
> Error parsing OVF due to 2
> 2015-03-17 23:30:57,033 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ajp--127.0.0.1-8702-8) Correlation ID: null, Call Stack: null, Custom
> Event ID: -1, Message: Failed to read VM '[Empty Name]' OVF, it may be
> corrupted
> 2015-03-17 23:30:57,071 ERROR
> [org.ovirt.engine.core.utils.ovf.OvfManager] (ajp--127.0.0.1-8702-8)
> Error parsing OVF due to 2
> 2015-03-17 23:30:57,091 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ajp--127.0.0.1-8702-8) Correlation ID: null, Call Stack: null, Custom
> Event ID: -1, Message: Failed to read VM '[Empty Name]' OVF, it may be
> corrupted
> 
> 
> I've brought up new export storage domains on both the new and old
> cluster (and a seperate storage array for that matter) all resulting the
> same messages.
> 
> Anyone any thoughts on these errors?
> 
> Thanks
> 
> Jon
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>