Description of problem: I got some btrfs problem, after machine reboot, yum-complete-transaction failed and then rpm reports broken database. I guess yum should handle underlying problems more gracefully then just bailing out with "core dumped" ... Version-Release number of selected component: yum-utils-1.1.31-20.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/python -tt /sbin/yum-complete-transaction crash_function: __atomic_inc executable: /usr/bin/python2.7 kernel: 3.13.10-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 __atomic_inc at ../../src/dbinc/atomic.h:153 #1 __memp_alloc at ../../src/mp/mp_alloc.c:329 #2 __memp_fget at ../../src/mp/mp_fget.c:646 #3 __db_goff at ../../src/db/db_overflow.c:173 #4 __dbc_iget at ../../src/db/db_cam.c:1132 #5 __dbc_get at ../../src/db/db_cam.c:770 #6 __dbc_get_pp at ../../src/db/db_iface.c:2361 #7 dbiCursorGet at backend/db3.c:394 #8 rpmdbNextIterator at rpmdb.c:1831 #9 rpmmi_iternext at rpmmi-py.c:73
Created attachment 891757 [details] File: backtrace
Created attachment 891758 [details] File: cgroup
Created attachment 891759 [details] File: core_backtrace
Created attachment 891760 [details] File: dso_list
Created attachment 891761 [details] File: environ
Created attachment 891762 [details] File: exploitable
Created attachment 891763 [details] File: limits
Created attachment 891764 [details] File: maps
Created attachment 891765 [details] File: open_fds
Created attachment 891766 [details] File: proc_pid_status
Created attachment 891767 [details] File: var_log_messages
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.