When the installer fails during the initial DNS check and aborts installation, the information in log is not descriptive of the problem.
2016-03-24T21:01:51Z DEBUG Logging to /var/log/ipaserver-install.log 2016-03-24T21:01:51Z INFO Checking DNS domain dom-086.idm.lab.eng.brq.redhat.com, please wait ... 2016-03-24T21:01:51Z DEBUG File "/usr/lib/python2.7/site-packages/ipapython/admintool.py", line 171, in execute return_value = self.run() File "/usr/lib/python2.7/site-packages/ipapython/install/cli.py", line 309, in run self.option_parser.error("{0}: {1}".format(desc, e)) File "/usr/lib64/python2.7/optparse.py", line 1584, in error self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg)) File "/usr/lib64/python2.7/optparse.py", line 1574, in exit sys.exit(status) 2016-03-24T21:01:51Z DEBUG The ipa-server-install command failed, exception: SystemExit: 2 2016-03-24T21:01:51Z ERROR The ipa-server-install command failed. See /var/log/ipaserver-install.log for more information
The particular error message in this case was:
ipa-server-install: error: option --domain: DNS zone dom-086.example.com. already exists in DNS and is handled by server(s): vm-086.example.com.
Oh yes, we should log complete DNS message into the debug log.
BTW the ideal way would be to log complete DNS message.
4.3.2 was released, moving to 4.3.3
Metadata Update from @mkubik: - Issue assigned to mbasti - Issue set to the milestone: FreeIPA 4.3.3
4.3.x EOL
Metadata Update from @mbasti: - Issue close_status updated to: None - Issue set to the milestone: FreeIPA 4.4.5 (was: FreeIPA 4.3.3)
Metadata Update from @mbasti: - Assignee reset
This was fixed in 4.4.0 as a side-effect of another fix. Testing for my domain:
Checking DNS domain redacted.com., please wait ... DNS zone redacted.com. already exists in DNS and is handled by server(s): zippy.redacted.com.
master: 0c75df4
Metadata Update from @rcritten: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.