Bug 1045595 - No RAID levels shown in Configure Container dialog
Summary: No RAID levels shown in Configure Container dialog
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: mulhern
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-20 19:41 UTC by mulhern
Modified: 2014-10-31 16:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1054372 (view as bug list)
Environment:
Last Closed: 2014-10-31 16:19:05 UTC
Type: Bug


Attachments (Terms of Use)

Description mulhern 2013-12-20 19:41:09 UTC
Description of problem:

The dropdown list of RAID levels to select from is empty in all instances that I tried.

Version-Release number of selected component (if applicable):

anaconda-21.14-1

How reproducible:

Always in rawhide, not in current fedora or rhel7.

Steps to Reproduce:
1) Choose Installation Destination
2) Select both disks (I have two)...Done
3) Choose "I want to review/modify..."
4) Choose "Click here to create..."
5) For Device Type select LVM
6) Press "Modify" next to Volume Group choices.
7) Observe that the RAID Level label is not hidden, but the dropdown menu next to it is empty.

It does the same with Device Type BTRFS.

Actual results:

Drop down list of RAID levels empty.

Expected results:

Should see a list of RAID levels that are supported for this fs.

Additional info:

So, if one selects Device Type RAID a dropdown list of RAID levels appears on
the Manual Partitioning spoke and it appears to be correct.

The drop down labels are distinctly named ComboBoxes, raidStoreFiltered and containerRaidStoreFiltered but both boxes are backed by the same raidLevelStore.

It's obvious that the problem lies in this line:

for (i, row) in enumerate(self._raidLevelCombo.get_model()):

which is an empty generator for the bad case, but I can't tell why this should be the case in one instance and not another.

It also seems weird to me that that the refilter method is called. Apparently this method works by sending a row-changed signal for each row in the raidStore, but there doesn't seem to be any method registered for handling this signal

Comment 1 mulhern 2014-10-31 16:19:05 UTC
This problem went away insidiously and appears to have been due to some strange behavior of glade.


Note You need to log in before you can comment on or make changes to this bug.