@Ekantheshwara Basappa Ranger admin in HDP 2.5 has a new property for a truststore. So if using ldaps, you need to import the ldapserver cert to the ranger admin truststore , property name ranger.truststore.file. Although no log is being showed for failed connection to ldapserver, setting ranger debug will show that ranger admin is not able to establish ssl connection to ldap server and there by not able to validate the user login. For ranger usersync has similar property ranger.usersync.truststore.file which must already have ldap server cert in it as you have mentioned usersync is working fine. Use the same truststore file for ranger.truststore.file and see if it works. Make sure that you set the UserSerachFilter as sAMAccountName={0} if using AD for ldap accounts. ... View more

@François Vienneau Binette It looks the problem is with hdp-select versions command. hdp-select command will review the directories under /usr/hdp on each host prior to installing the pkgs. /usr/hdp should not contain any directories other than hdp version and current/share directory as below. [root@hdp1 hdp]# pwd /usr/hdp [root@hdp1 hdp]# ls 2.5.0.0-1245 current There can be multiple version directories in case of cluster upgrade under this location. If you have any other directories other than these then please move those directories to other location and make sure "hdp-select versions" command doesnt return any error prior to starting the installation. ... View more