Created attachment 665771 [details] crash report Description of problem: If you mark a preexisting (unencrypted) lv for reformat including encryption, you get asked for a passphrase but the passphrase doesn't get set in the device object, causing a traceback at activation time. Version-Release number of selected component (if applicable): anaconda-18.37.2 How reproducible: Always Steps to Reproduce: 1. start with an existing unencrypted lv 2. mark it for reformat and encryption in the custom spoke 3. continue with installation Actual results: crash as detailed below Expected results: no crash Additional info: anaconda 18.37.2 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 336, in doIt self.devicetree.processActions() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 174, in turnOnFilesystems storage.doIt() File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 114, 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
I have a working patch here.
at least +1 nth, probably +1 blocker (per the 'do any partitioning you like' criterion)
definitely +1 nth, weak +1 blocker...
So doing a slightly fuzzy count as we're firing off an anaconda build here and it'd be a shame to miss this - that's +1 from dlehman (anaconda), +1 from nirik (releng) and +1 from me (qa), so accepted NTH at least.
anaconda-18.37.4-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.37.4-1.fc18
Package anaconda-18.37.4-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.37.4-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20677/anaconda-18.37.4-1.fc18 then log in and leave karma (feedback).
anaconda-18.37.4-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Petr verified, closing again.