[CentOS] kickstart compat C7 -> C8

[Leon Fauster]

> Am 08.05.2019 um 19:20 schrieb mark <m.roth at 5-cent.us>:
> 
> Leon Fauster via CentOS wrote:
>> Hi all,
>> 
>> 
>> I still use the following kickstart partition scheme for C7 installations
>> (via virt-install):
>> Briefly, fixed size for /root and /boot, and the rest is filled up for
>> /srv.
>> 
>> The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work
>> with Fedora29 (EL8). I get a "device is too small for new format" error.
>> Any hints?
>> 
>> part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part
>> /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT
>> part pv.0104 --fstype="lvmpv" --ondisk=sda --grow volgroup ee --pesize=4096
>> pv.0104 logvol / --fstype="ext4" --size=3072 --encrypted --label="ROOT"
>> --name=00 --vgname=ee
>> logvol /srv --fstype="ext4" --percent=100 --grow --encrypted --label="SRV"
>> --name=01 --vgname=ee
>> 
> If I'm reading that correctly - haven't worked on a kickstart in years -
> I'd start by increasing root to 1024 (1M) for /boot.


That sounds reasonable but it doesn't help (tested up to 3GB for boot). The point is, that 
with fixed sizes everything works (even with 3GB root, 512MB boot, 768 RAM). The anaconda 
text-installation process passes without any problems. Only when "--grow" option comes in 
the problem appears. And this only for Fedora29, a C7 installation works fine (dynamically 
expands to the boundaries of the disk).

Looking into the docs doesn't show any modifications:  
https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#chapter-3-kickstart-commands-in-red-hat-enterprise-linux

It seems that with every new major release the headaches starts again :-(.

<retest>

While writing I did a new installation; the grow option for the "part" command seems to work. 
The VG expands to the disk boundaries. So, the problem gets more located around the "logvol" 
command ...


--
LF