Bug 1412137

Summary:	Upgrading dnf makes dnf fail
Product:	[Fedora] Fedora	Reporter:	Jan Pazdziora <jpazdziora>
Component:	dnf	Assignee:	rpm-software-management
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	jpazdziora, lslebodn, packaging-team-maint, rpm-software-management, vmukhame
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-11 11:23:53 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 Jan Pazdziora 2017-01-11 10:53:53 UTC

Description of problem:

When dnf gets upgraded on rawhide, either directly or as a dependency, subsequent dnf invocations fail with

/usr/libexec/system-python: relocation error: /lib64/libpython3.6m.so.1.0: symbol getrandom, version GLIBC_2.25 not defined in file libc.so.6 with link time reference

Version-Release number of selected component (if applicable):

dnf-2.0.0-0.rc1.4.fc26.noarch -> dnf-2.0.0-2.fc26.noarch

How reproducible:

Deterministic.

Steps to Reproduce:
1. docker run --rm -ti fedora:rawhide bash
2. In the container: dnf upgrade -y dnf
   Or something like dnf install -y rpm-build which for some reason upgrades dnf as well.
3. In the container: dnf list

Actual results:

/usr/libexec/system-python: relocation error: /lib64/libpython3.6m.so.1.0: symbol getrandom, version GLIBC_2.25 not defined in file libc.so.6 with link time reference

Expected results:

No error.

Additional info:

Comment 1 Igor Gnatenko 2017-01-11 11:23:53 UTC


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

Comment 2 Lukas Slebodnik 2017-01-11 11:44:38 UTC

If you check related discussion on fedora-devel[1] you will find out that there is not a solution for this bug. They do not even want to rebuild docker images to prevent such bugs :-(

[1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/B565A2TWWZILEJRI6BFEVNMI6PLGXGO5/

Comment 3 Jan Pazdziora 2017-01-11 12:23:46 UTC

Yes, it's a sad world we live in. I think computers are just hard.