Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

This bug has been copied from bug #1767159 and has been proposed to be backported to 7.8 z-stream (EUS).

 * sssd-1-16
  * f845355e32127c5e8f2bf700cdaa5b8721804232

Hi Alexey,

Could you please share the steps to reproduce this crash ? 
Would it be enough to run sanity tests to verify this bug or do we need to run specific regression test suites ?

Regards,
Amith

Hi,

(In reply to Amith from comment #5)
> Hi Alexey,
> 
> Could you please share the steps to reproduce this crash ? 

We do not have a reproducer.


> Would it be enough to run sanity tests to verify this bug or do we need to
> run specific regression test suites ?
> 
> Regards,
> Amith

This bug will be verified sanity only, and automation suites have be scheduled to ensure no related regressions are detected.

https://beaker.engineering.redhat.com/jobs/4229587
https://beaker.engineering.redhat.com/jobs/4229585

We are waiting for RHEL-7.8 prod-pipelines to finish all the Tier-1 tests to mark this bug verified.

Verified the bug on SSSD Version: sssd-1.16.4-37.el7_8.3.x86_64

The bug is verified Sanity Only and no related regression detected.

Here are the sanity runs:
- http://idm-artifacts.usersys.redhat.com/trigger-test-suite/production/487/trigger//report.html
- https://beaker.engineering.redhat.com/jobs/4229587
- https://beaker.engineering.redhat.com/jobs/4229585

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, 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:2090