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 824492 - Cannot re-connect replica to previously disconnected master
Summary: Cannot re-connect replica to previously disconnected master
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-23 15:22 UTC by Dmitri Pal
Modified: 2015-05-19 13:49 UTC (History)
4 users (show)

Fixed In Version: ipa-3.0.0-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-21 09:13:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 826677 0 medium CLOSED IPA cannot remove disconnected replica data to reconnect 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2013:0528 0 normal SHIPPED_LIVE Low: ipa security, bug fix and enhancement update 2013-02-21 08:22:21 UTC

Internal Links: 826677

Description Dmitri Pal 2012-05-23 15:22:08 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/2759


{{{
vm-046# ipa-replica-manage disconnect vm-091.$domain
Deleted replication agreement from vm-046.$domain to vm-091.$domain

vm-046# ipa-replica-manage connect vm-091.$domain
You cannot connect to a previously deleted master
}}}

I started with this topology, with IPA 2.2 installed everywhere:

{{{
     106
   /  |
089  091
   \  |
     046
}}}

The check for this was added for https://fedorahosted.org/freeipa/ticket/2126, but the ticket only mentions ipa-replica-manage del, not disconnect.
Comment 1 RHEL Program Management 2012-07-10 07:12:56 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 2 RHEL Program Management 2012-07-10 23:27:53 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 3 Martin Kosek 2012-09-18 07:07:06 UTC 
Upstream ticket was closed as this issue should be fixed in 32c1aa45b3d41e15adb2ca8f8713e774046bc340 as part of https://fedorahosted.org/freeipa/ticket/2925.

This bug is also related to Bug 826677, where additional checks have been added to prevent replica orphaning.
Comment 7 Scott Poore 2012-11-27 17:46:29 UTC 
Verified.

Version ::

ipa-server-3.0.0-8.el6.x86_64

Manual Test Results ::

Confirming environment setup:

[root@rhel6-1 ~]# ipa-replica-manage -p $ADMINPW list
rhel6-1.testrelm.com: master
rhel6-2.testrelm.com: master
rhel6-3.testrelm.com: master
rhel6-4.testrelm.com: master

[root@rhel6-1 ~]# ipa-replica-manage -p $ADMINPW list rhel6-1.testrelm.com
rhel6-2.testrelm.com: replica
rhel6-4.testrelm.com: replica

[root@rhel6-1 ~]# ipa-replica-manage -p $ADMINPW list rhel6-2.testrelm.com
rhel6-1.testrelm.com: replica
rhel6-3.testrelm.com: replica

[root@rhel6-1 ~]# ipa-replica-manage -p $ADMINPW list rhel6-3.testrelm.com
rhel6-2.testrelm.com: replica
rhel6-4.testrelm.com: replica

[root@rhel6-1 ~]# ipa-replica-manage -p $ADMINPW list rhel6-4.testrelm.com
rhel6-1.testrelm.com: replica
rhel6-3.testrelm.com: replica

Testing:

[root@rhel6-2 ~]# ipa-replica-manage disconnect rhel6-3.testrelm.com
ipa: INFO: Setting agreement cn=meTorhel6-2.testrelm.com,cn=replica,cn=dc\=testrelm\,dc\=com,cn=mapping tree,cn=config schedule to 2358-2359 0 to force synch
ipa: INFO: Deleting schedule 2358-2359 0 from agreement cn=meTorhel6-2.testrelm.com,cn=replica,cn=dc\=testrelm\,dc\=com,cn=mapping tree,cn=config
ipa: INFO: Replication Update in progress: FALSE: status: 0 Replica acquired successfully: Incremental update succeeded: start: 0: end: 0
Deleted replication agreement from 'rhel6-2.testrelm.com' to 'rhel6-3.testrelm.com'

[root@rhel6-2 ~]# ipa-replica-manage connect rhel6-3.testrelm.com
ipa: INFO: Getting ldap service principals for conversion: (krbprincipalname=ldap/rhel6-2.testrelm.com) and (krbprincipalname=ldap/rhel6-3.testrelm.com)
Connected 'rhel6-2.testrelm.com' to 'rhel6-3.testrelm.com'

[root@rhel6-2 ~]# ipa-replica-manage list rhel6-2.testrelm.com
rhel6-1.testrelm.com: replica
rhel6-3.testrelm.com: replica
Comment 9 errata-xmlrpc 2013-02-21 09:13:27 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/RHSA-2013-0528.html
Note You need to log in before you can comment on or make changes to this bug.