ipa-client-install sets NIS domainname via starting fedora-domainname.service. However, when the service is already started or enabled, the NIS domainname is not set which would make SUDO not working:
ipa-client-install
fedora-domainname.service
# ipa-server-install ... # nisdomainname nisdomainname: Local domain name not set
See debugging:
# service fedora-domainname status Redirecting to /bin/systemctl status fedora-domainname.service fedora-domainname.service - Read and set NIS domainname from /etc/sysconfig/network Loaded: loaded (/usr/lib/systemd/system/fedora-domainname.service; enabled) Active: active (exited) since Thu 2014-06-19 17:12:20 CEST; 3 days ago Main PID: 8157 (code=exited, status=0/SUCCESS) # service fedora-domainname start Redirecting to /bin/systemctl start fedora-domainname.service # nisdomainname nisdomainname: Local domain name not set # service fedora-domainname restart Redirecting to /bin/systemctl restart fedora-domainname.service # nisdomainname idm.lab.eng.brq.redhat.com
Adding to list of tickets required for 4.0 release.
To clarify the issue, the problem resides not in nisdomainname not being set after ipa-server-install. The problem here is that nisdomain name is not loaded if the fedora-nisdomain service is already configured and started, since we only attempt to start the service, which will become no-op. Thus for reloading the nisdomain name for the current session without rebooting we need to restart it.
master:
Metadata Update from @mkosek: - Issue assigned to tbabej - Issue set to the milestone: FreeIPA 4.0 GA
Login to comment on this ticket.