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.

Description of problem:

During an overload on the LDAP backend, all the sssd client got disconnected.
The issue was longer than 15 minutes.
Once the clients were reconnected, given the default smart refresh timeout (15 minutes), all the clients have requested the SUDO rules update in a small time frame, overloading once again the LDAP backend, and triggering once again the issue in a loop cause-effect.

As sssd has several "random" added for the providers and the reconnections, 
the suggestion consists of introducing a random timeout for the refresh of the SUDO rules.

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

Any

How reproducible:


Steps to Reproduce:

1. introduce a down of the LDAP backend for a longer time than 15 minutes
2. put the LDAP backend back online
3.

Actual results:

Exactly upon reconnection, the SUDO rules will be refreshed

Expected results:

Randomize the timer after the reconnection

Additional info:

Upstream ticket:
https://github.com/SSSD/sssd/issues/5609

Upstream PR:
https://github.com/SSSD/sssd/pull/5610

Pushed PR: https://github.com/SSSD/sssd/pull/5610

* `master`
    * ca47accad0b8e1dccf0618df7ce8352ccdbd4dea - sudo: add ldap_sudo_random_offset

Pushed PR: https://github.com/SSSD/sssd/pull/5670

* `master`
    * a3cb981204b22a117cf3edbcdf1205218200da58 - sudo: disable ldap_sudo_random_offset by default

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-2021:4435