there have been cases where administrators didn't follow the recommended procedure of replica uninstallation: 1. call ipa-replica-manage del replica-fqdn 2. call ipa-server-install --uninstall
ipa-server-install --uninstall warns that the administrator has to do the first step with Replication agreements with the following IPA masters found: %s. 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.
This warning could be easily skipped by writing simple "yes" and there is no obstruction if it's run in unattended mode.
step #2 also doesn't check if the uninstallation will break replication topology and disconnect other replicas. Which may lead to replication or other issues.
Uninstallation if step #1 didn't happen is not valid. Uninstallation should proceed only if the server don't know that ipa-replica-manage del was ran (from whatever reason, e.g. broken replication).
ipa-replica-manage del
Proposal is: Make harder to skip the warning in step #2. E.g with:
--remove-broken-server
if topology is managed, we can uninstall the replica AND update the topology as well
I think this is implemented in topology changes. I propose to close it.
Replying to [comment:2 simo]:
I think this is implemented in topology changes. I propose to close it. I agree, we have these checks implemented by #5409. AFAIK there were no plans to implement them for domain level 0.
See #5409
Metadata Update from @pvoborni: - Issue assigned to someone - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Login to comment on this ticket.