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 1778694 - libtalloc 2.2.0 update breaks Samba's Python bindings: undefined symbol: pytalloc_reference_ex
Summary: libtalloc 2.2.0 update breaks Samba's Python bindings: undefined symbol: pyta...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libtalloc
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 8.2
Assignee: Andreas Schneider
QA Contact: sssd-qe
URL:
Whiteboard:
Depends On:
Blocks: ipa_rebase_rhel82_482 1754417
TreeView+ depends on / blocked
 
Reported: 2019-12-02 10:29 UTC by Christian Heimes
Modified: 2021-09-03 15:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
This will require a release note for Beta
Clone Of:
Environment:
Last Closed: 2019-12-06 09:34:53 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1754417 0 unspecified CLOSED Rebase talloc to version 2.2.0 for samba 2021-02-22 00:41:40 UTC

Description Christian Heimes 2019-12-02 10:29:02 UTC
Description of problem:
The recent update of libtalloc to libtalloc-2.2.0-5.el8 breaks Samba's Python bindings. The samba Python package fails to import because the pytalloc_reference_ex symbol is missing.

The bug affects IPA's AD trust feature and prevents IPA to establish a trust with Active Directory.

Version-Release number of selected component (if applicable):
libtalloc-2.2.0-5.el8.x86_64
python3-samba-4.10.4-101.el8_1.x86_64
python3-talloc-2.2.0-5.el8.x86_64

How reproducible:
always

Steps to Reproduce:
# python3
Python 3.6.8 (default, Oct 29 2019, 14:26:23) 
[GCC 8.3.1 20190507 (Red Hat 8.3.1-4)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import samba

Actual results:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib64/python3.6/site-packages/samba/__init__.py", line 29, in <module>
    import samba.param
ImportError: /usr/lib64/python3.6/site-packages/samba/param.cpython-36m-x86_64-linux-gnu.so: undefined symbol: pytalloc_reference_ex, version PYTALLOC_UTIL.PY3_2.1.5

Expected results:
No error

Additional info:

Comment 3 Andreas Schneider 2019-12-02 11:31:20 UTC
libtalloc, libtevent, libtdb, libldb, samba and sssd need to use side-tag gating. We set up rhel-8.2.0-samba-and-sssd-stack-gate as a tag for this. However there is a bug in samba packaging which needs to be fixed now (found by that side-tag gaging).

Trying to build new samba package for a new gating run.


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