389-ds-base

#50896 dsconf healthcheck for replication agreements is not displaying the correct agmt name
Closed: wontfix by mreynolds. Opened by mreynolds.

Closed: wontfix
Reopen Issue

Issue Description

dsconf healthcheck is not displaying the agreement name in the lint report. It used to do it so this is a regression,:

[1] DS Lint Error: DSREPLLE0001

Severity: HIGH
Affects:
-- Replication
-- Agreement

Details:

The replication agreement (exampleagreement) under "dc=example,dc=com" is not in synchronization.

Resolution:

You may need to reinitialize this replication agreement. Please check the errors
log for more information. If you do need to reinitialize the agreement you can do so
using dsconf. Here is an example:

# dsconf slapd-inst1 repl-agmt init "exampleagreement" --suffix dc=example,dc=com

This does work correctly, closing as invalid

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: invalid
- Issue status updated to: Closed (was: Open)

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

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
None
None
None
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.