Hide Forgot
Description of problem: When deploying RHV in self-hosted engine config, the documented requirements for storage are at least 60GiB for /var in order for the the RHV-M appliance. Regardless of how much disk space is allotted to a host, Anaconda gives that space to "/" and effectively starves "/var". Either RHVH needs a different layout to account for this automatically OR there needs to be a checkbox in RHVH Anaconda for hosted engine deployments Version-Release number of selected component (if applicable): ISO image for RHVH - RHVH-4.0-20161018.0-RHVH-x86_64-dvd1.iso How reproducible: consistently every time Steps to Reproduce: 1. deploy RHVH from ISO (DVD, USB, etc) 2. accept default layout 3. allow RHVH to finish 4. launch hosted engine configuration 5. hosted engine deployment fails because RHV-M appliance doesn't have the space it needs to expand Actual results: hosted engine fails because the disk layout is incorrect/incompatible with documented requirements Expected results: RHVH deployment is deployed per documented requirements such that customers are not frustrated Additional info:
/var has a default size of 15GB. With the fix of bug 347340, the space requirements in the HE case should be much lower and the 15GB should be sufficient. Ying, could QE verify that the default partitioning of the most recent RHVH is correct to be used for HE?
I tested HostedEngine deploy via cockpit successfully.And /var has a default size of 15GB. Version: redhat-virtualization-host-4.0-20161130.0.x86_64. Thanks, Yihui
(In reply to Yihui Zhao from comment #3) > I tested HostedEngine deploy via cockpit successfully.And /var has a default > size of 15GB. > > Version: redhat-virtualization-host-4.0-20161130.0.x86_64. > > Thanks, > Yihui Thanks for yihui's help. Update some HE related packages info. redhat-virtualization-host-4.0-20161130.0.x86_64. imgbased-0.8.10-0.1.el7ev.noarch ovirt-hosted-engine-setup-2.0.4-2.el7ev.noarch ovirt-hosted-engine-ha-2.0.5-1.el7ev.noarch rhevm-appliance-20161130.0-1.el7ev.ova
Closed this bug according to comment 3.