Bug 1632177
Summary: | dnf segfault in libdnf::TransactionItem::saveReplacedBy() | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nerijus Baliūnas <nerijus> |
Component: | dnf | Assignee: | Daniel Mach <dmach> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 29 | CC: | awilliam, dmach, klember, lruzicka, markus.linnala, mattdm, mblaha, nerijus, packaging-team-maint, peter.hutterer, robatino, rpm-software-management, vmukhame, zbyszek |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | AcceptedBlocker | ||
Fixed In Version: | dnf-4.0.4-1.fc29 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-22 16:13:38 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1517013 |
Description
Nerijus Baliūnas
2018-09-24 10:10:43 UTC
Could you provide the core dump and also ideally contents of the /var/lib/dnf/ directory so we can reproduce the problem? https://sat.lt/core.dnf.0.5aab7f53580f4cbe9f543b262aaa786c.91743.1537782703000000.lz4 https://sat.lt/dnf.tgz dnf started to work after deleting /var/lib/dnf directory. I got essentially same dump when trying to do 'dnf check-update' or 'dnf update' etc. Deleting /var/lib/dnf directory solved the problem for me too. I got this problem with f29 beta version of dnf and then I upgraded it by hand from koji without any progress and current versions are: dnf-plugins-core-3.0.4-1.fc29.noarch python3-dnf-plugins-extras-common-3.0.1-1.fc29.noarch python3-dnf-plugin-leaves-3.0.4-1.fc29.noarch python3-dnf-plugin-versionlock-3.0.4-1.fc29.noarch dnfdragora-updater-1.0.1-13.git20180108.b0e8a66.fc29.noarch dnf-3.6.1-1.fc29.noarch etckeeper-dnf-1.18.8-1.fc29.noarch libdnf-debuginfo-0.20.0-1.fc29.x86_64 dnf-automatic-3.6.1-1.fc29.noarch dnf-utils-3.0.4-1.fc29.noarch dnfdaemon-0.3.19-4.fc29.noarch python3-dnf-3.6.1-1.fc29.noarch python3-dnf-plugins-core-3.0.4-1.fc29.noarch python3-dnfdaemon-0.3.19-4.fc29.noarch python3-dnf-plugin-rpmconf-3.0.1-1.fc29.noarch libdnf-0.20.0-1.fc29.x86_64 dnfdragora-1.0.1-13.git20180108.b0e8a66.fc29.noarch python3-libdnf-0.20.0-1.fc29.x86_64 python3-dnf-plugin-local-3.0.4-1.fc29.noarch libdnf-debugsource-0.20.0-1.fc29.x86_64 python3-dnf-plugin-system-upgrade-3.0.1-1.fc29.noarch dnfdaemon-selinux-0.3.19-4.fc29.noarch dnf-data-3.6.1-1.fc29.noarch Just ran into this too after a a dnf system-upgrade to f29. Deleting /var/lib/dnf did the trick, before that all dnf operations failed with the above stacktrace. $ rpm -qa | grep dnf libdnf-0.20.0-1.fc29.x86_64 python3-dnf-plugins-core-3.0.4-1.fc29.noarch python2-dnf-plugins-extras-common-3.0.2-1.fc29.noarch dnf-yum-4.0.3.6.1-2.fc29.noarch dnf-3.6.1-2.fc29.noarch python3-dnf-plugins-extras-common-3.0.2-1.fc29.noarch python3-dnf-plugin-system-upgrade-3.0.2-1.fc29.noarch python3-libdnf-0.20.0-1.fc29.x86_64 python2-dnf-3.6.1-2.fc29.noarch python2-libdnf-0.20.0-1.fc29.x86_64 dnf-automatic-3.6.1-2.fc29.noarch dnf-data-3.6.1-2.fc29.noarch dnf-plugins-core-3.0.4-1.fc29.noarch python3-dnf-3.6.1-2.fc29.noarch I still have the /var/lib/dnf directory for now, let me know if you need it for debugging. Seems worth considering as a Final blocker, we really do not want people who upgrade to F29 hitting this. +1 blocker +1 blocker Marking accepted, then. dmach, tomasz torcz suggests 1600917 is probably the same bug as this; can you check and close one as a dupe of the other (doesn't really matter which way around, it's up to you) if you agree? Thanks! Yes, it's a duplicate. I've created a fix that avoids the crash: https://github.com/rpm-software-management/libdnf/pull/614 We'll need more time for a proper patch, but that can be done after F29 release. dnf-4.0.4-1.fc29 dnf-plugins-core-4.0.0-2.fc29 libdnf-0.22.0-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2789f6b6e7 dnf-4.0.4-1.fc29, dnf-plugins-core-4.0.0-2.fc29, libdnf-0.22.0-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2789f6b6e7 The update solved the problem. The above mentioned commands do not traceback anymore and the operation completes. Verified. anaconda-29.24.6-1.fc29 dnf-4.0.4-1.fc29 dnf-plugins-core-4.0.0-2.fc29 libblockdev-2.20-2.fc29 libdnf-0.22.0-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2789f6b6e7 anaconda-29.24.7-1.fc29, dnf-4.0.4-1.fc29, dnf-plugins-core-4.0.0-2.fc29, libblockdev-2.20-2.fc29, libdnf-0.22.0-5.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2789f6b6e7 anaconda-29.24.7-1.fc29, dnf-4.0.4-1.fc29, dnf-plugins-core-4.0.0-2.fc29, libblockdev-2.20-2.fc29, libdnf-0.22.0-5.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. |