Learn more about these different git repos.
Other Git URLs
Similar to ticket #2229 that called for SSSD to start with bad or absent sssd.conf this RFE calls for SSSD to start with bad or corrupt cache. IMO we should set the cache aside if we can't start with it and start with an empty cache. A thorough design would be required to make sure we cover all the cases.
Fields changed
keywords: => localusers milestone: NEEDS_TRIAGE => SSSD 1.13 beta rhbz: => todo
mark: => 1
Makes sense to copy the cache on broken update, but not required for normal SSSD operation.
priority: major => minor
Internal only change as part of the sysdb refactoring.
rhbz: todo => 0
The sysdb refactoring came too late for 1.13 and this ticket is more-or-less dependant on that effort.
Moving to the milestone where sysdb name attribute refactoring is.
milestone: SSSD 1.13 beta => SSSD 1.14 beta sensitive: => 0
This could come handy if we support the async ldb mode. But I suspect this won't happen in 1.14 either.
milestone: SSSD 1.14 beta => SSSD 1.14 backlog
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 @dpal: - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1469400 (was: 0)
Issue linked to Bugzilla: Bug 1469400
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/3292
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.