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 1893443 - User lookups over the InfoPipe responder fail intermittently [rhel-7.9.z]
Summary: User lookups over the InfoPipe responder fail intermittently [rhel-7.9.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Sumit Bose
QA Contact: Anuj Borah
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-31 16:12 UTC by Marco Rhodes
Modified: 2022-04-06 02:23 UTC (History)
16 users (show)

Fixed In Version: sssd-1.16.5-10.el7_9.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 11:22:17 UTC
Target Upstream Version:
Embargoed:
striker: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 5382 0 None closed User lookups over the InfoPipe responder fail intermittently 2020-12-30 09:32:25 UTC

Comment 10 Sumit Bose 2020-11-03 09:11:40 UTC
Upstream ticket:
https://github.com/SSSD/sssd/issues/5382

Comment 16 Pavel Březina 2020-11-05 10:47:45 UTC
Pushed PR: https://github.com/SSSD/sssd/pull/5383

* `master`
    * 81e757b7b1d69893b5725f9c148c55d89c779e7b - ifp: fix use-after-free
* `sssd-1-16`
    * 316b8cde698bd4586a70fc5ed50a70dedc4b424f - ifp: fix use-after-free

Comment 25 Jeremiah Buckley 2020-11-11 13:08:23 UTC
Hi, yes, because this is patch in production they don't want to run the patch unless it's signed or they have the checksums. So, as far as I know (unless they did it late last night) they still haven't tested it. Thanks for the estimated ETA. I think the checksums and a rough idea of when they can expect a signed release should help the client plan.

Comment 38 Pavel Březina 2020-11-23 10:55:34 UTC
Pushed PR: https://github.com/SSSD/sssd/pull/5411

* `master`
    * 3b158934cbb8f87cbfaf1650389b8dcd654b92ca - ifp: fix original fix use-after-free

Comment 41 Alexey Tikhonov 2020-11-25 11:11:20 UTC
Pushed PR: https://github.com/SSSD/sssd/pull/5416

* `sssd-1-16`
    * 1b523ba2a6bfba6974c9c909d6180590d16cc6bd - fp: fix original fix use-after-free - 1.16 version

Comment 51 errata-xmlrpc 2020-12-15 11:22:17 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 (sssd bug fix and enhancement update), 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/RHBA-2020:5459


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