Description of problem: Version-Release number of selected component (if applicable): rhvm-appliance-20170619.0-1.x86_64.rhevm.ova How reproducible: Every time. Steps to Reproduce: 1. use `hosted-engine --deploy` on rhel host 2. use rhvm-appliance-4.1.20170619.0-1.el7.noarch.rpm to deploy manager VM 3. run out of disk space after about a week of logs and postgres data accumulation Actual results: anaconda.ks file has following entries for partitioning [root@cloud ~]# cat anaconda-ks.cfg ... bootloader --append="console=tty0" --location=mbr --timeout=1 # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel # Disk partitioning information part / --fstype="xfs" --ondisk=vda --size=6144 part swap --size=8192 ... [root@cloud ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sr0 11:0 1 1024M 0 rom vda 253:0 0 75G 0 disk ├─vda1 253:1 0 6G 0 part / └─vda2 253:2 0 8G 0 part [SWAP] Expected results: 'part /' line should include --grow by default, root partition should use full amount of available space. Additional info:
growth is handled by cloud-utils-growpart Since swap was added, cloud-utils-growpart will not grow the first partition, since swap abuts it. These partitions are being reversed, so swap is first.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Should this be ON_QA? Can you add it to the errata?
No -- it doesn't have 4.1.z+ yet, which is necessary to add it to the errata. I also can't set the target version for appliance. I'll find someone who can.
Verified with: rhvm-appliance-20170709.3-1.x86_64.rhevm.ova # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sr0 11:0 1 1024M 0 rom sr1 11:1 1 374K 0 rom vda 253:0 0 58G 0 disk ├─vda1 253:1 0 8G 0 part [SWAP] └─vda2 253:2 0 50G 0 part /
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:1525
BZ<2>Jira Resync
sync2jira