Version-Release number of selected component: anaconda-20.25.15-1.fc20.x86_64 The following was filed automatically by anaconda: anaconda 20.25.15-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/__init__.py", line 613, in _setDefaultBootTarget if ts.dbMatch("provides", 'service(graphical-login)').count() and \ File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/__init__.py", line 642, in postInstall self._setDefaultBootTarget() File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/livepayload.py", line 150, in postInstall super(LiveImagePayload, self).postInstall() File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 168, in doInstall payload.postInstall() File "/usr/lib64/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 192, in run threading.Thread.run(self, *args, **kwargs) error: rpmdb open failed Additional info: cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Desktop-x86_64-20-1 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.10-301.fc20.x86_64 other involved packages: python-libs-2.7.5-9.fc20.x86_64 product: Fedora release: Fedora release 20 (Heisenbug) type: anaconda version: 20 Potential duplicate: bug 868755
Created attachment 858671 [details] File: anaconda-tb
Created attachment 858672 [details] File: anaconda.log
Created attachment 858673 [details] File: environ
Created attachment 858674 [details] File: journalctl
Created attachment 858675 [details] File: lsblk_output
Created attachment 858676 [details] File: nmcli_dev_list
Created attachment 858677 [details] File: os_info
Created attachment 858678 [details] File: program.log
Created attachment 858679 [details] File: storage.log
Created attachment 858680 [details] File: ifcfg.log
Created attachment 858681 [details] File: packaging.log
Yet more lies from some component about how much disk space is required: 10:53:22,687 INFO program: Running... rsync -pogAXtlHrDx --exclude /dev/ --exclude /proc/ --exclude /sys/ --exclude /run/ --exclude /boot/*rescue* --exclude /etc/machine-id /mnt/install/source/ /mnt/sysimage 11:00:23,386 INFO program: rsync: write failed on "/mnt/sysimage/usr/share/tracker/ontologies/41-mfo.ontology": No space left on device (28) 11:00:23,478 INFO program: rsync error: error in file IO (code 11) at receiver.c(389) [receiver=3.1.0pre1]
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.