If cluster is installed with Ambari 2.5 , Upgrading to Ambari2.6.x cause service re-start ( client) failure and Add service also fails with installation. with above combination, you might be hitting https://issues.apache.org/jira/browse/AMBARI-24629 if you see error like below 2018-09-15 08:37:13,748 - Looking for matching packages in the following repositories: HDP-2.6, HDP-UTILS-1.1.0.21 2018-09-15 08:37:15,841 - No package found for hive_${stack_version}(hive_(\d|_)+$) 2018-09-15 08:37:15,844 - The repository with version 2.6.1.0-129 for this command has been marked as resolved. It will be used to report the version of the component which was installed root cause is already explained in the BUG. How to fix the issue: 1. First find out what is your current version repo version id. in browser go to http://apappu3.hdp.com:8080/api/v1/stacks/HDP/versions/2.6/repository_versions?fields=operating_systems/repositories/Repositories/base_url From the response find out the repository_version_id for the version. 2. Now create /tmp/data.json with below content { "operating_systems" : [ { "OperatingSystems" : { "ambari_managed_repositories": false, "os_type" : "redhat6", "stack_name" : "HDP", "stack_version" : "2.6" }, "repositories" : [ { "Repositories" : { "base_url" : "", "repo_id" : "MY-ID", "repo_name" : "MY_name" } }, { "Repositories" : { "base_url" : "", "repo_id" : "MY-UTILS", "repo_name" : "MY-UTILS_name" } } ] } ] } Note: replace "MY-ID"/"MY-UTILS" with the actual sateliterepotag and os_type as well. 3. now run below curl call to update it. curl -u admin -H "X-Requested-By: ambari" --data @data.json -X PUT /api/v1/stacks/HDP/versions/2.6/repository_versions/ID Now - refresh the UI and see if the updated tags are visible in version definition. Note: Please take Ambari database backup before running the CURL call ... View more

Many times Ambari throws installation errors like "No package found for hive_${stack_version}(hive_(\d|_)+$) ..." There can be many reasons for this failure. The root cause for this issue is, basically Ambari could not be able to determine the installable package. Reason1: Check if the same package is already installed using different repoid/sateliterepotag. that can be check using below command yum list installed | grep packagename Ex: yum list installed | grep hive If it shows the entries then determine if those are installed with different repoid/sateliterepotag. In Ambari task logs you can find what tag/repo Ambari is using to install Now see "yum list installed" has the correct repoId - if it is not matching then manually uninstall that library and let Ambari install it. Reason2: If you are using Satelite repository - Ambari should show the repo tag name at "Applicable repositories: Satelitehdp265.." If it is not showing correctly, that means you repo version definition is incorrect. Make sure sateliterepo tag is defined correctly. Reason3: If you have installed the cluster with Ambari 2.5.x and then upgraded to Ambari2.6.x then you might encounter AMBARI-24629 bug. please follow https://community.hortonworks.com/articles/223111/service-restartadd-fails-after-upgrading-to-ambari.html to fix that issue. ... View more

While Upgrading/Downgrading HDP in Ambari, if you see "Unable to determine the stack and stack version" it is possible the repo version has some inconsistency. Post Ambari2.6.x, should have repo_version table "resolved" column as 1 - If it shows "0" then run below update query. update repo_version set resolved = 1 Re-start Ambari and then attempt the operation again - it should go through. Note: As of now it is not a BUG as we could not able to reproduce the issue. ... View more

Ambari 2.7 provides UI for API to learn and perform many of the operations. You can launch the UI and play - http://AMBARI-UI:8080/api-docs/ For example: You can delete the Host by simply entering the hostname in the UI. 1. Go to http://AMBARI-HOST:8080/api-docs/#!/Hosts/deleteHost 2. Move to "Delete a host" section 3. Enter the "hostname" 4. click on "Try" . Window popup shows the API response with response (errors) message and code like below. Similar many other Services/Groups/users API can be tried in the same page. This feature makes life easies to find and use the APIs. ... View more

Starting from Ambari 2.7 there are 2 new features to track who did what. 1. In operations history - for every operation there is a user name associated. 2. In Prior versions there is no way to find out who launched Install/Add wizards. Starting from 2.7 there is Username name being shows in the UI. These features make Administrators life easier to track who did what. ... View more

With Ambari 2.6.0 or 2.5.x version if you try to use 2.6.3 ( http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.6.4.0/HDP-2.6.4.0-91.xml) or 2.6.4 -) http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.6.3.0/HDP-2.6.3.0-235.xml ) VDF files, it fails to load/parse the files - would see below error in the logs.f "like An internal system exception occurred: Could not load url from http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.6.4.0/HDP-2.6.4.0-91.xml. null" Those VDF files has GPL tag URLs and these ambari versions can't understand it - hence fails with the above error. You can consider Upgrading the Ambari to 2.6.1 or later versions. If you want to continue using 2.6.0 or earloer Ambari versions then you may have to create private repo and download GPL binaries and work without GPL tags in VDF file. you can contact Hortonworks support for any further help. ... View more