Bug 1214634

Summary: Error: g-bd-crypto-error-quark: Failed to activate device: Operation not permitted (0)
Product: [Fedora] Fedora Reporter: Jens Tingleff <jensting>
Component: python-blivetAssignee: David Lehman <dlehman>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: amulhern, anaconda-maint-list, bcl, dlehman, g.kaviyarasu, jonathan, vanmeeuwen+fedora, vpodzime
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:150623d1fffd7aede383de28d726e29eef2936760c4fbae3b1918836a4ef2c2e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-30 11:39:20 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: anaconda.log
none
File: environ
none
File: journalctl
none
File: lsblk_output
none
File: nmcli_dev_list
none
File: os_info
none
File: program.log
none
File: storage.log
none
File: ifcfg.log none

Description Jens Tingleff 2015-04-23 09:33:07 UTC
Description of problem:
Crashed after failure to open existing LUKS encrypted partition in LVM volume given known bad password.

Installation from Fedora 22 B3 64 bt live burnt onto a DVD. Initial dry-run installation (not mounting the LUKS partition) worked fine. Attempt to include LUKS encrypted partition but giving bad password and clicking "Unlock" hangs installer. 


Version-Release number of selected component:
anaconda-core-22.20.9-1.fc22.x86_64

The following was filed automatically by anaconda:
anaconda 22.20.9-1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/gi/overrides/BlockDev.py", line 71, in crypto_luks_open
    return _crypto_luks_open(device, name, passphrase, key_file)
  File "/usr/lib/python2.7/site-packages/blivet/formats/luks.py", line 187, in setup
    key_file=self._key_file)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2660, in on_unlock_clicked
    device.format.setup()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/utils.py", line 242, in _run_once_one_arg
    self._func(*args, **kwargs)
Error: g-bd-crypto-error-quark: Failed to activate device: Operation not permitted (0)

Additional info:
cmdline:        /usr/bin/python2  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base
cmdline_file:   BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-22_B-3 rootfstype=auto ro rd.live.image quiet  rhgb rd.luks=0 rd.md=0 rd.dm=0 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         4.0.0-0.rc5.git4.1.fc22.x86_64
other involved packages: libblockdev-0.9-1.fc22.x86_64, python-blivet-1.0.7-1.fc22.noarch, anaconda-gui-22.20.9-1.fc22.x86_64
product:        Fedora
release:        Fedora release 22 (Twenty Two)
type:           anaconda
version:        22

Comment 1 Jens Tingleff 2015-04-23 09:33:17 UTC
Created attachment 1017835 [details]
File: anaconda-tb

Comment 2 Jens Tingleff 2015-04-23 09:33:18 UTC
Created attachment 1017836 [details]
File: anaconda.log

Comment 3 Jens Tingleff 2015-04-23 09:33:20 UTC
Created attachment 1017837 [details]
File: environ

Comment 4 Jens Tingleff 2015-04-23 09:33:24 UTC
Created attachment 1017838 [details]
File: journalctl

Comment 5 Jens Tingleff 2015-04-23 09:33:25 UTC
Created attachment 1017839 [details]
File: lsblk_output

Comment 6 Jens Tingleff 2015-04-23 09:33:27 UTC
Created attachment 1017840 [details]
File: nmcli_dev_list

Comment 7 Jens Tingleff 2015-04-23 09:33:28 UTC
Created attachment 1017841 [details]
File: os_info

Comment 8 Jens Tingleff 2015-04-23 09:33:30 UTC
Created attachment 1017842 [details]
File: program.log

Comment 9 Jens Tingleff 2015-04-23 09:33:41 UTC
Created attachment 1017843 [details]
File: storage.log

Comment 10 Jens Tingleff 2015-04-23 09:33:42 UTC
Created attachment 1017844 [details]
File: ifcfg.log

Comment 11 Jens Tingleff 2015-04-23 10:05:08 UTC
I checked, and the installation does run correctly if the password is correct. So, this is an error handling bug (but since it's no fun to have the installer crash, it's still a bug, IMHO)

Comment 12 Vratislav Podzimek 2015-04-30 11:39:20 UTC
This has in the meantime changed into a different traceback tracked in the bug #1217438. Closing this bug report as a duplicate.

*** This bug has been marked as a duplicate of bug 1217438 ***