Description of problem: From Peter Larsen 2013-02-07 21:24:03 EST - The installer doesn't allow for encryption setup of individual LVs. While the checkbox is listed for each LV, the encryption covers the whole PV - not the individual LV. I have not found a work-around to this. If I launch the installer, manually setup partitions/filesystems/encryptions I cannot get the installer to read the current setup and assign mount-points. Major issues: 1. Reading existing setup. Even existing VG names are not listed. 2. Being able to simply assign mount points and a potential "reformat" on existing structure seems to be completely missing in the interface. 3. Encryption is only available on the PV level Minor issues: 1. The password complexity check seems off. Even non-words and random letters seems to only get 1 or 2 bars of "complexity". Setting encryption password does not allow you to continue if the password is deemed too simple - this should be corrected. 2. Max size of a new install's VG is calculated as a sum of all mount points. As a result, the VG does not allocate the whole disk and allow for later additions of space. If you start with a 256GB HDD, and do a default install, you end up with about 150GB of unallocated, unpartitioned space. The VG space should either be specified separately, or default to take up all disk-space. Having an advanced option where VG space could be managed would be best. (from https://bugzilla.redhat.com/show_bug.cgi?id=892269#c17)
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This is definitely present since 19.22. Please test it out and file new bugs if you find problems. Thanks!
*** This bug has been marked as a duplicate of bug 880876 ***