#3272 timestamp entries are not added if the persistent cache entry exists but the timestamp entry does not
Closed: cloned-to-github 5 years ago by pbrezina. Opened 8 years ago by jhrozek.

The sysdb code that adds the timestamp entries tried to be smart in the sense that it tried to create the timestamp entry along when the persistent cache entry is created and then just update the timestamp entry when then persistent cache entry is updated.

This breaks when some persistent cache entry already exists, but no timestamp entry exists, because the timestamp code would just try to update an entry which would fail with LDB_NO_SUCH_OBJECT (or similar).

We should catch this error and recover by adding the timestamp entry even during update.


Fields changed

owner: somebody => pcech

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14.3

Fields changed

rhbz: => todo

Metadata Update from @jhrozek:
- Issue assigned to pcech
- Issue set to the milestone: SSSD 1.14.3

8 years ago

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/4305

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 Update from @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)

5 years ago

Log in to comment on this ticket.

Metadata