Learn more about these different git repos.
Other Git URLs
When a DS replica is reinitialized the USNs are reset to 0 for all imported entries, and the counter is also reset to 0. When connecting to the same server therefore it is not sufficient to check the name we also need to verify that the highest USN value of the server is not lower than what we have recorded. If so we need to reset the enumeration counters just like if we were connecting to a new server.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.6.0
owner: somebody => jzeleny upgrade: => 0
status: new => assigned
Fixed in: 743475e
patch: => 0 resolution: => fixed status: assigned => closed
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=785877
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=785877 785877]
Reopening this bug. It appears to be broken on 1.8.0. See https://bugzilla.redhat.com/show_bug.cgi?id=785877
blockedby: => blocking: => feature_milestone: => milestone: SSSD 1.6.0 => NEEDS_TRIAGE resolution: fixed => status: closed => reopened
milestone: NEEDS_TRIAGE => SSSD 1.10.0 priority: critical => blocker
As it was described in the BZ, the issue now is a bit different than the original request stated. Now the SSSD correctly detects that remote DS has be re-initialized but it doesn't delete the old data, it just fetches a whole bunch of new data. However that's a problem of enumeration in general, it doesn't delete records that are in the cache but no longer on the server.
The best solution in context of this ticket is to delete all records of given type with entryUSN higher than lastUSN retrieved from the server. More generic solution would be to check for all entries that have expired as well.
milestone: SSSD 1.10.0 => SSSD 1.9.0
owner: jzeleny => pbrezina status: reopened => new
milestone: SSSD 1.9.0 => SSSD 1.9.0 RC1
patch: 0 => 1
Fixed in 41be4e3
proposed_priority: => Undefined resolution: => fixed status: new => closed
Metadata Update from @simo: - Issue assigned to pbrezina - Issue set to the milestone: SSSD 1.9.0 beta 7
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/1776
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.