The customer has 6 IPA servers.Two replicas reported "unable to decode: {replica xxx}" after a third replica was re-installed.
The problem is reproducible on a build without the fix for #49463.
dn: cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config nsds50ruv: {replicageneration} 5a69ec4a000000010000 nsds50ruv: {replica 1 ldap://host:39001} 5a69ec70000000010000 5a69ee64000000010000 nsds50ruv: {replica 3 ldap://host:39003} 5a69eca7000200030000 5a69ee47000000030000 nsds50ruv: {replica 2 ldap://host:39002} 5a69eca6000000020000 5a69ee45000000020000 nsds50ruv: {replica 4} 5a69eddc000000040000 5a69eddc000000040000
This ticket is to evaluate if the bug is fixed or hidden by #49463
1.3.6
Metadata Update from @tbordaz: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1518247 - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @vashirov: - Issue close_status updated to: fixed - 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/2657
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: fixed)
Login to comment on this ticket.