Description of problem: Attempting to reproduce Bug 876180. Version-Release number of selected component: anaconda-18.29-1.fc18.x86_64 Additional info: libreport version: 2.0.17 cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8 kernel: 3.6.6-3.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.29 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1508, in _populate_right_side : typeCombo.set_active(type_index_map[device_type]) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1149, in _save_right_side : self._populate_right_side(selector) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1843, 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 647491 [details] File: anaconda-tb
Created attachment 647492 [details] File: environ
Created attachment 647493 [details] File: type
Created attachment 647494 [details] File: ifcfg.log
Created attachment 647495 [details] File: storage.log
Created attachment 647496 [details] File: version
Created attachment 647497 [details] File: program.log
Created attachment 647498 [details] File: executable
Created attachment 647499 [details] File: product
Created attachment 647500 [details] File: anaconda.log
Created attachment 647501 [details] File: hashmarkername
Created attachment 647502 [details] File: packaging.log
Created attachment 647504 [details] File: cmdline_file
Created attachment 647505 [details] File: release
Created attachment 647506 [details] File: messages
*** Bug 877874 has been marked as a duplicate of this bug. ***
We shouldn't be letting users change the encryption setting when the encryption is on existing devices that are at a level below what we are editing (eg: editing an LV in a preexisting VG whose PVs are encrypted).
-1 NTH. At this point we don't really want to be poking at 'doctor it hurts' stuff, I don't think.
Discussed at 2012-11-21 NTH review meeting. Agreed it's too late to be poking at partitioning code just to save user errors, rejected NTH.
pykickstart-1.99.22-1.fc18, anaconda-18.34-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2012-19380/pykickstart-1.99.22-1.fc18,anaconda-18.34-1.fc18
Package pykickstart-1.99.22-1.fc18, anaconda-18.34-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing pykickstart-1.99.22-1.fc18 anaconda-18.34-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19380/pykickstart-1.99.22-1.fc18,anaconda-18.34-1.fc18 then log in and leave karma (feedback).
Package pykickstart-1.99.22-1.fc18, anaconda-18.35-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing pykickstart-1.99.22-1.fc18 anaconda-18.35-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19380/pykickstart-1.99.22-1.fc18,anaconda-18.35-1.fc18 then log in and leave karma (feedback).
pykickstart-1.99.22-1.fc18, anaconda-18.35-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.