Description of problem:
ipa-client-install configures ipa on clients. It creates /etc/ipa/default.conf with the proper configuration.
It populates "server" field, which according to man default.conf is deprecated.
This came up because another tool I use was parsing that file and was expecting "host" not "server", which according to the man page is the preferred value.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2. grep '\(host\|server\)' /etc/ipa/default.conf
server = ipaserver.kbnet.redhat.com
host = ipaserver.kbnet.redhat.com
Thanks for report! I see exactly the same issue was just reported in upstream FreeIPA: https://fedorahosted.org/freeipa/ticket/4481. I will link those 2 together.
I briefly checked in the code, we do not use api.env.server except one place, we probably copy it to, widely used, api.env.host variable. This needs to be investigated in the upstream ticket.
Thank you Martin,
Sorry that this was a double post. I didn't know Nalin had posted this in freeipa.
This is related as, the "other tool" is written by Nalin.
- host option description in man page was fixed - it is the local hostname. The option is now also generated by client installer by default
- server option was "un-deprecated" in the client default.conf - this specifies the server that the client enrolled with.
Verified on ipa-client-4.1.0-13.el7.x86_64:
[root@qe-blade-05 ~]# ipa-client-install
WARNING: ntpd time&date synchronization service will not be configured as
conflicting service (chronyd) is enabled
Use --force-ntpd option to disable it and force configuration of ntpd
Discovery was successful!
DNS Domain: testrelm.test
IPA Server: hp-dl385gen8-01.testrelm.test
Continue to configure the system with these values? [no]: y
Client configuration complete.
[root@qe-blade-05 ~]# grep '\(host\|server\)' /etc/ipa/default.conf
server = hp-dl385gen8-01.testrelm.test
host = qe-blade-05.testrelm.test
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.