CentOS - May 2019 - kickstart compat C7 -> C8

> 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

Once upon a time, Leon Fauster via CentOS <centos at centos.org>
said:
> And this only for Fedora29, a C7 installation works fine (dynamically 
> expands to the boundaries of the disk).
You are asking about Fedora - you'd probably get better results on the
Fedora mailing lists, forums, etc.

-- 
Chris Adams <linux at cmadams.net>

> Am 08.05.2019 um 21:12 schrieb Chris Adams <linux at cmadams.net>:
> 
> Once upon a time, Leon Fauster via CentOS <centos at centos.org>
said:
>> And this only for Fedora29, a C7 installation works fine (dynamically 
>> expands to the boundaries of the disk).
> 
> You are asking about Fedora - you'd probably get better results on the
> Fedora mailing lists, forums, etc.
Well, F29 is very close to EL8 but you are right. Anyway, for the sake of
precision.
I made the same installation with RHEL8 (anaconda 29.19 vs 29.24 on F29). The
results
are same!

Following "logvol" stanza "--percent=100 --grow" works for
EL7 but not for EL8.

While doing this again I found a solution; "--size=SIZE --grow" as
options with an
arbitrary SIZE will grow the LV to the size of the free VG size.

--
LF