https://bugzilla.redhat.com/show_bug.cgi?id=720486
Description of problem: When creating a new replica agreement, replica attributes are not correctly set, thus, preventing data replication. Version-Release number of selected component (if applicable): RHDS 8.2 How reproducible: Easily Steps to Reproduce: 1. Set up a multi-master environment 2. Remove your replica agreement rule 3. Create a new fractional replication 4. Include all attributes 5. Change a user password in the master server 6. Try to log in using the other master server, using the new password Actual results: Authentication won't proceed Expected results: Replication should have happened and authenticate the new password. Additional info: As a work around, if you *remove* an attribute, then the replica agreement will be correctly created. See attached files.
batch move to milestone future
set default ticket origin to Community
Added initial screened field value.
Per weekly triage, closing this ticket as WONTFIX.
Metadata Update from @nhosoi: - Issue set to the milestone: FUTURE
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/188
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.