SSSD / sssd

#3128 throw away the timestamp cache if re-initializing the persistent cache
Closed: Fixed Opened by jhrozek.

Closed: Fixed
Reopen Issue

Many users are used to rm -f /var/lib/sss/db/cache_$. When they do that, but leave the timestamp cache around, sssd might not detect changes to the entry and only keep updating the timestamp cache. We should throw away the timestamp cache contents if we're re-initializing the persistent cache.

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1366470 (Red Hat Enterprise Linux 7)

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1366470 1366470]

Fields changed

owner: somebody => fidencio

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14.2
patch: 0 => 1
  • master:
    • b6d1cd5eaab4c7c73df8ee041944ec05630a9630
    • 9023bf51de6c84337af024388f1860ac1051924c

resolution: => fixed
status: new => closed

Additional patch
master:

  • 975d0b67a40847265523d195438bf4753d18ff1c

Metadata Update from @jhrozek:
- Issue assigned to fidencio
- Issue set to the milestone: SSSD 1.14.2

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4161

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.
Metadata
None
None
None
Normal
defect
SSSD
1.14.0
0
0
1
https://bugzilla.redhat.com/show_bug.cgi?id=1366470
0
0
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.