Hide Forgot
Description of problem: ipa-client-install --domain=testrelm --realm=TESTRELM -p admin -w <xxx> --no-sssd installs the client. But it should check if nss_ldap package is available or if config files exist and not proceed with the join, if LDAP cannot be configured. we don't require the nss_ldap package because not using sssd is optional note: related bug 746276 Version-Release number of selected component (if applicable): ipa-client-2.1.3-8.el6.x86_64 How reproducible: always Steps to Reproduce: 1. With nss_ldap not installed, run cmd: ipa-client-install --domain=testrelm --realm=TESTRELM -p admin -w <xxx> --no-sssd Actual results: client is installed Expected results: message to indicate that nss_ldap pkg should be installed to allow --no-sssd option Additional info:
Upstream ticket: https://fedorahosted.org/freeipa/ticket/2063
Fixed upstream: master: 005b74d869ce240018985fd8abc752a5e200eb74
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No documentation needed.
Verified. Package nss_ldap or nss-pam-ldap is required when option --no-sssd is used with ipa-client-install. ipa-client version: =================== [root@ipa63client1 ~]# rpm -q ipa-client ipa-client-2.2.0-12.el6.x86_64 [root@ipa63client1 ~]# ipa-client-install with --no-sssd option and nss_ldap or nss-pam-ldapd not installed: ========================================================================= [root@ipa63client1 ~]# rpm -q nss-pam-ldapd nss_ldap package nss-pam-ldapd is not installed package nss_ldap is not installed [root@ipa63client1 ~]# [root@ipa63client1 ~]# ipa-client-install -p admin -w ******* -U --no-sssd One of these packages must be installed: nss_ldap or nss-pam-ldapd Installation failed. Rolling back changes. IPA client is not configured on this system. [root@ipa63client1 ~]#
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. http://rhn.redhat.com/errata/RHBA-2012-0819.html