Bug 1463505

Summary:	DNF errors with "Assertion `ret == 0' failed."
Product:	[Fedora] Fedora	Reporter:	Jiří Vymazal <jvymazal>
Component:	dnf	Assignee:	rpm-software-management
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	cunio, packaging-team-maint, rpm-software-management, vmukhame
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-21 07:45:35 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:

Description Jiří Vymazal 2017-06-21 07:17:13 UTC

Description of problem:
Cannot use dnf

Version-Release number of selected component (if applicable):
1.1.10
  Installed: dnf-0:1.1.10-6.fc25.noarch at 2017-03-28 08:29
  Built    : Fedora Project at 2017-03-15 08:52

  Installed: rpm-0:4.13.0.1-1.fc25.x86_64 at 2017-03-28 08:29
  Built    : Fedora Project at 2017-02-24 12:48

How reproducible:
run any dnf command (tried install, update, upgrade)

Steps to Reproduce:
1. $ sudo dnf upgrade

Actual results:
system-python: /builddir/build/BUILD/hawkey-0.6.4/src/sack.c:354: load_ext: Assertion `ret == 0' failed.
zsh: abort      sudo dnf upgrade

Expected results:
dnf upgrade runs

Additional info:
before this started happening dnf timed out on probably some back-end connection
issue and encountered Transaction check error concerning dnf-installed and gem-installed rake packages.

Comment 1 Jiří Vymazal 2017-06-21 07:26:11 UTC

Also tried running "sudo dnf clean all" but it did not help.

Comment 2 Igor Gnatenko 2017-06-21 07:45:35 UTC

rm -rf /var/cache/dnf/*

DNF 1.x is unsupported and will get only security fixes, so closing.

Comment 3 Jiří Vymazal 2017-06-21 08:28:26 UTC

Ok, just how am I supposed to "correctly" upgrade dnf to supported version (and by the way why is this not handled (semi-)automatically during dnf upgrade)? The work-around you listed above worked only for one dnf command after it and now no longer works at all. Tried also reboot and coupling your work-around with dnf clean all but nothing helps.

Comment 4 Igor Gnatenko 2017-06-21 09:24:09 UTC

*** Bug 1463582 has been marked as a duplicate of this bug. ***

Comment 5 Igor Gnatenko 2017-06-21 09:24:16 UTC

*** Bug 1463580 has been marked as a duplicate of this bug. ***

Comment 6 Jacek Pawlyta 2017-06-21 11:09:20 UTC

Jiri,
In ma case updates-testing repo caused the error.

Disabling it helps:

dnf --disabelrepo=updates-tetsing update


Igor, 
there is no any other version of dnf than 1.x in any official fedora 25 repos.
What should we use then?

Comment 7 Jacek Pawlyta 2017-06-21 11:14:14 UTC

I think the bug should be be reopened with hight priority beacuse it blocks updating the system.

Comment 8 Igor Gnatenko 2017-06-21 11:14:55 UTC


*** This bug has been marked as a duplicate of bug 1463561 ***