Description
Describe the bug
osbuild does not support specifying the maximum size of disk allocation according to the documentation. It only refers to setting a minimum size. This will cause problems when images are used in combination with other automation tools that have created a maximum disk size, where the automated growth may not align nicely.
e.g. we build a VM using Terraform with a first disk always 20GB in size, and want the automatic partitioning to grow to use that full size (creating the default /boot, /boot/efi, /, and swap partitions).
This will end up with a more consistent partition sizing that we would expect comparing it to using a Kickstart installation.
Environment
- CentOS 7, RHEL 8, RHEL 9
- Red Hat Image Builder https://console.redhat.com/beta/insights/image-builder
To Reproduce
Steps to reproduce the behavior:
- create an ISO image trying to calculate what will work create enough space while fitting under 20GB in size.
- Give up in frustration.
Expected behavior
Disk auto growth should be based on the size of the disk you have available. You should be able to tell osbuild "you have maximum 20GB" and let it work out the rest based on a default disk layout.
The size of / may vary depending on how much is allocated to swap space, or whether a /boot/efi partition is created.
Additional context
We currently use kickstart scripts to define fancy disk layouts, we don't need specifics of minimum sizes for partitions, we just need the automatic growth to fit inside the maximum disk size (we chose 20GB) disk VMware has.
Refer also to #3416