See also ticket #415.
Replying to [comment:15 rmeggins]:
We can do these later: As Rich pointed out, there are more cases this patch does not fix: e.g, a pseudo user in the sync scope but not being sync'ed would be deleted, which should not be. To learn if an entry is in the scope is sync'ed or not, map_entry_dn_inbound would provide us the answer, which requires an entire entry. I.e., we need to search all the members to determine we could delete it or not. Would it be acceptable?
We can do these later:
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1206306
Not a customer issue.
No requests from customers/community.
Per triage, set to closed/wontfix.
Metadata Update from @nhosoi: - Issue set to the milestone: 1.4 backlog
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/801
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.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Invalid)
Login to comment on this ticket.