Description of problem:
sss_cache is may be used to force invalidation of cached data and thus forcing up-to-date data into SSSD cache. However, this approach has own performance limitations (with sshd or other long-running processes leaving open FDs to deleted old versions of the cache).
Thanks to the limitations, sss_cache is typically not recommended as a tool that is run periodically (for example in a cron), but mostly for troubleshooting. Users should rather should define proper timeout for given LDAP object, to balance amount of LDAP traffic and expected freshness of the information (like ldap_sudo_smart_refresh_interval which is set to 15 minutes by default).
The intent for this tool and limitations should be spelled out in man pages (or documentation), so that users are not using it unknowingly in improper way.
Version-Release number of selected component (if applicable):
sssd-2.2.0-19.el8_1.1
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