Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionAlex Williamson
2010-05-18 22:13:41 UTC
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
crypto.luks_close(self.mapName)
File "/usr/lib/anaconda/storage/devices.py", line 1667, in teardown
self.slave.originalFormat.teardown()
File "/usr/lib/anaconda/storage/__init__.py", line 1293, in findExistingRootDevices
device.teardown(recursive=True)
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
flags.cmdline.has_key("upgradeany"))
File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
self.moveStep()
File "/usr/lib/anaconda/gui.py", line 1348, in setScreen
self.anaconda.dispatch.gotoNext()
File "/usr/lib/anaconda/gui.py", line 1261, in nextClicked
self.setScreen ()
CryptoError: luks_close failed for luks-94a3ee80-0366-41a9-9247-0802a4a50385
Full report to be attached
Version-Release number of selected component (if applicable):
RHEL6.0-20100512.0-Server-x86_64-DVD1.iso
How reproducible:
100%
Steps to Reproduce:
1. Attempt to install to a system with an existing volume group containing an encrypted logical volume
2.
3.
Actual results:
Fails
Expected results:
Success
Additional info:
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.
*** Bug 596340 has been marked as a duplicate of this bug. ***
Comment 15Alexander Todorov
2010-06-15 10:02:20 UTC
I've used the steps to reproduce from the duplicate bug and tested with 0610.n.0 tree. No traceback. Moving to VERIFIED.
Comment 17releng-rhel@redhat.com
2010-07-02 18:57:22 UTC
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.
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 crypto.luks_close(self.mapName) File "/usr/lib/anaconda/storage/devices.py", line 1667, in teardown self.slave.originalFormat.teardown() File "/usr/lib/anaconda/storage/__init__.py", line 1293, in findExistingRootDevices device.teardown(recursive=True) 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 flags.cmdline.has_key("upgradeany")) File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1348, in setScreen self.anaconda.dispatch.gotoNext() File "/usr/lib/anaconda/gui.py", line 1261, in nextClicked self.setScreen () CryptoError: luks_close failed for luks-94a3ee80-0366-41a9-9247-0802a4a50385 Full report to be attached Version-Release number of selected component (if applicable): RHEL6.0-20100512.0-Server-x86_64-DVD1.iso How reproducible: 100% Steps to Reproduce: 1. Attempt to install to a system with an existing volume group containing an encrypted logical volume 2. 3. Actual results: Fails Expected results: Success Additional info: