Uninstaller relies on ipactl stop to stop all services before unconfiguring them. But when installation failed, ipactl has no correct information and thus not all services are stopped and may cause issues with next installation run (see example with named-pkcs11)
Steps to reproduce: 1. put 'assert False' to main method of ipa-client-install (simulation of failed ipa-client-install) 1. ipa-server-install --setup dns 1. ipa-server-install --uninstall 1. systemctl status named-pkcs11 (is running, but it should be stopped) 1. ipa-server-install --setup-dns (same params as first run, will report zone already exists error)
uninstall log (named and other services are not stopped)
2016-05-06T09:07:17Z DEBUG Starting external process 2016-05-06T09:07:17Z DEBUG args=/usr/sbin/ipactl stop 2016-05-06T09:07:22Z DEBUG Process finished, return code=0 2016-05-06T09:07:22Z DEBUG stdout=Stopping pki-tomcatd Service Stopping krb5kdc Service Stopping Directory Service 2016-05-06T09:07:22Z DEBUG stderr=ipa: INFO: The ipactl command was successful
Proposed solution: explicitly stop all services during unconfiguration, uninstaller should not rely on ipactl stop. This is not the fist uninstall bug caused by ipactl, we should get rid of it in uninstall.
Metadata Update from @mbasti: - Issue assigned to someone - Issue set to the milestone: FreeIPA 4.5 backlog
Login to comment on this ticket.