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.

Description of problem:
I tried to set up manual partitioning on RHEL7-20121022. After entering the parititioning screen, Anaconda crashed.

There is an LVM volume group with one LUKS-encrypted partition (locked), one ext4 and one btrfs partition.


Version-Release number of selected component:
anaconda-18.19

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.19 exception report
:Traceback (most recent call first):
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 900, in _save_right_side
:    device_type = device_type_map[device_type]
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1831, in on_page_clicked
:    self._save_right_side(self._current_selector)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/accordion.py", line 119, in _onExpanded
:    cb(obj.get_child())
:KeyError: None

Created attachment 633186 [details]
File: anaconda-tb

Created attachment 633187 [details]
File: product

Created attachment 633188 [details]
File: type

Created attachment 633189 [details]
File: storage.log

Created attachment 633190 [details]
File: version

Created attachment 633191 [details]
File: environ

Created attachment 633192 [details]
File: anaconda.log

Created attachment 633193 [details]
File: syslog

Created attachment 633194 [details]
File: hashmarkername

Created attachment 633195 [details]
File: packaging.log

Created attachment 633196 [details]
File: cmdline_file

Created attachment 633197 [details]
File: release

Created attachment 633198 [details]
File: program.log

This should be fixed in anaconda-18.28-1 if not earlier versions.

Verified with anaconda-19.30.13-1 and partitioning described in the description:
LVM:
 - encrypted LV
 - ext4 LV
 - btrfs LV

anaconda showed all devices correctly, I was able to unlock the encrypted device and reuse all devices. After the installation, system booted correctly (asked for password for the encrypted device), all filesystems were mounted.

Moving to VERIFIED.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.