#782 Fatal errors updating the cache should delete the entry
Closed: wontfix 3 years ago by pbrezina. Opened 13 years ago by sgallagh.

Currently, if SSSD experiences a fatal error while trying to save an entry to the sysdb, we return an error and mark the DP offline. As a result, we will then return any value in the sysdb that was previously available to the client.

This is probably bad behavior and we should attempt to remove any potentially-corrupt entries from the cache if we fail to update it.


Triage suggested to defer.
The solution should be to try to delete the entry only if we detect that this entry is really corrupt and deleting it would help.

milestone: NEEDS_TRIAGE => SSSD Deferred

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- Issue set to the milestone: SSSD Patches welcome

7 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

3 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/1824

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.

Metadata