#2760 sss_cache & negative cache - improve behaviour
Closed: cloned-to-github 3 years ago by pbrezina. Opened 8 years ago by ondrejv2.

When using sss_cache against some item which is in negative cache (i.e. not found), it does not work.
I would expect negative cache is cleared, sssd attempts to go online and get current result.


Fields changed

owner: somebody => pcech

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14 beta

Nice to have for 1.14..

milestone: SSSD 1.14 beta => SSSD 1.14 backlog

Fields changed

rhbz: => todo

Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.

milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)

Metadata Update from @ondrejv2:
- Issue assigned to pcech
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Future milestone

4 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/3801

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)

3 years ago

Login to comment on this ticket.

Metadata