Description of problem: 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/formats/__init__.py", line 342, in setup raise FormatSetupError("invalid device specification") File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 837, in setupParents _format.setup() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 700, in _preSetup self.setupParents(orig=orig) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 2150, in _preSetup return StorageDevice._preSetup(self, orig=orig) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 711, in setup if not self._preSetup(orig=orig): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 308, in setupParents parent.setup(orig=orig) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 2536, in setupParents Device.setupParents(self, orig=orig) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 700, in _preSetup self.setupParents(orig=orig) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 711, in setup if not self._preSetup(orig=orig): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 492, in execute self.device.setup(orig=True) 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) FormatSetupError: invalid device specification Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2018\x20x86_64 quiet BOOT_IMAGE=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 694122 [details] File: anaconda-tb
Created attachment 694123 [details] File: anaconda.log
Created attachment 694124 [details] File: environ
Created attachment 694125 [details] File: ifcfg.log
Created attachment 694126 [details] File: packaging.log
Created attachment 694127 [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.