Bug 1040720

Summary: Inconsistent use of encrypted VG vs. encrypted LVs in custom partitioning with autopart and custom partitioning with manual mount point creation
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 22CC: anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 19:28:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Adam Williamson 2013-12-12 01:18:36 UTC 
Noticed while investigating https://bugzilla.redhat.com/show_bug.cgi?id=1040716 .

If I do this:

1. On Installation Options, check 'encrypt my data' and leave the drop-down on LVM, and pick custom partitioning
2. After entering password, hit the autopart button in custom partitioning (the blue 'create them for me' link)

then I get a 500MB /boot, a VG called 'fedora' which is encrypted, and LVs for / and swap which are not encrypted.

If I do this:

1. On Installation Options, check 'encrypt my data' and leave the drop-down on LVM, and pick custom partitioning
2. After entering password, in custom partitioning, manually create a 500MB boot, then a / mount and a swap mount

then I wind up with a VG called 'fedora' which is *not* encrypted, and LVs for / and swap which *are* encrypted.

It seems like both of these ought to work the same way - whether I create the mount points manually or let autopart do it, anaconda should prefer either encrypting the VG or encrypting the LVs, not do it one way for autopart and the other for manual creation.
Comment 1 Jaroslav Reznik 2015-03-03 15:19:29 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 2 Fedora End Of Life 2016-07-19 19:28:18 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.