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'
Created attachment 743011 [details] File: anaconda-tb
Created attachment 743012 [details] File: anaconda.log
Created attachment 743013 [details] File: backtrace
Created attachment 743014 [details] File: environ
Created attachment 743015 [details] File: ifcfg.log
Created attachment 743016 [details] File: lsblk_output
Created attachment 743017 [details] File: nmcli_dev_list
Created attachment 743018 [details] File: packaging.log
Created attachment 743019 [details] File: program.log
Created attachment 743020 [details] File: storage.log
Created attachment 743021 [details] File: syslog
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.
*** This bug has been marked as a duplicate of bug 958897 ***