Learn more about these different git repos.
Other Git URLs
SSSD should save last configuration it started with and compare the configuration it is about to use with the previous one. If the configuration is different then it should drill down and see if there are any changes that invalidate portions of the offline cache. If there are changes like this it should attempt to clean or repair the cache.
I suspect that there should be an exception. If we can't read the old configuration we should assume it is the first start after the wipe out or fresh install. I am not sure anything should be explicitly cleaned in this case. If we can't read the new one but can read old one then we should probably fall back to the old configuration and issue warning. We need to decide whether it makes sense to clean the cache in this case. If we can't read either we should fall back to the default config covered in the ticket #2229. A design page should probably drill down and cover all these cases.
Fields changed
type: defect => enhancement
milestone: NEEDS_TRIAGE => SSSD 1.13 beta
keywords: => localusers rhbz: => todo
mark: => 1
Supporting last-known-good configuration would be nice but not required for 1.13
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
Mass-moving tickets not planned for the 1.13 release to 1.14
milestone: SSSD 1.13 backlog => SSSD 1.14 beta
cc: => mzidek@redhat.com sensitive: => 0
Parts of this ticket might be solved by Michal's work in 1.14, but I'm quite certain not the cache invalidation part.
milestone: SSSD 1.14 beta => SSSD 1.15 beta
Metadata Update from @dpal: - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @thalman: - Custom field design_review reset (from 0) - Custom field mark adjusted to on (was: 1) - 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: Canditate to close
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)
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/3291
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.