+++ This bug was initially created as a clone of Bug #610740 +++

Created attachment 429015 [details]
screenshot of partitioning gone wrong

Description of problem:
When opening a file in s-c-kickstart the partitioning screen shows the current settings. When opening the same or another file this screen will append the new partitioning scheme to already existing one. After several reopenings user ends up with several definitions for the root filesystem. If saved this results in invalid ks.cfg

Version-Release number of selected component (if applicable):
system-config-kickstart-2.8.6.1-1.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. Install system-config-kickstart
2. Uncomment the partitioning lines in your /root/anaconda-ks.cfg
3. Open the file with s-c-kickstart. Observe the partitioning page.
4. Open the same file again. See screenshot.
5. Try opening it for the 3rd time.
  
Actual results:
The existing partitions are not cleared when opening new file and new ones are appended to the list. This produces invalid ks.cfg if saved. Check with "Preview".

Expected results:
Existing partitions are removed and new ones are added when opening new file (or the same one).

Additional info:

Upon filing this bug I've noticed that s-c-kickstart will not properly display the LVM VG and LVs. Only /boot and the PV are displayed. My ks.cfg has:

bootloader --location=mbr --driveorder=sda --append="console=ttyS0,115200 crashkernel=auto"
clearpart --all --initlabel

part /boot --fstype=ext4 --size=500
part pv.Z6tsRr-yItL-6yIJ-fKFx-ZXd0-virq-eU81WE --grow --size=1

volgroup vg_tyangt2409 --pesize=4096 pv.Z6tsRr-yItL-6yIJ-fKFx-ZXd0-virq-eU81WE
logvol /home --fstype=ext4 --name=lv_home --vgname=vg_tyangt2409 --grow --size=100
logvol / --fstype=ext4 --name=lv_root --vgname=vg_tyangt2409 --grow --size=1024 --maxsize=51200
logvol swap --name=lv_swap --vgname=vg_tyangt2409 --grow --size=1024 --maxsize=10128


Do you want me to open a separate bug for that?

--- Additional comment from pm-rhel on 2010-07-02 14:03:17 EEST ---

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

--- Additional comment from clumens on 2010-08-25 20:48:19 EEST ---

diff --git a/src/partition.py b/src/partition.py
index 575cb8e..ca50bd9 100644
--- a/src/partition.py
+++ b/src/partition.py
@@ -293,10 +293,11 @@ class partition:
                 self.initlabel_yes_radiobutton.set_active(True)
             else:
                 self.initlabel_no_radiobutton.set_active(True)
-
         else:
             self.remove_parts_none_radiobutton.set_active(True)
 
+        self.part_store.clear()
+
         for part in self.ks.partition.partitions:
              self.partWindow.populateList(part)

--- Additional comment from syeghiay on 2010-09-13 19:10:05 EEST ---

Cleared acks since set before rhel-6.1.0? flag.

--- Additional comment from errata-xmlrpc on 2011-01-06 22:55:10 EET ---

Bug report changed to ON_QA status by Errata System.
A QE request has been submitted for advisory RHBA-2011:10445-01
http://errata.devel.redhat.com/errata/show/10445

--- Additional comment from atodorov on 2011-01-13 15:28:15 EET ---

With system-config-kickstart-2.8.6.3-1.el6.noarch when re-opening the same ks.cfg file again and again the previous partitions are cleared and new ones added. This doesn't cause duplication. Moving to VERIFIED.