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 1193104

Summary: IndexError: list index out of range
Product: Red Hat Enterprise Linux 7 Reporter: Jaromír Cápík <jcapik>
Component: anacondaAssignee: Vratislav Podzimek <vpodzime>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: mbanas, mmello, ovasik, pholica, vpodzime
Target Milestone: rc   
Target Release: ---   
Hardware: ppc64   
OS: Unspecified   
Whiteboard: abrt_hash:c8c6775e6551bf87e68eea6f6a68cbb5f4ce14716c2038152a6f819c41c63531
Fixed In Version: anaconda-21.48.22.3-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 09:55:57 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:
Bug Depends On:    
Bug Blocks: 1205794    
Attachments:
Description Flags
File: anaconda-tb
none
File: anaconda.log
none
File: environ
none
File: lsblk_output
none
File: nmcli_dev_list
none
File: os_info
none
File: program.log
none
File: storage.log
none
File: syslog
none
File: ifcfg.log
none
File: packaging.log none

Description Jaromír Cápík 2015-02-16 15:05:53 UTC
Description of problem:
I just deleted existing LVM mountpoint in manual partitioning and the window showing the mountpoints got empty (usually there's a block of text and a button for creating the partitions manually). Few seconds later it crashed.

Version-Release number of selected component:
anaconda-19.31.111-1

The following was filed automatically by anaconda:
anaconda 19.31.111-1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1169, in _do_refresh
    firstPage = self._accordion.allPages[0]
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2524, in on_remove_clicked
    self._do_refresh()
IndexError: list index out of range

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   ro vnc noeject
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.10.0-210.el7.ppc64
product:        Red Hat Enterprise Linux 7"
release:        Red Hat Enterprise Linux ComputeNode release 7.1 Beta (Maipo)
release_type:   pre-release
type:           anaconda
version:        Red Hat Enterprise Linux ComputeNode"

Comment 1 Jaromír Cápík 2015-02-16 15:06:00 UTC
Created attachment 992234 [details]
File: anaconda-tb

Comment 2 Jaromír Cápík 2015-02-16 15:06:01 UTC
Created attachment 992235 [details]
File: anaconda.log

Comment 3 Jaromír Cápík 2015-02-16 15:06:03 UTC
Created attachment 992236 [details]
File: environ

Comment 4 Jaromír Cápík 2015-02-16 15:06:04 UTC
Created attachment 992237 [details]
File: lsblk_output

Comment 5 Jaromír Cápík 2015-02-16 15:06:05 UTC
Created attachment 992238 [details]
File: nmcli_dev_list

Comment 6 Jaromír Cápík 2015-02-16 15:06:06 UTC
Created attachment 992239 [details]
File: os_info

Comment 7 Jaromír Cápík 2015-02-16 15:06:08 UTC
Created attachment 992240 [details]
File: program.log

Comment 8 Jaromír Cápík 2015-02-16 15:06:12 UTC
Created attachment 992241 [details]
File: storage.log

Comment 9 Jaromír Cápík 2015-02-16 15:06:14 UTC
Created attachment 992242 [details]
File: syslog

Comment 10 Jaromír Cápík 2015-02-16 15:06:16 UTC
Created attachment 992243 [details]
File: ifcfg.log

Comment 11 Jaromír Cápík 2015-02-16 15:06:18 UTC
Created attachment 992244 [details]
File: packaging.log

Comment 17 Vratislav Podzimek 2015-07-01 12:43:11 UTC
Judging from the logs the possible reproducer seems to be:
1. start anaconda with multipath [*] disks with RHEL 7 installed on them
2. go to custom partitioning with those disks selected
3a. click to reformat the prepboot partition
4. delete all the mountpoints from the existing installation except for prepboot

or 3b. create new prepboot "mountpoint"
[*] not sure if really required

I don't have a setup available that I could use to test the above steps, but I tried to test a similar thing with GPT and biosboot instead of prepboot and that worked well with the rebased anaconda. So I'm marking this as fixed in the new anaconda. Please test the steps above and if it still fails, let us know so that we can do some more debugging.

Comment 22 errata-xmlrpc 2015-11-19 09:55:57 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2284.html