@martinhorton yes, if you were running from the sources, you'll need to rebuild from master.
If you're using Xen Orchestra Appliance, the fix is available in the 'latest' channel in version 5.48.1 https://github.com/vatesfr/xen-orchestra/blob/master/CHANGELOG.md
you can follow the bug fix here: https://github.com/vatesfr/xen-orchestra/pull/5129
@cbritton privately sent me a file that exhibit the error, many thanks. I am searching for the bug now.
@cbritton thank you, that would be great.
I really want everybody here know that I believe there is a bug in my code, it's just that I really need help reproducing on my machine to pinpoint it.
@martinhorton Haha, sorry, it's the VMDK parser.
OVA files are a tar files containing an XML file (.ovf) that describes the VM and .vmdk files that representing the disks. The VMDK file format uses a specific vocabulary, and each block of data is called a "grain" and there is a table that contains all the addresses of the "grains". The parser couldn't find it.
Can someone please send me a .ova file that triggers this error? I really need to trigger it on my machine to fix it.
thanks,
Nicolas.
@tofaz I don't see the parsing problem with the .ova file you sent me.
I have another test you could try: extract the .vmdk file from the ova, and try importing the disk itself, you should get the same error since it's the same .vmdk parser.
@tofaz Thank you, it's really hard to find the bug without a reliable reproduction. Even for simple bugs.
Hi Tofaz,
would you be able to transfer me the failing file please?
Thanks,
Nicolas.
you can follow the fix is in this pull request: https://github.com/vatesfr/xen-orchestra/pull/5085
<References>
<File ovf:compression="gzip" ovf:href="SexiLog-disk1.vmdk.gz" ovf:id="file1" ovf:size="1113498212"/>
<File ovf:compression="gzip" ovf:href="SexiLog-disk2.vmdk.gz" ovf:id="file2" ovf:size="317806"/>
</References>
I had never seen a gzipped vmdk file in a .ova before, I need to add this case. It might take a bit of time, because of our very peculiar import system.
Ok, .ova files are actually tar files.
would you mind listing the content of the tar file and dumping the content of the ovf file that is enclosed in the tar file, please?
This would spill your disk and network, and machine names here, are they sensitive too?
Nicolas.
Hi, would it be possible to send us the file privately ?
I have a local reproduction of the bug.
At first glance it looks like a stupid bug linked to the fact that there is more than one disk in the file.
@MrMike Hi, The netdata on the hosts is configured to stream towards the Xen Orchestra VM when activated from there.
Nicolas.
I think I got the bug, there is some cleanup and QA to be done before releasing a fix.
I'm still on it, I think I found an unrelated bug whose effect would be to upload a VM without any disk.
I am looking into it on my side. I might come back with questions.
hare you up to date on your XOA? we just released the utility