Description of problem:
Installing to a system with a LUKS encrypted logical volume for home, anaconda asks for the passphrase, then crashes with the below backtrace.
<report><binding name="localhash">06c818d03e8cf22c647924bf402b40049795b82b815a246e22d8fe0a6764dafa</binding><binding name="description">The following was filed automatically by anaconda:
anaconda 13.21.39 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/storage/devicelibs/crypto.py", line 120, in luks_close
raise CryptoError("luks_close failed for %s" % name)
File "/usr/lib/anaconda/storage/formats/luks.py", line 182, in teardown
File "/usr/lib/anaconda/storage/devices.py", line 1667, in teardown
File "/usr/lib/anaconda/storage/__init__.py", line 1293, in findExistingRootDevices
File "/usr/lib/anaconda/upgrade.py", line 94, in findExistingRoots
rootparts = findExistingRootDevices(anaconda, upgradeany=upgradeany)
File "/usr/lib/anaconda/upgrade.py", line 81, in findRootParts
File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
File "/usr/lib/anaconda/gui.py", line 1348, in setScreen
File "/usr/lib/anaconda/gui.py", line 1261, in nextClicked
CryptoError: luks_close failed for luks-94a3ee80-0366-41a9-9247-0802a4a50385
Full report to be attached
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Attempt to install to a system with an existing volume group containing an encrypted logical volume
Created attachment 414976 [details]
*** Bug 593671 has been marked as a duplicate of this bug. ***
Can you please attach the /tmp/anaconda-tb-* file as plain text, not as some crazy xml format?
does the attachment on the duplicate bug help:
Created attachment 415453 [details]
not some crazy xml format
The error code from python-cryptsetup is -15 (-ENOTBLK).
This seems to be a general failure to close/unmap LUKS devices whose backing device is also a device-mapper device.
To reproduce, format any LV as LUKS. Activate the LV, run cryptsetup luksOpen to map it, then try to unmap it using cryptsetup luksClose. You will get a failure much like this:
Device 253:0 doesn't exist or access denied.
I really wonder what I broke here...
This should be covered by usptream regression tests.
Anyway, I can reproduce it in RHEL6.
Fixed upstream, POST for now.
*** Bug 594789 has been marked as a duplicate of this bug. ***
Fixed in cryptsetup-luks-1.1.1-1.el6.
*** Bug 596340 has been marked as a duplicate of this bug. ***
I've used the steps to reproduce from the duplicate bug and tested with 0610.n.0 tree. No traceback. Moving to VERIFIED.
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.