Version: 8b12ef5
server-del command does not allow me to remove last DNS server from the topology and --force does not help. On the other hand the same works with ipa-replica-manage if --force option is used.
# ipa server-del vm-046.abc.idm.lab.eng.brq.redhat.com Removing vm-046.abc.idm.lab.eng.brq.redhat.com from replication topology, please wait... ipa: ERROR: Server removal aborted: Deleting this server will leave your installation without a DNS.. # ipa server-del vm-046.abc.idm.lab.eng.brq.redhat.com --force True Removing vm-046.abc.idm.lab.eng.brq.redhat.com from replication topology, please wait... ipa: ERROR: Server removal aborted: Deleting this server will leave your installation without a DNS.. # ipa-replica-manage del vm-046.abc.idm.lab.eng.brq.redhat.com --force WARNING: yacc table file version is out of date ipa: INFO: Skipping replication agreement deletion check for suffix 'domain' ipa: INFO: Skipping replication agreement deletion check for suffix 'ca' ipa: WARNING: Ignoring topology connectivity errors. ipa: WARNING: Deleting this server will leave your installation without a DNS. ipa: WARNING: Ignoring these warnings and proceeding with removal ipa: WARNING: Failed to cleanup vm-046.abc.idm.lab.eng.brq.redhat.com DNS entries: abc.idm.lab.eng.brq.redhat.com.: DNS zone not found ipa: WARNING: You may need to manually remove them from the tree ---------------------------------------------------------- Deleted IPA server "vm-046.abc.idm.lab.eng.brq.redhat.com" ----------------------------------------------------------
BTW it is quite weird that server-del's option --force requires an boolean argument. Do we still have time to fix this to behave the same way as all other --force options?
My bad. I was told that difference in --force's behavior between ipa-replica-install and ipa-replica-manage is intentional.
Metadata Update from @pspacek: - Issue assigned to mbabinsk - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Login to comment on this ticket.