Bug 1283102

Summary: Anaconda doesn't set disk encryption
Product: [Fedora] Fedora Reporter: Lukas Brabec <lbrabec>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 20:33:57 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:
Attachments:
Description Flags
anaconda.log
none
anaconda-ks.cfg none

Description Lukas Brabec 2015-11-18 09:37:20 UTC 
Description of problem:
Anaconda doesn't encrypt disk when, at first, custom partition is set without encryption, which is then added separately on the second entrance to "installation destination" spoke.


Version-Release number of selected component (if applicable):
Fedora 24 Rawhide 20151117
anaconda 24.6-1


Steps to Reproduce:
1. boot to installer
2. manually partition disk without encryption 
3. from "installation summary" return to "installation destination" and check "encrypt my data"
4. provide password a go through manual partitioning by clicking on done and accept changes
5. install the system

Actual results:
disk is not encrypted

Expected results:
user is prompted for password right after grub, disk is encrypted
Comment 1 Lukas Brabec 2015-11-18 09:37:51 UTC 
Created attachment 1095914 [details]
anaconda.log
Comment 2 Lukas Brabec 2015-11-18 09:38:30 UTC 
Created attachment 1095916 [details]
anaconda-ks.cfg
Comment 3 Lukas Brabec 2015-11-18 09:47:54 UTC 
I was able to reproduce this bug also on Fedora 23 with anaconda 23.19.10-1
Comment 4 David Lehman 2015-11-19 20:33:57 UTC 
We do not attempt to perform any automatic conversion of manually-created layouts, which is what you seem to expect.

If you use manual storage configuration and then change your mind about encryption you have to specify encryption for each device you want to encrypt in the custom storage spoke. There is no way we could reliably guess which devices you want to encrypt.