Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionAneta Šteflová Petrová
2015-05-07 09:04:21 UTC
Description of problem:
When I attempt to install a replica on a system where a replica is already installed, I get a warning that an IPA client is configured and that I have to uninstall it using "ipa-client-install --uninstall". However, what I really need to do is to run "ipa-server-install --uninstall":
[root@vm-077 ~]# ipa-replica-install /var/lib/ipa/replica-info-vm-077.abc.idm.lab.eng.brq.redhat.com.gpg --setup-dns --forwarder 10.38.5.26
IPA client is already configured on this system.
Please uninstall it first before configuring the replica, using 'ipa-client-install --uninstall'.
[root@vm-077 ~]# ipa-client-install --uninstall
IPA client is configured as a part of IPA server on this system.
Refer to ipa-server-install for uninstallation.
How reproducible:
Always
Steps to Reproduce:
1. Install a replica
2. Forget that you have already done it and run ipa-replica-install again
Actual results:
IPA advises to uninstall the client using "ipa-client-install --uninstall".
Expected results:
IPA should tell the user to uninstall the replica.
(Alternatively, it could advise to run "ipa-replica-manage del" first on the initial master and then uninstall the replica.)
Verified on RHEL73 using ipa-server-4.4.0-11.el7.x86_64
IPA doesnot advise to uninstall the client using "ipa-client-install --uninstall" instead it asks to uninstall ipa-server.
[root@ipareplica1 vagrant]# ipa-replica-install
ipa.ipapython.install.cli.install_tool(Replica): ERROR IPA server is already configured on this system.
If you want to reinstall the IPA server, please uninstall it first using 'ipa-server-install --uninstall'.
ipa.ipapython.install.cli.install_tool(Replica): ERROR The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information
[root@replica ~]# /usr/sbin/ipa-server-install --uninstall
This is a NON REVERSIBLE operation and will delete all data and configuration!
Are you sure you want to continue with the uninstall procedure? [no]: yes
Replication agreements with the following IPA masters found:
master.test-relm.test. Removing any replication agreements before uninstalling the server is strongly recommended. You can remove replication agreements by running the following command on any other IPA master:
$ ipa-replica-manage del replica.test-relm.test
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.
https://rhn.redhat.com/errata/RHBA-2016-2404.html