Description of problem: Tried to configure out of the mainline. On top of a Fedora 17 installation Got the hard failure Could not go back and fix whatever badness is in there. Will have to restart. The following was filed automatically by anaconda: anaconda 18.37.11 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 806, in _preDestroy raise DeviceError("Cannot destroy non-leaf device", self.name) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 1523, in _preDestroy StorageDevice._preDestroy(self) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 1505, in resize self._preDestroy() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 370, in execute self.device.resize() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 323, in processActions action.execute() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 323, in doIt self.devicetree.processActions() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 174, in turnOnFilesystems storage.doIt() File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 114, in doInstall turnOnFilesystems(storage) File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run threading.Thread.run(self, *args, **kwargs) DeviceError: ('Cannot destroy non-leaf device', 'sda1') Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=F18/x86_64/isolinux/initrd.img vnc headless shell sshd ksdevice=link lang=en_US keymap=us repo=nfs:vers=3:angel-eyes:/nfs/cistern/fedora/mirrors/18/replica/development/18/x86_64/os BOOT_IMAGE=F18/x86_64/isolinux/vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.6.10-4.fc18.x86_64 other involved packages: package: anaconda-18.37.11 product: Fedora release: Cannot get release name. type: libreport version: 18
Created attachment 679326 [details] File: anaconda-tb
Created attachment 679327 [details] File: anaconda.log
Created attachment 679328 [details] File: environ
Created attachment 679329 [details] File: ifcfg.log
Created attachment 679330 [details] File: packaging.log
Created attachment 679331 [details] File: program.log
Created attachment 679332 [details] File: storage.log
Created attachment 679333 [details] File: syslog
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.