Bug 959038

Summary: TypeError: __init__() got an unexpected keyword argument 'container_raid_level'
Product: [Fedora] Fedora Reporter: Branko Grubić <bitlord0xff>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: anaconda-maint-list, g.kaviyarasu, jonathan, mkolman, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:59dbbcc1d71b46360983ce81c0c337814d505bb89198488944be4cdb4d67c019
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-03 12:32:33 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: backtrace
none
File: environ
none
File: ifcfg.log
none
File: lsblk_output
none
File: nmcli_dev_list
none
File: packaging.log
none
File: program.log
none
File: storage.log
none
File: syslog none

Description Branko Grubić 2013-05-03 04:09:50 UTC
Description of problem:
I was trying to install fedora on LUKS(LVM()), I selected Type LVM, and checked encryption. 
Removed all of my f18 partitions (using '-', custom partitoning). Created /boot (500M), swap (3G), / (30G) and /home (all other free space). And after that I clicked at /boot in the list it stopped responding and got this dialog about unexpected error (or something like that). And it didn't asked me for new luks key, maybe it asks for that later?
The following was filed automatically by anaconda:
anaconda 19.23-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/blivet/devicefactory.py", line 97, in get_device_factory
    return factory_class(blivet, size, disks, **kwargs)
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1875, in factoryDevice
    **kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 957, in _replace_device
    new_device = self.__storage.factoryDevice(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1237, in _save_right_side
    selector=selector)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2231, in _save_current_selector
    self._save_right_side(self._current_selector)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2241, in on_selector_clicked
    self._save_current_selector()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/accordion.py", line 220, in _onSelectorClicked
    cb(selector)
TypeError: __init__() got an unexpected keyword argument 'container_raid_level'

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

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2019-Beta-TC2\x20x86_64 quiet BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.9.0-0.rc8.git0.2.fc19.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        19-Beta-TC2

Truncated backtrace:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/accordion.py", line 220, in _onSelectorClicked
    cb(selector)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2241, in on_selector_clicked
    self._save_current_selector()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2231, in _save_current_selector
    self._save_right_side(self._current_selector)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1237, in _save_right_side
    selector=selector)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 957, in _replace_device
    new_device = self.__storage.factoryDevice(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1875, in factoryDevice
    **kwargs)
  File "/usr/lib/python2.7/site-packages/blivet/devicefactory.py", line 97, in get_device_factory
    return factory_class(blivet, size, disks, **kwargs)
TypeError: __init__() got an unexpected keyword argument 'container_raid_level'

Comment 1 Branko Grubić 2013-05-03 04:10:03 UTC
Created attachment 743011 [details]
File: anaconda-tb

Comment 2 Branko Grubić 2013-05-03 04:10:11 UTC
Created attachment 743012 [details]
File: anaconda.log

Comment 3 Branko Grubić 2013-05-03 04:10:15 UTC
Created attachment 743013 [details]
File: backtrace

Comment 4 Branko Grubić 2013-05-03 04:10:17 UTC
Created attachment 743014 [details]
File: environ

Comment 5 Branko Grubić 2013-05-03 04:10:19 UTC
Created attachment 743015 [details]
File: ifcfg.log

Comment 6 Branko Grubić 2013-05-03 04:10:22 UTC
Created attachment 743016 [details]
File: lsblk_output

Comment 7 Branko Grubić 2013-05-03 04:10:24 UTC
Created attachment 743017 [details]
File: nmcli_dev_list

Comment 8 Branko Grubić 2013-05-03 04:10:26 UTC
Created attachment 743018 [details]
File: packaging.log

Comment 9 Branko Grubić 2013-05-03 04:10:30 UTC
Created attachment 743019 [details]
File: program.log

Comment 10 Branko Grubić 2013-05-03 04:10:35 UTC
Created attachment 743020 [details]
File: storage.log

Comment 11 Branko Grubić 2013-05-03 04:10:42 UTC
Created attachment 743021 [details]
File: syslog

Comment 12 Branko Grubić 2013-05-03 04:25:02 UTC
I think this is "not" related to my partition setup, I tried after this to remove my existing partition setup (no luks, no raid, no lvm, just a classic paritioning setup swap, /boot, /, /home) and re-create the same classic setup without RAID, LVM, LUKS ... I was able to remove all partitions of the existing setup, created new, and when I tried to click on /boot (same as in this bug report) it stopped working, and dialog appears with an error message, and looks like same error message like in this title, so I didn't wanted to report it again.

Comment 13 Chris Lumens 2013-05-03 12:32:33 UTC

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