Red Hat Bugzilla – Bug 436344
Generated ks.cfg partitioning section doesn't match real life when reusing partitions
Last modified: 2008-03-06 16:30:03 EST
Description of problem: doing an install on a system that already has disks partitioned and choosing to use the existing disks leads to partitioning configuration in ks.cfg which doesn't reproduce the install. Version-Release number of selected component (if applicable): pykickstart-0.43-1.el5 anaconda-11.1.2.105-1 How reproducible: always Steps to Reproduce: (using xen for example) 1. Install the system choosing default partitioning 2. Make a note on partitions used 3. After install reboot and start a second install 4. Chose customized disk layout and assign mountpoints/fs type for the existing partitions. 5. Finish the install and grab the resulting anaconda-ks.cfg Actual results: generated ks.cfg will not reproduce the install Expected results: generated ks.cfg will reproduce the install Additional info: kistart configuration from Xen guest with one disk 4GB initial install (autopart) --------------------------------------------------------------------- clearpart --all --drives=xvda part /boot --fstype ext3 --size=100 --ondisk=xvda part pv.2 --size=0 --grow --ondisk=xvda volgroup VolGroup00 --pesize=32768 pv.2 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=528 --grow --maxsize=1056 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow --------------------------------------------------------------------- second install --------------------------------------------------------------------- clearpart --linux part /boot --fstype ext3 --onpart xvda1 part pv.2 --noformat --onpart xvda2 volgroup VolGroup00 --noformat --useexisting --pesize=32768 pv.2 logvol swap --useexisting --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=1056 logvol / --useexisting --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=2816 --------------------------------------------------------------------- note the --onpart options which are just fine. However the clearpart line removes all partitions so in the next step they can't be found. I get an error dialog saying that partition xvda1 can't be found. If you remove the clearpart line it's ok.
This probably isn't something we're ever going to address -- that's why this part of the generated ks.cfg is commented out.