Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libdnf
Version: 8.1
Hardware: All
OS: Linux
high
urgent
Target Milestone: rc
: 8.0
Assignee: Packaging Maintenance Team
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On: 1727424
Blocks:
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
Environment:
Last Closed: 2019-11-05 22:22:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
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:
https://github.com/rpm-software-management/libdnf/pull/761

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-10.88.0.1-22-FAIL.log
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.

https://access.redhat.com/errata/RHSA-2019:3583


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