After installation anaconda-ks.cfg stores wrong record of disk layout when percentage used
Issue
-
When using in kickstart:
part /boot --fstype=ext4 --size=256 --asprimary --ondisk=$ondisk part pv.2 --size=1 --grow --asprimary --ondisk=sda volgroup vg_root pv.2 lv_snapshot_space to allow cleanup in post logvol /snapshot_space --fstype=ext4 --name=lv_snapshot_space --vgname=vg_root --percent=10 --grow --size=1 -
anaconda-ks.cfg was written with:
# The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work #clearpart --all --drives=vda --initlabel #part /boot --fstype=ext4 --asprimary --size=256 #part pv.253002 --grow --asprimary --size=1 #volgroup vg_root --pesize=32768 pv.253002 #logvol / --fstype=ext4 --name=lv_root --vgname=vg_root --grow --size=1 #logvol /snapshot_space --fstype=ext4 --name=lv_snapshot_space --vgname=vg_root --grow --size=1 #logvol swap --name=lv_swap --vgname=vg_root --size=2048 - Note the missing percent for /snapshot_space
Environment
- Red Hat Enterprise Linux
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.