Bug 1730224 - libdnf 0.35.1 crashes with "Assertion `repoImpl->libsolvRepo == repo' failed"
Summary: libdnf 0.35.1 crashes with "Assertion `repoImpl->libsolvRepo == repo' failed"
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libdnf
Version: 8.1
Hardware: All
OS: Linux
Target Milestone: rc
: 8.0
Assignee: Packaging Maintenance Team
QA Contact: Karel Srot
Depends On: 1727424
TreeView+ depends on / blocked
Reported: 2019-07-16 08:53 UTC by Daniel Mach
Modified: 2020-11-14 09:00 UTC (History)
2 users (show)

Fixed In Version: libdnf-0.35.1-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1727424
Last Closed: 2019-11-05 22:22:23 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3583 0 None None None 2019-11-05 22:22:31 UTC

Comment 1 Daniel Mach 2019-07-16 08:55:17 UTC
The patch has been posted upstream and it seems to be fixing the problem already:

Moving to POST

Comment 3 Martin Pitt 2019-07-18 11:28:53 UTC
I am just running into this with cockpit-appstream's gating test, it seems to reproduce this bug (through a PackageKit crash) every time on the OSCI infra (unfortunately not on my local 8.1 VM): https://dashboard.osci.redhat.com/#/artifact/brew-build/aid/22673078?focus=tc:osci.brew-build.tier0.functional

journal shows that assertion failure: https://jenkins.osci.redhat.com/job/rhel-8-pr-pipeline/3085/artifact/package-tests/cockpit-appstream/logs/verify/TestUpdates-testBasic-rhel-8-1-
This is from https://jenkins.osci.redhat.com/blue/organizations/jenkins/rhel-8-pr-pipeline/detail/rhel-8-pr-pipeline/3085/artifacts

So I'm happy to re-run this to validate a fix.

Comment 4 Martin Pitt 2019-07-18 11:36:01 UTC
Or better yet, I think the original infra problem from your previous libdnf update got fixed (which hid the regression), so the next libdnf update should trigger cockpit-appstream automatically through reverse dependency testing.

Comment 12 errata-xmlrpc 2019-11-05 22:22:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.