@Keshav Piplani Latest version of HDP is 2.6.4 which is compatible with Ambari 2.6 (Ambari 2.6.1.3 is the latest version) https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.4/bk_support-matrices/content/ch_matrices-ambari.html#ambari_stack . Some Known Issues of HDP 2.6.4 are listed here: https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.4/bk_release-notes/content/known_issues.html For Ambari HOTFIX/BUG issues which are fixed in Ambari 2.6.1.3 are listed here: https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.1.3/bk_ambari-release-notes/content/ambari_relnotes-2.6.1.3-fixed-issues.html . ... View more

@Michael Bronson What is the ambari server version? # ambari-server --version . Also can you please try using "Incognito Mode" of your browser so that we can isolate the possibility of Browser cachine? Also please let us know if you have recently upgraded ambari ? (What is your current ambari version and what was the old version). . ... View more

@Michael Bronson When we try to register a new version from ambari UI then on the mentioned page ambari makes the following API call to determine which one is the latest minor release of the selected stack: # curl -i -u admin:admin -H "X-Requested-By: ambari" -X GET http://amb25101.example.com:8080/api/v1/stacks/HDP/versions/2.6/operating_systems/redhat7/repositories/HDP-2.6 That way ambari knows which is the "latest_base_url" for the selected stack: { "href" : "http://amb25101.example.com:8080/api/v1/stacks/HDP/versions/2.6/operating_systems/redhat7/repositories/HDP-2.6", "Repositories" : { "base_url" : "http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.6.3.0", "default_base_url" : "http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.6.0.3", "latest_base_url" : "http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.6.4.0", "mirrors_list" : null, "os_type" : "redhat7", "repo_id" : "HDP-2.6", "repo_name" : "HDP", "stack_name" : "HDP", "stack_version" : "2.6", "unique" : false } } Like in this case it knows: http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.6.4.0 So if you do not see this info because you do not have the Internet access. So you will need to configure a local HDP repo and make it available in ambari. You will than need to provide the HDP and HDP-UTILS local repo location in the below text boxes. . ... View more

@Sagar Shimpi Not sure if i understood the query correctly... But i tried this 1. Get the "ranger-ugsync-site" config as following using "action=get" # /var/lib/ambari-server/resources/scripts/configs.py --user=admin --password=admin --port=8080 --action=get --host=localhost --cluster=plain_ambari --config-type=ranger-ugsync-site --file=/tmp/ranger-ugsync-site_payload.json 2. Edited the file "/tmp/ranger-ugsync-site_payload.json" and changed the value of property "ranger.usersync.ldap.ldapbindpassword" in clear text like "ABCD..blah..blah" 3. set this file back using the following command. (action=set) # /var/lib/ambari-server/resources/scripts/configs.py --user=admin --password=admin --port=8080 --action=set --host=localhost --cluster=plain_ambari --config-type=ranger-ugsync-site --file=/tmp/ranger-ugsync-site_payload.json . Done. In order to verify the password was set correctly or not i then tried to get the value again: # /var/lib/ambari-server/resources/scripts/configs.py --user=admin --password=admin --port=8080 --action=get --host=localhost --cluster=plain_ambari --config-type=ranger-ugsync-site | grep 'ldapbindpassword' "ranger.usersync.ldap.ldapbindpassword": "SECRET:ranger-ugsync-site:3:ranger.usersync.ldap.ldapbindpassword", . ... View more

@Michael Bronson The default timeout value for python based service checks are defined as 300 seconds, so one option will be to try increasing the value to a higher value like 450 or 600 to see if it work: # grep -A3 -B2 'service_check.py' /var/lib/ambari-server/resources/common-services/YARN/2.1.0.2.0/metainfo.xml <commandScript> <script>scripts/service_check.py</script> <scriptType>PYTHON</scriptType> <timeout>300</timeout> </commandScript> . BUT here the problem looks like there may be some issue from Yarn side, Because normally the service check does not take all the 300 seconds time. So it will be better to check the health of HDFS and Yarn by looking at the logs to see if there are any errors reported. . ... View more