Bug 2000022

Summary: /usr/bin/python3: symbol lookup error: /lib64/libpython3.10.so.1.0: undefined symbol: close_range, version GLIBC_2.34
Product: [Fedora] Fedora Reporter: Zbigniew Jędrzejewski-Szmek <zbyszek>
Component: python3.10Assignee: Python Maintainers <python-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: rawhideCC: cstratak, mhroncok, python-maint, python-sig, thrnciar, torsava, vstinner
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: 2021-09-01 08:34:41 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 Zbigniew Jędrzejewski-Szmek 2021-09-01 08:25:50 UTC
Description of problem:
In rawhide mock (on F33, not sure if that matters), I get $subject as error when I execute python3.

Version-Release number of selected component (if applicable):
python3-3.10.0~rc1-1.fc35.x86_64
glibc-2.33.9000-36.fc35.x86_64

How reproducible:
Deterministic

Steps to Reproduce:
1. mock --shell
2. python3

Comment 1 Zbigniew Jędrzejewski-Szmek 2021-09-01 08:34:41 UTC
I renitiailized the mock chroots, and I get a newer glibc:

<mock-chroot-f35> sh-5.1# rpm -q python3 glibc
python3-3.10.0~rc1-1.fc35.x86_64
glibc-2.34-1.fc35.x86_64

<mock-chroot-rawhide> sh-5.1# rpm -q python3 glibc
python3-3.10.0~rc1-1.fc35.x86_64
glibc-2.34.9000-4.fc36.x86_64

and in both cases python3 works. So it seems that the original issue was caused
by some stale mock definition. I'll close this, even though it seems that some version
dependency is missing somewhere.

Comment 2 Miro Hrončok 2021-09-01 10:15:17 UTC
> even though it seems that some version dependency is missing somewhere.

Yes, newer glibc now has a requirements generator to avoid this in the future. Se https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/MENH65L5JJLMT7JGN4LB2L67WXRFW6ZT