Bug 867533

Summary: LUKSError: luks device not configured
Product: [Fedora] Fedora Reporter: Richard Marko <rmarko>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, awilliam, g.kaviyarasu, jberan, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8636a1c8633a31b1b029eb6e758feddc2e80f4156a69b9d29e850327a224e8ad
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-23 05:11:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: anaconda-tb
none
File: product
none
File: type
none
File: ifcfg.log
none
File: storage.log
none
File: version
none
File: environ
none
File: anaconda.log
none
File: syslog
none
File: hashmarkername
none
File: packaging.log
none
File: cmdline_file
none
File: release
none
File: program.log none

Description Richard Marko 2012-10-17 16:32:55 UTC
Description of problem:
Trying to access luks device.

Version-Release number of selected component:
anaconda-18.16

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.16 exception report
:Traceback (most recent call first):
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/luks.py", line 163, in setup
:    raise LUKSError("luks device not configured")
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1959, in on_unlock_clicked
:    device.format.setup()
:LUKSError: luks device not configured

Comment 1 Richard Marko 2012-10-17 16:32:58 UTC
Created attachment 628941 [details]
File: anaconda-tb

Comment 2 Richard Marko 2012-10-17 16:33:00 UTC
Created attachment 628942 [details]
File: product

Comment 3 Richard Marko 2012-10-17 16:33:02 UTC
Created attachment 628944 [details]
File: type

Comment 4 Richard Marko 2012-10-17 16:33:04 UTC
Created attachment 628945 [details]
File: ifcfg.log

Comment 5 Richard Marko 2012-10-17 16:33:06 UTC
Created attachment 628946 [details]
File: storage.log

Comment 6 Richard Marko 2012-10-17 16:33:08 UTC
Created attachment 628947 [details]
File: version

Comment 7 Richard Marko 2012-10-17 16:33:10 UTC
Created attachment 628948 [details]
File: environ

Comment 8 Richard Marko 2012-10-17 16:33:13 UTC
Created attachment 628949 [details]
File: anaconda.log

Comment 9 Richard Marko 2012-10-17 16:33:15 UTC
Created attachment 628950 [details]
File: syslog

Comment 10 Richard Marko 2012-10-17 16:33:17 UTC
Created attachment 628951 [details]
File: hashmarkername

Comment 11 Richard Marko 2012-10-17 16:33:19 UTC
Created attachment 628952 [details]
File: packaging.log

Comment 12 Richard Marko 2012-10-17 16:33:21 UTC
Created attachment 628953 [details]
File: cmdline_file

Comment 13 Richard Marko 2012-10-17 16:33:23 UTC
Created attachment 628954 [details]
File: release

Comment 14 Richard Marko 2012-10-17 16:33:26 UTC
Created attachment 628955 [details]
File: program.log

Comment 15 David Lehman 2012-10-18 17:05:08 UTC
This should be fixed by the patch for bug 865247, which expanded the set of exceptions caught when testing the provided passphrase. The fix for that bug will hopefully be in anaconda-18.19-1.

Comment 16 Fedora Update System 2012-10-20 01:31:36 UTC
anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.19-1.fc18

Comment 17 Fedora Update System 2012-10-20 03:50:12 UTC
Package anaconda-18.19-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.19-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16528/anaconda-18.19-1.fc18
then log in and leave karma (feedback).

Comment 18 Adam Williamson 2012-11-23 05:11:34 UTC
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.