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 757798 - DOC: Missing replica-demotion
Summary: DOC: Missing replica-demotion
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Identity_Management_Guide
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 6.3
Assignee: Deon Ballard
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-28 17:51 UTC by Sigbjorn Lie
Modified: 2012-06-21 23:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-21 23:16:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sigbjorn Lie 2011-11-28 17:51:07 UTC
On 11/28/2011 03:11 PM, Simo Sorce wrote:
> On Sun, 2011-11-27 at 18:53 +0100, Sigbjorn Lie wrote:
>> Perhaps an opertunity for improvements here? My suggestions:
>>
>> * First off, add to the documentation to remove the replica on
>> another 
>> IPA server before uninstalling the IPA replica?
>
> We should probably do this, can you open a doc bug ?
>

Comment 1 Sigbjorn Lie 2011-11-28 17:54:14 UTC
In addition:

> * Where did the CA instance go? I see nothing in the documentation
> about 
> this, but I found a ipa-ca-install command.

The CA component is always optional on replicas. You do not necessarily
want to have a CA replica in every single FreeIPA replica. Usually a few
CA instance (perhaps one or two per geography will suffice).

So you should either pass --setup-ca at ipa-replica-install time or call
ipa-ca-install later.

Comment 3 Rob Crittenden 2011-11-28 22:11:35 UTC
Deon, they will want to do something like:

On the replica to be removed, show all replication agreements:
# ipa-replica-manage list
Directory Manager password: 

ipa.example.com: master
replica.example.com: master

For each server in the list (other than our own, of course):
# ipa-replica-manage del ipa.example.com

Now you can uninstall the replica:
# ipa-server-install --uninstall -U

On a remaining server clean up all references to the old replica:
# ipa host-del replica.example.com

Comment 7 Deon Ballard 2012-06-21 23:16:43 UTC
Closing.


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