Red Hat Bugzilla – Bug 864120
LUKS encryption option has no effect
Last modified: 2012-10-18 05:07:00 EDT
Description of problem:
I have used a custom partitioning screen, let anaconda create the layout automatically, selected root partition and checked "Encrypt" checkbox. Then hit Finish button and started installation.
I was not asked for password and the resulting system has only standard partitioning, none of them is encrypted.
Version-Release number of selected component (if applicable):
F18 Beta TC2
Steps to Reproduce:
1. follow description
Created attachment 623528 [details]
Created attachment 623529 [details]
Created attachment 623530 [details]
Created attachment 623531 [details]
Created attachment 623532 [details]
Proposing as Beta blocker:
" The installer's custom partitioning mode must be capable of the following:
Creating, destroying and assigning mount points to partitions of any specified size using most commonly-used filesystem types
Creating encrypted partitions
Rejecting obviously invalid operations without crashing
Discussed at 2012-10-11 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-11/f18beta-blocker-review-3.1.2012-10-11-16.04.log.txt . Accepted as a blocker per criterion cited in comment #6. (We note this may be fixed as of TC3 or 18.15, kparal will re-test).
This has been changed in F18 Beta TC4, the UI looks different now. However, it still doesn't work. It allows me to set password, but it claims I have too little free space on disk, even though I have selected all existing partitions to be removed. It seems that disk encryption currently doesn't work well with reclaiming space.
(In reply to comment #8)
> This has been changed in F18 Beta TC4, the UI looks different now. However,
> it still doesn't work. It allows me to set password, but it claims I have
> too little free space on disk, even though I have selected all existing
> partitions to be removed. It seems that disk encryption currently doesn't
> work well with reclaiming space.
So you have verified that the exact path you describe works without encryption but fails with encryption? If so, please attach anaconda.log and storage.log from each. Thanks.
Encryption works as of anaconda-18.14-1 in my testing. Kamil, this is not going to be a catch-all bug for every encryption-related failure in F18. If you are experiencing a problem, please open a new bug with specific details and logs.
It seems pretty clear that the original bug here has been addressed, if it's as of 18.14, then we can close it, as 18.14 has gone stable. Kamil, can you open a new bug for the problem you're now experiencing, and nominate it as a blocker if appropriate? Thanks.
I verified that encrypted installation works if I have an uninitialized disk (anaconda 18.16). I'll report a new bug wrt comment 8.