Description of problem: 0. I booted a guest with a previous install + a raid5 1. I selected 1 disk, then 2, then 3 (because they were 1gb disks -each part of an array- , so i reached the point in which anaconda let me 'reclaim space') 2. Then i selected 'shrink' for each disk. 3. Anaconda behaved ok (by not unlocking the 'reclaim space' button for these partitions, since they were a part of a raid5 array) but i changed the last disk to 'delete' and then back to 'shrink'. This time the 'reclaim space' button was unlocked while it should not have. anaconda crashed when returning to the main hub. Version-Release number of selected component: anaconda-18.28 Additional info: libreport version: 2.0.17 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.6-3.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.28 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 374, in _removeDevice : raise ValueError("Cannot remove non-leaf device '%s'" % dev.name) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 428, in registerAction : self._removeDevice(action.device) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1207, in destroyDevice : self.devicetree.registerAction(action) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 779, in recursiveRemove : self.destroyDevice(device) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 259, in _scheduleActions : self.storage.recursiveRemove(device) :ValueError: Cannot remove non-leaf device 'vdc1'
Created attachment 646540 [details] File: anaconda-tb
Created attachment 646541 [details] File: product
Created attachment 646542 [details] File: type
Created attachment 646543 [details] File: ifcfg.log
Created attachment 646544 [details] File: storage.log
Created attachment 646545 [details] File: version
Created attachment 646546 [details] File: environ
Created attachment 646547 [details] File: executable
Created attachment 646548 [details] File: anaconda.log
Created attachment 646549 [details] File: syslog
Created attachment 646550 [details] File: hashmarkername
Created attachment 646551 [details] File: packaging.log
Created attachment 646552 [details] File: cmdline_file
Created attachment 646553 [details] File: release
Created attachment 646554 [details] File: program.log
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.