The ipa-replica-install and ipa-client-install use different way of determining whether client has been setup. This can lead to interesting situations, such as:
$ sudo ipa-replica-install ipa.ipapython.install.cli.install_tool(Replica): ERROR IPA client is not configured on this system. You must use a replica file or join the system using 'ipa-client-install'. ipa.ipapython.install.cli.install_tool(Replica): ERROR The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information $ sudo ipa-client-install IPA client is already configured on this system. If you want to reinstall the IPA client, uninstall it first using 'ipa-client-install --uninstall'.
How is this situation created?
Isn't it sort of dup of #5410?
Not a blocker for 4.3 release.
I cannot reproduce it, can you provide steps to reproduce?
I tried:
# installed replica [root@vm-058-138 ~]# ipa-client-install IPA client is already configured on this system. If you want to reinstall the IPA client, uninstall it first using 'ipa-client-install --uninstall'. [root@vm-058-138 ~]# 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 # only client installed [root@vm-058-138 ~]# ipa-client-install IPA client is already configured on this system. If you want to reinstall the IPA client, uninstall it first using 'ipa-client-install --uninstall'.
I do not think this is worth to fix, check if ipa-client is installed is and must be different on server and on standalone client.
triage results: close
Metadata Update from @tbabej: - Issue assigned to mbasti - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Login to comment on this ticket.