While enabling replication, we can create a custom 'replication manager'. If we try to set it to something invalid - replication still will be enabled and the invalid DN will exist in the table. It will be impossible to remove it and it stays in the table even after UI reload (F5).
cn=replication manager,cn=configinvalid
Replication Managers
F5
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.1
Metadata Update from @mreynolds: - Issue priority set to: normal
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.4 (was: 1.4.1)
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/3858
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 - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.