#2132 ipa-replica-manage list doesn't always match cn=mapping tree
Closed: Fixed None Opened 12 years ago by dpal.

https://bugzilla.redhat.com/show_bug.cgi?id=755094

Description of problem:
Have a master with 2 replicas. Topology master -> replica1, master -> replica2
Used:
ldapsearch -x -h `hostname` -p 389 -D "cn=Directory Manager" -w Secret123 -b
"cn=mapping tree,cn=config"
to check replication agreements on each of the machines, and they all look
correct, and as expected. Will attach here.
But doing a ipa-replica-manage list shows different output:
[root@dell-pe1950-02 ~]# ipa-replica-manage list
dell-pe1950-02.testrelm: master
dell-pe1950-03.testrelm: master
[root@dell-pe1950-02 ~]# ipa-replica-manage list -p Secret123
dell-pe1950-02.testrelm: master
dell-pe1950-03.testrelm: master
[root@dell-pe1950-02 ~]# ipa-replica-manage list -p Secret123 `hostname`
dell-pe1950-03.testrelm: replica
ibm-ls22-03.testrelm: replica


For reference:
master: 10.34.35.52 ; replica1: 10.34.35.54; replica2: 10.34.54.39

Version-Release number of selected component (if applicable):
ipa-server-2.1.3-9.el6.i686

How reproducible:
always

Steps to Reproduce:
1. install master and 2 replicas
2.ipa-replica-manage list
3.ipa-replica-manage list -p Secret123
4.ipa-replica-manage list -p Secret123 `hostname`

Actual results:
lists are not same always

Expected results:
list to be same

Additional info:

Ondra, please check this one.

There was a problem in directory server. Current version of 389 DS - 389-ds-base-1.2.10.rc1 - seems to be fixing it.

In DS it is BZ 788140.

Thanks for investigation. Closing this ticket.

Metadata Update from @dpal:
- Issue assigned to ohamada
- Issue set to the milestone: FreeIPA 2.2 Core Effort - 2012/02

7 years ago

Login to comment on this ticket.

Metadata