From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2)
Gecko/20010726 Netscape6/6.1

Description of problem:
The clearpart kickstart directive only does things if --all or --linux is
specified.  Essentially, the --drives flag has no effect.  This makes it
impossible to leave a drive untouched with a kickstart install, whilst still
repartitioning another drive.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.  Make a kickstart configuration that uses clearpart --drives <foo>.
2.  An install vs. that config will not clear any partitions (and will fail if
one attempts to specify new partitions for the drive that one wishes to
repartition).
3.  Make a kickstart configuration that uses clearpart --all --drives <foo>.
4.  An install vs. that config will clear all partitions on all drives.
	

Actual Results:  Specified in the steps above...

Expected Results:  In the first case, it should just clear the partition tables
on the specified drives.  The second case is the only way to complete an
installation, but it can cause data loss (though it can be recovered by applying
an identical partition table to the affected drives).

Additional info:

The lines in the anaconda source where --all and --linux are the only options
effected can be found in autopart.py, line 765:

    if type == CLEARPART_TYPE_LINUX:
        linuxOnly = 1
    elif type == CLEARPART_TYPE_ALL:
        linuxOnly = 0
    elif type == CLEARPART_TYPE_NONE:
        return
    else:
        raise ValueError, "Invalid clear part type in doClearPartAction"

See the second elif clause, where the function returns if one of --all or
--linux was not specified.  The code probably needs adjustment elsewhere.  I'd
submit a patch, but I am not familiar with Python.