Description of problem: Running the Fedora 20 installer, using custom partitioning against a previously partitioned Fedora 17 system. I also experienced a crash when attempting connect to a wireless network. Version-Release number of selected component: anaconda-20.25.15-1 The following was filed automatically by anaconda: anaconda 20.25.15-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/formats/disklabel.py", line 411, in read_int_from_sys return int(open(path).readline().strip()) File "/usr/lib/python2.7/site-packages/blivet/formats/disklabel.py", line 423, in free disk_length = read_int_from_sys("%s/size" % disk_root) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 884, in getFreeSpace disk_free = disk.format.free File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 829, in _currentFreeInfo return self.__storage.getFreeSpace(clearPartType=CLEARPART_TYPE_NONE) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 833, in _setCurrentFreeSpace self._free_space = sum(f[0] for f in self._currentFreeInfo.values()) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 846, in _updateSpaceDisplay self._setCurrentFreeSpace() File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2250, in on_remove_clicked self._updateSpaceDisplay() IOError: [Errno 2] No such file or directory: '/sys/class/block/dm-5/size' Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020\x20x86_64 quiet BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.10-301.fc20.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 20
Created attachment 848001 [details] File: anaconda-tb
Created attachment 848002 [details] File: anaconda.log
Created attachment 848003 [details] File: environ
Created attachment 848004 [details] File: lsblk_output
Created attachment 848005 [details] File: nmcli_dev_list
Created attachment 848006 [details] File: os_info
Created attachment 848007 [details] File: program.log
Created attachment 848008 [details] File: storage.log
Created attachment 848009 [details] File: syslog
Created attachment 848010 [details] File: ifcfg.log
Created attachment 848011 [details] File: packaging.log
This is some kind of race wherein the udev information required to identify an LVM logical volume is missing when we look for it, leading to problems later on. It's fairly likely that another attempt would yield a different outcome.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.