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.

Bug 866372

Summary: FormatSetupError: invalid device specification
Product: Red Hat Enterprise Linux 7 Reporter: Vitezslav Humpa <vhumpa>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: dcantrell
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:df19160bac314502742d95a311e065b4428e6056236d75f88d5f7f3e784baa97
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-15 20:52:05 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: 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 Vitezslav Humpa 2012-10-15 08:40:48 UTC
Description of problem:
Anaconda crashed on typing in a password for an encrypted LUKS LVM in the 'Manual Partitioning' screen.

RHEL7...1012 through RH PXE


Version-Release number of selected component:
anaconda-18.16

Additional info:
libreport version: 2.0.16
cmdline:        /usr/bin/python  /sbin/anaconda
kernel:         3.6.0-0.28.el7.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/__init__.py", line 342, in setup
:    raise FormatSetupError("invalid device specification")
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/luks.py", line 168, in setup
:    DeviceFormat.setup(self, *args, **kwargs)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1959, in on_unlock_clicked
:    device.format.setup()
:FormatSetupError: invalid device specification

Comment 1 Vitezslav Humpa 2012-10-15 08:40:56 UTC
Created attachment 627246 [details]
File: anaconda-tb

Comment 2 Vitezslav Humpa 2012-10-15 08:40:59 UTC
Created attachment 627247 [details]
File: product

Comment 3 Vitezslav Humpa 2012-10-15 08:41:01 UTC
Created attachment 627248 [details]
File: type

Comment 4 Vitezslav Humpa 2012-10-15 08:41:04 UTC
Created attachment 627249 [details]
File: storage.log

Comment 5 Vitezslav Humpa 2012-10-15 08:41:06 UTC
Created attachment 627250 [details]
File: version

Comment 6 Vitezslav Humpa 2012-10-15 08:41:08 UTC
Created attachment 627251 [details]
File: environ

Comment 7 Vitezslav Humpa 2012-10-15 08:41:11 UTC
Created attachment 627252 [details]
File: anaconda.log

Comment 8 Vitezslav Humpa 2012-10-15 08:41:13 UTC
Created attachment 627253 [details]
File: syslog

Comment 9 Vitezslav Humpa 2012-10-15 08:41:15 UTC
Created attachment 627254 [details]
File: hashmarkername

Comment 10 Vitezslav Humpa 2012-10-15 08:41:17 UTC
Created attachment 627255 [details]
File: packaging.log

Comment 11 Vitezslav Humpa 2012-10-15 08:41:19 UTC
Created attachment 627256 [details]
File: cmdline_file

Comment 12 Vitezslav Humpa 2012-10-15 08:41:21 UTC
Created attachment 627257 [details]
File: release

Comment 13 Vitezslav Humpa 2012-10-15 08:41:23 UTC
Created attachment 627258 [details]
File: program.log

Comment 14 Jesse Keating 2012-10-15 20:52:05 UTC
Lets track this by way of Fedora.

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