Bug 1283102 - Anaconda doesn't set disk encryption
Anaconda doesn't set disk encryption
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-18 04:37 EST by Lukas Brabec
Modified: 2015-11-19 15:33 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-19 15:33:57 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
anaconda.log (40.19 KB, text/plain)
2015-11-18 04:37 EST, Lukas Brabec
no flags Details
anaconda-ks.cfg (1.40 KB, text/plain)
2015-11-18 04:38 EST, Lukas Brabec
no flags Details

  None (edit)
Description Lukas Brabec 2015-11-18 04:37:20 EST
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 04:37 EST
Created attachment 1095914 [details]
anaconda.log
Comment 2 Lukas Brabec 2015-11-18 04:38 EST
Created attachment 1095916 [details]
anaconda-ks.cfg
Comment 3 Lukas Brabec 2015-11-18 04:47:54 EST
I was able to reproduce this bug also on Fedora 23 with anaconda 23.19.10-1
Comment 4 David Lehman 2015-11-19 15:33:57 EST
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.

Note You need to log in before you can comment on or make changes to this bug.