Description of problem: i was able to start installing with an empty <null> luks password. (! wOw !) Version-Release number of selected component: anaconda-18.19 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.1-1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.19 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/luks.py", line 189, in create : raise LUKSError("luks device has no key/passphrase") : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 439, in execute : options=self.device.formatArgs) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 323, in processActions : action.execute() : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 357, in doIt : self.devicetree.processActions() : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 195, in turnOnFilesystems : storage.doIt() : File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 107, in doInstall : turnOnFilesystems(storage) : File "/usr/lib64/python2.7/threading.py", line 504, in run : self.__target(*self.__args, **self.__kwargs) : File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run : threading.Thread.run(self, *args, **kwargs) :LUKSError: luks device has no key/passphrase
Created attachment 632301 [details] File: anaconda-tb
Created attachment 632302 [details] File: product
Created attachment 632303 [details] File: type
Created attachment 632304 [details] File: ifcfg.log
Created attachment 632305 [details] File: storage.log
Created attachment 632306 [details] File: version
Created attachment 632307 [details] File: environ
Created attachment 632308 [details] File: anaconda.log
Created attachment 632309 [details] File: syslog
Created attachment 632310 [details] File: hashmarkername
Created attachment 632311 [details] File: packaging.log
Created attachment 632312 [details] File: cmdline_file
Created attachment 632313 [details] File: release
Created attachment 632314 [details] File: program.log
When prompted for a LUKS passphrase, click continue. Package: anaconda-18.19 OS Release: Fedora release 18-Beta-TC6
(In reply to comment #15) > When prompted for a LUKS passphrase, click continue. > > Package: anaconda-18.19 > OS Release: Fedora release 18-Beta-TC6 Correction: Click "Save Passphrase". What will happen during a kickstart install, if the passphrase is empty? Cf: Bug 868519, Comment 22.
Steps to Reproduce: 1. prepare disk without free space 2. start installation 3. on disks screen check 'Encrypt my data', click on Continue 4. Reclaim space, delete all partitions 5. begin installation Expected: Ask for password for encryption Package: anaconda-18.24 OS Release: Fedora release 18-Beta-TC7
I have patches to fix this. I'll be sending them out for review later today.
Reproduced as described by Michal: if you check the 'Encrypt my data' box and then go through 'guided partitioning' to delete partitions and free up space, you are not prompted for an encryption passphrase at any point, and install crashes at the start of actual installation, when it's creating partitions.
Reproduced as described by Michal: if you check the 'Encrypt my data' box and then go through 'guided partitioning' to delete partitions and free up space, you are not prompted for an encryption passphrase at any point, and install crashes at the start of actual installation, when it's creating partitions. Discussed at 2012-11-05 QA meeting acting as a blocker review meeting. Accepted as a blocker. At present our criteria don't cover this very well as they were written when you could only do encryption through custom partitioning, so it says: "The installer's custom partitioning mode must be capable of the following: ... Creating encrypted partitions" But the intention is just that install to encrypted partitions should work in general. So now newUI can encrypt without going through custom part, the criteria need updating, and this bug should be covered.
anaconda-18.25-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.25-1.fc18
Package anaconda-18.25-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.25-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17691/anaconda-18.25-1.fc18 then log in and leave karma (feedback).
anaconda-18.26-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.26-1.fc18
Confirmed fixed in 18.26, the dialog pops up right after you reclaim space.
anaconda-18.27-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.27-1.fc18
18.26 went stable. Closing. (Bodhi closing of bugs when updates go stable is currently broken).