RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 755094 - ipa-replica-manage list doesn't always match cn=mapping tree
Summary: ipa-replica-manage list doesn't always match cn=mapping tree
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On: 788140
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-18 20:05 UTC by Namita Soman
Modified: 2012-06-20 13:17 UTC (History)
5 users (show)

Fixed In Version: ipa-2.2.0-1.el6
Doc Type: Bug Fix
Doc Text:
No documentation needed.
Clone Of:
Environment:
Last Closed: 2012-06-20 13:17:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
cn=mapping tree (9.06 KB, text/plain)
2011-11-18 20:07 UTC, Namita Soman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0819 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2012-06-19 20:34:17 UTC

Description Namita Soman 2011-11-18 20:05:16 UTC
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:

Comment 1 Namita Soman 2011-11-18 20:07:16 UTC
Created attachment 534486 [details]
cn=mapping tree

MASTER (10.34.35.52 dell-pe1950-02.testrelm)
REPLICA1 (10.34.35.54 dell-pe1950-03.testrelm)
REPLICA2 (10.34.54.39 ibm-ls22-03.testrelm)

Comment 3 Dmitri Pal 2011-11-22 16:13:16 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/2132

Comment 4 Martin Kosek 2012-02-08 15:51:49 UTC
Ondrej Hamada found out that this issue is fixed by 389-ds-base-1.2.10.rc1 which was released for Fedora and epel6. I will link this BZ to Bug 788140 that Rich marked as the root cause of this bug.

Comment 6 Gowrishankar Rajaiyan 2012-03-08 07:01:31 UTC
Manual:
[root@primenova ~]# ipa-replica-manage list -p Secret123
goldbug.lab.eng.pnq.redhat.com: master
primenova.lab.eng.pnq.redhat.com: master

[root@primenova ~]# ipa-replica-manage list -p Secret123 goldbug.lab.eng.pnq.redhat.com
primenova.lab.eng.pnq.redhat.com: replica

[root@primenova ~]# ipa-replica-manage list -p Secret123 primenova.lab.eng.pnq.redhat.com
goldbug.lab.eng.pnq.redhat.com: replica
[root@primenova ~]# 


Automated:
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: Uninstalling replica
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
--8<--
:: [   LOG    ] :: verifies https://bugzilla.redhat.com/show_bug.cgi?id=755094
:: [   PASS   ] :: Running 'ipa-replica-manage list | grep "ipaqavmd.testrelm.com: master"'
:: [   PASS   ] :: Running 'ipa-replica-manage list | grep "ipaqavma.testrelm.com: master"'
:: [   PASS   ] :: Running 'ipa-replica-manage list -p Secret123 | grep "ipaqavmd.testrelm.com: master"'
:: [   PASS   ] :: Running 'ipa-replica-manage list -p Secret123 | grep "ipaqavma.testrelm.com: master"'
:: [   PASS   ] :: Running 'ipa-replica-manage list -p Secret123 ipaqavmd.testrelm.com | grep "ipaqavma.testrelm.com: replica"'
:: [   PASS   ] :: Running 'ipa-replica-manage list -p Secret123 ipaqavma.testrelm.com | grep "ipaqavmd.testrelm.com: replica"'


Verified:
ipa-server-2.2.0-3.el6.x86_64
389-ds-base-1.2.10.2-2.el6.x86_64

Comment 8 Martin Kosek 2012-04-19 12:31:54 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No documentation needed.

Comment 10 errata-xmlrpc 2012-06-20 13:17:46 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0819.html


Note You need to log in before you can comment on or make changes to this bug.