#3272 timestamp entries are not added if the persistent cache entry exists but the timestamp entry does not

Created 8 months ago by jhrozek
Modified 6 months ago

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

6 months ago

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

Login to comment on this ticket.

defect

SSSD

1.14.2

0

0

todo

0

0

0

0

cancel