[ovirt-devel] Engine OVA: Incoherence detected in OVF file: image size 10485760000 does not match declared size 10737418240

Fabian Deutsch fdeutsch at redhat.com
Wed Apr 22 09:44:44 UTC 2015


----- Original Message -----
> Hi,
> just hit:
> 
> [ ERROR ] Failed to execute stage 'Misc configuration': Incoherence detected
> in OVF file: image size 10485760000 does not match declared size 10737418240
> 
> While trying to use upstream OVA for deploying hosted engine.
> The OVA is
> http://jenkins.ovirt.org/job/ovirt-appliance-engine_master_merged/lastSuccessfulBuild/artifact/exported-artifacts/oVirt-Engine-Appliance-CentOS-x86_64-7-20150421.464.ova
> 
> 2015-04-22 10:38:02 DEBUG
> otopi.plugins.ovirt_hosted_engine_setup.vm.boot_disk plugin.execute:934
> execute-output: ('/bin/sudo', '-u', 'vdsm', '-g',
> 'kvm', '/bin/qemu-img', 'info', '--output', 'json', '/tmp/tmpGr
> ggJe') stdout:
> {
>     "virtual-size": 10485760000,
>     "filename": "/tmp/tmpGrggJe",
>     "cluster-size": 65536,
>     "format": "qcow2",
>     "actual-size": 2955214848,
>     "format-specific": {
>         "type": "qcow2",
>         "data": {
>             "compat": "1.1",
>             "lazy-refcounts": false
>         }
>     },
>     "dirty-flag": false
> }
> 
> while the OVF xml file declares:
> ovf:size="10" -> 10*pow(2,30) = 10737418240
> 
> 
> Please fix the disk image virtual size to be 10737418240, thanks.

Hey,

nice catch. That is interesting, because we leverage imgfac to do the ova wrapping.
Looking at the code we use to trigger the ova creation, I do not see any size related code.

Which means that imgfac is identifying the size of the image by itself and writing those values.

And looking at the imgfac history I see this commit:
https://github.com/redhat-imaging/imagefactory/commit/ee8bdd4a8df8669cacf4ab6e1e9c00c7a08e0862

which landed in master recently (we use imgfac master for building).

I've commented on the fix, and adding Ian as the author of that patch.

- fabian



More information about the Devel mailing list