I keep getting the strange failures during installation of IPA master:
ipa : CRITICAL failed to create ds instance Command ''/usr/sbin/setup-ds.pl' '--silent' '--logfile' '-' '-f' '/tmp/tmpzxaPeO'' returned non-zero exit status 1 ipa : CRITICAL Failed to restart the directory server (Timeout exceeded). See the installation log for details. ipa.ipapython.install.cli.install_tool(Server): ERROR Timeout exceeded ipa.ipapython.install.cli.install_tool(Server): ERROR The ipa-server-install command failed. See /var/log/ipaserver-install.log for more information
attachment ipaserver-install.log
Oleg, how reproducible it is (e.g. in percentage)?
I see in a log:
[Setup] Info Error: the server already exists at '/etc/dirsrv/slapd-JUSTFOR-TEST' 269 Please remove it first if you really want to recreate it, 270 or use a different ServerIdentifier to create another instance. 271 Error: the server already exists at '/etc/dirsrv/slapd-JUSTFOR-TEST' 272 Please remove it first if you really want to recreate it, 273 or use a different ServerIdentifier to create another instance. 274 [15/12/09:14:52:18] - [Setup] Fatal Error: Could not create directory server instance 'JUSTFOR-TEST'. 275 Error: Could not create directory server instance 'JUSTFOR-TEST'. 276 [15/12/09:14:52:18] - [Setup] Fatal Exiting . . .
Does the machine contains DS from old installation? Was ipa-server properly uninstalled before re-installation?
The issue was quite frequently seen in VM's in ABC lab: something like 30% - 40% of cases. Generally, it was observed when the ipa-server is installed after it was previously removed with standard method {{{ipa-server-install --uninstall}}}. I recently switched to using libvirt-powered VMs and the issue is not observed any more. So it could be something specific to ABC setup
It is looking like the previous 'ipa-server-install --uninstall' did not fully uninstalled the directory. When the problem occurs, would you also grab the /var/log/ipaserver-uninstall.log and the DS logs /var/log/dirsrv/slapd/
closing based on comment 2. Please reopen if it happens again and more info is available.
Metadata Update from @ofayans: - Issue assigned to someone - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Log in to comment on this ticket.