#48957 set proper update status to replication agreement in case of failure
Closed: wontfix None Opened 6 years ago by lkrispen.

The replication agreement contains a last update status field, which can be read by ldapsearch.
Unfortunately, if send_updates() returns a fatal error, the update status is always set to:

agmt_set_last_update_status(prp->agmt, -1, 0, "Incremental update has failed and requires administrator action");

but send_updates() has 13 different reasons to return UPDATE_FATAL_ERROR and logs more info to the error log, this could be propagated to the caller or directly set to the agreement

This would be great for troubleshooting!

1e44c1f..cdf4fb4 master -> master
commit cdf4fb4
Author: Mark Reynolds mreynolds@redhat.com
Date: Fri Aug 26 15:04:02 2016 -0400

590799f..32ee33b master -> master
commit 32ee33b
Author: Mark Reynolds mreynolds@redhat.com
Date: Thu Sep 1 12:54:08 2016 -0400

4d60ed2..cf5683a 389-ds-base-1.3.5 -> 389-ds-base-1.3.5
commit cf5683a

Need to fix the description of last_update_status? It says "Format = numeric code <space> textual description", which is not the case anymore.

Metadata Update from @nhosoi:
- Issue assigned to mreynolds
- Issue set to the milestone:

5 years ago

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

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: Fixed)

2 years ago

Login to comment on this ticket.