#3060 better debugging of timestamp cache modifications
Closed: Fixed None Opened 6 years ago by jhrozek.

When debugging the cache writes, it would be beneficial to add some more debug messages to sssd. These might include:
- a message whether only the timestamp cache changed or the sysdb did
- a message saying /why/ the sysdb or timestamp cache changed. What attribute triggerred a cache write
- we might even want to dump the whole ldb LDIF with a special debug level

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14.0

1.14.0 should be released no later than Wednesday next week, this ticket should not block the 1.14.0 release.

milestone: SSSD 1.14.0 => SSSD 1.14.1

Fields changed

owner: somebody => pcech

Fields changed

rhbz: => 0

Fields changed

status: new => assigned

We need to release 1.14.1 soon, therefore moving to 1.14.2.

milestone: SSSD 1.14.1 => SSSD 1.14.2

Fields changed

patch: 0 => 1

Moving tickets that didn't make it into the 1.14.2 release into the next point release.

milestone: SSSD 1.14.2 => SSSD 1.14.3

master and 1.14 diverged meanwhile.
Therefore pushed just into master.
If you think it should be also pushed to 1.14.3
then please reopen ticket and ask for backport.


milestone: SSSD 1.14.3 => SSSD 1.15 Alpha
resolution: => fixed
status: assigned => closed
version: 1.13.3 => master

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

5 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/4093

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.

Login to comment on this ticket.