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.

Description of problem:
When a master server and replica are installed, ipa-replica-manage list will list the 2 servers in the topology. But when replica is uninstalled, it is still listed. This can lead to lost time (possibly, not proven) or other unwanted issues when master attempts to replicate its data to rest of the servers, and cannot reach this uninstalled replica

If a ipa-replica-manage del is done before uninstalling, this replica will not be listed. 

Seeing this behaviour in ipa-csreplica-manage as well.

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

How reproducible:
always

Steps to Reproduce:
1. install master, replica
2. ipa-replica-manage list - will list both servers
3. uninstall replica
4. ipa-replica-manage list
  
Actual results:
will list both servers

Expected results:
should list only master

Additional info:

Rob, could we just remove replication agreements when ipa-server-install --uninstall is run? It seems that an obligation to run "ipa-replica-manage del" just confuses users.

This will require one be authenticated in order to uninstall (either via GSSAPI with right credentials or with DM password). I've resisted this in the past, perhaps we should bring it up on the public devel list for discussion.

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/2163

`ipa-replica-manage del` step was missing, see

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/removing-replica.html

Given the FreeIPA behaves as designed, closing this ticket.