If it said where it was going to extract to it would be an easy work around, for any one who hits it. 
There is not enough space in /var/lib/somdir/somdir/ to extract the image <x> GiB is required.

If I hit that then I can just put some more disk on that directory. 

On 25 June 2017 at 14:57, Yuval Turgeman <yuvalt@redhat.com> wrote:

On Sun, Jun 25, 2017 at 1:31 PM, Yaniv Kaul <ykaul@redhat.com> wrote:


On Sun, Jun 25, 2017 at 12:38 PM, Ben De Luca <bdeluca@gmail.com> wrote:
Hi,
     I am in the middle of a disaster recovery situation trying to install ovirt 4.1 after a failure of some of our NFS systems. So I was redeploying 4.0 but there is a bug with the image uploader, that means I cant upload images. Our actually virtual machine hosts have very small HD's and the current 4.1 release installer thinks that the OVA extracted is 50GiB, I have exactly 50GB free! yay. So I did manage to hack the installer, to ignore my local disk space as the OVA is really only a few gigs in side. 

     But its been pretty painful. Any chance of some one fixing the estimate there, I have read through the code, there was an attempt to find out the real size but they gave up and just guessed. 


We changed it to 50G in[1].
Did we over-estimate?


Could very well be, but this patch was posted in order to align the upstream disk size.  Adding Fabian, perhaps he remembers the initial thoughts.

Thanks,
Yuval.

 

Y.

 
-bd
*tired sysadmin*


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