Description of problem: During installation when you do automatic partitioning you get error kickstart insufficient on disk formatting Version-Release number of selected component (if applicable): Ovirt Node 4.4.1, iso used ovirt-node-ng-installer-4.4.1-2020080418.el8.iso How reproducible: Installing in Virtualbox. So i've tried with 26GB and 46GB disk sizes to check if it works. Minimum disk space is 25G as per documentation. Steps to Reproduce: 1. Run install 2. Select disk 3. Actual results: kickstart insufficient on disk formatting Expected results: Automatically partition the selected disk Additional info:
(In reply to Djordje Vujnovic from comment #0) > How reproducible: > Installing in Virtualbox. So i've tried with 26GB and 46GB disk sizes to > check if it works. Minimum disk space is 25G as per documentation. Can you please point to the documentation page mentioning the 25 GB? Documentation needs to be updated.
I think it's this one https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/#hardware-requirements_SHE_cockpit_deploy
(In reply to Djordje Vujnovic from comment #2) > I think it's this one > https://www.ovirt.org/documentation/installing_ovirt_as_a_self- > hosted_engine_using_the_cockpit_web_interface/#hardware- > requirements_SHE_cockpit_deploy This one describe the oVirt Engine disk requirements, not the oVirt Node ones. https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/#Storage_Requirements_SHE_cockpit_deploy is for the host and it says 55GB minimum. I see the document also don't mention minimal deployment option for oVirt Node. commit e8c5bb6298dab0f709440060d8203163bffa943a Author: Yuval Turgeman <yturgema> Date: Tue Jan 14 11:54:12 2020 +0200 Support minimal storage requirements for node Booting the ISO with "node_storage=minimal" will require a smaller disk for installing node. It will *not* use NIST partitioning, and will require only 15G for data and more for swap (unless using the noswap keyword) Change-Id: I82b69db4289600e4d75c1f65da53273d4fd9a003 Signed-off-by: Yuval Turgeman <yturgema> Steve, can you help updating the install guide? Thanks,
I've just tried installation with 58GB disk, but same issue appears
when using "node_storage=minimal" it accepts my disk 58GB
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
I was only able to install a virtual machine with RHVH after setting the disk size to about 73GiB. Is 73GiB the minimum disk size?
Chen, What's your experience with the minimum disk size you need to allocate in a vm when installing RHVH? Is the minimum disk size in a vm different from the minimum disk size on bare metal?
(In reply to Steve Goodman from comment #8) > Chen, > > What's your experience with the minimum disk size you need to allocate in a > vm when installing RHVH? Install RHVH on 45G disk can successful if we don't consider Anaconda reserves 20% of the thin pool size. But 55G is recommended. The minimum storage requirements for host installation are listed below. However, use the default allocations, which use more storage space. / (root) - 6 GB /home - 1 GB /tmp - 1 GB /boot - 1 GB /var - 15 GB /var/crash - 10 GB /var/log - 8 GB /var/log/audit - 2 GB swap - 1 GB (for the recommended swap size, see https://access.redhat.com/solutions/15244) Anaconda reserves 20% of the thin pool size within the volume group for future metadata expansion. This is to prevent an out-of-the-box configuration from running out of space under normal usage conditions. Overprovisioning of thin pools during installation is also not supported. Minimum Total - 55 GB If you are also installing the Engine Appliance for self-hosted engine installation, /var/tmp must be at least 5 GB. > Is the minimum disk size in a vm different from the minimum disk size on > bare metal? I think no different.
Created attachment 1736100 [details] minimum 55G
(In reply to cshao from comment #9) > Install RHVH on 45G disk can successful if we don't consider Anaconda > reserves 20% of the thin pool size. But 55G is recommended. So why was I unable to install with anything less than 73GiB?
(In reply to Steve Goodman from comment #11) > (In reply to cshao from comment #9) > > > Install RHVH on 45G disk can successful if we don't consider Anaconda > > reserves 20% of the thin pool size. But 55G is recommended. > > So why was I unable to install with anything less than 73GiB? Could you please provide more info? e.g. error screenshot or log info.
(In reply to Steve Goodman from comment #7) > I was only able to install a virtual machine with RHVH after setting the > disk size to about 73GiB. > > Is 73GiB the minimum disk size? As far as I know it's 55 GB: https://ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/#Storage_Requirements_SHE_cockpit_deploy Needs to be investigated if it require more than that. Moving this bug out of documentation for investigation. Lev can you look into this?
I was able to create RHVH instance w/ just 50 GB drive, with it failing to install with 40 GB drive. On u/s (ovirt-node) it was working for me with smaller drives (i.e. the same 40GB). I think that we should update the documentation to reflect this, or even ask to higher minimum drive size, as probably that number will go up with the newer releases.
(In reply to Lev Veyde from comment #14) > I was able to create RHVH instance w/ just 50 GB drive, with it failing to > install with 40 GB drive. > On u/s (ovirt-node) it was working for me with smaller drives (i.e. the same > 40GB). > > I think that we should update the documentation to reflect this, or even ask > to higher minimum drive size, as probably that number will go up with the > newer releases. We recently updated all the installation documents to say minimum 55 GiB for the Host > Storage requirements: https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/#Storage_Requirements_SHE_cockpit_deploy https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/installing_red_hat_virtualization_as_a_self-hosted_engine_using_the_cockpit_web_interface/index#Storage_Requirements_SHE_cockpit_deploy In the Engine Hardware requirements, it says the minimum is 25 GB of locally accessible, writable disk space, but recommends having 50 GB: https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/#hardware-requirements_SHE_cockpit_deploy https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/installing_red_hat_virtualization_as_a_self-hosted_engine_using_the_cockpit_web_interface/index#hardware-requirements_SHE_cockpit_deploy
Do you still experience the issue?
you can close the case as with greater than 55GB is ok
I wonder if it's a bug this time - on Centos 9 with up-to-date libvirt/qemu - as I use image size of 150GB and I get: "Kickstart insufficient" for "Install Destination" ovirt-node-ng-installer-latest-el9.iso or.. have storage requirements gone that high through the roof? thanks, L.
That was a pretty weird one - after each 'virt-install' failure I'd 'rm' created qcow2 and start again with size increased by 10G to that point of 150G where I tried 'qemu-img' but, to that same effect: "Kickstat insufficient", then.. I switched back to virt-install's auto-creation of the image, with only 70G, then!!... went for 'custom' disk partitioning and 'auto' populate partition and hey, installer was happy, so.. I destroyed VM mid-air, at the stage of 'partitioning', started again 'virt-install' and now 'Automatic' partitioning is happy as well... weird as hell. This all was one single metal host with libvirt/kvm.