Fatal errors updating the cache should delete the entry

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/782

• Created at 2011-01-21 21:38:48 by sgallagh
• Closed at 2020-03-24 14:22:49 as wontfix
• Assigned to nobody

---

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.

Comments

---

Comment from dpal at 2011-01-27 15:11:39

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

---

Comment from dpal at 2012-01-19 03:20:38

Fields changed

rhbz: => 0

---

Comment from sgallagh at 2017-02-24 15:06:50

Metadata Update from @sgallagh:

• Issue set to the milestone: SSSD Patches welcome

---

Comment from pbrezina at 2020-03-24 14:22:48

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.

---

Comment from pbrezina at 2020-03-24 14:22:49

Metadata Update from @pbrezina:

• Issue close_status updated to: wontfix
• Issue status updated to: Closed (was: Open)