Description of problem:

The kickstart file generated by the anaconda GUI does not correctly 
capture storage configurations.  (I have only tested LVM and BTRFS
configurations.)  This means that it cannot be used to automate
re-creation of the configured host, nor to provide a template for
extending the configuration to cover modes (such as LVM striping) not
exposed through the GUI.


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

As of the f18 release (20130115), the DVD 'Packages' directory shows
     anaconda-yum-plugins-1.0-8
I'm not sure how else to infer this information, but as the DVD-format
release remains unchanged, it's hard to see an ambiguity here. 


How reproducible:

Use the anaconda GUI to configure a host with LVM or BTRFS filesystems 
mapped over several physical drives; on reboot, examine the kickstart
file which was generated.


Steps to Reproduce:

 1. boot from the installation DVD and Continue to the hub.
 2. select the Storage/Installation Destination spoke.
 3. enable configuration of multiple (sda, sdb, sdc) Local Standard Disks.
 4. enable "Encrypt my data..." and Continue.
 5. enable "Let me customize the partitioning..." and Continue.
 6. delete any existing partitions/filesystems.
 7. add a '/' mountpoint; by-default, this sets Device Type to LVM.
     a  Modify the Volume Group to comprise only devices sda and sdb.
     b  re-set Desired Capacity (must be less than the combined capacity of
        sda and sdb.)
     c  Apply Changes.
     d  observe in-passing that there is no way to enable LVM striping...?
 8. add a '/boot' mountpoint; by-default, this sets Device Type to Standard
    Partition.
     a  configure the selected mountpoint (tools icon) to comprise only sdc.
     b  re-set Desired Capacity (must be less than sdc.)
     c  Apply Changes.
 9. add a 'swap' mount point; by-default, this sets Device Type to LVM.
     a  re-set the Device Type to Standard Partition.
     b  configure the selected mountpoint (tools icon) to comprise only sdc.
     c  re-set Desired Capacity (must less than the remainder of sdc.)
     d  Apply Changes.
     e  observe in-passing that the Desired Capacity gets stuck at your 
        initial setting...  that is, the value initially set cannot now be 
        changed (either via the '+' button or via text-entry), regardless of
        how much free space remains on sdc, selecting Apply Changes, etc.
10. Finish Partitioning.
11. set/confirm and save a disk passphrase.
12. select the Software/Software Selection spoke.
13. select Minimal Install (since our aim is to generate a Kickstart file,
    there's no point installing more than the minimum) and Done.
14. Begin Installation.
15. set/confirm a root password and Done.
17. Reboot and (before the BIOS locates the DVD) disconnect the DVD.
18. on reboot, decrypt the root device.
19. Login.
20. at the command prompt, 'view /root/anaconda-ks.cfg'.

  
Actual results:

The kickstart file shows a *fragment* of a kickstart command:

        --encrypted --type=lvm

Clearly this fragment is of no use for configuring filesystems and devices.

Further, if you modify step #7, above, to configure storage for BTRFS (which
does expose striping in the GUI), this will still generate the fragment:

        --encrypted --type=lvm

- which makes no sense whatsoever.


Expected results:

Anaconda documentation says, "The Fedora installation program also creates 
a sample kickstart file based on the options that you selected during
installation."  Clearly actual results are different.


Additional info:

Happy to provide such if it will make a difference.  Hard to feel confident
under the circumstances.