389-ds-base

#76 Replication ignores INSUFFICIENT_ACCESS errors
Closed: wontfix Opened by mkosek.

Closed: wontfix
Reopen Issue

https://bugzilla.redhat.com/show_bug.cgi?id=652483

If a plugin (mistakenly) returns insufficient access to a replication
operation, the result id ignored and the entry is lost forever in the replica
causing the 2 trees to diverge.
The replication engine should not ignore such an error (a configuration error
anyway) and instead report it as a replication problem so that it can be
hopefully fixed and replication the server can retry to replicate the entry.

batch update to FUTURE milestone

set default ticket origin to Community

Added initial screened field value.

This bug still is in the plug-in?

Works for me. Replication does retry to sen the update.

Metadata Update from @rmeggins:
- Issue set to the milestone: 1.3.5 eval

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/76

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Invalid)
Metadata
None
None
None
None
High
Needs Review
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.