<edit> Sorry I thought this was a new post.  @guido please do not respond to old posts with new solutions.   Ambari 2.6.0 Bug is not applicable here.     @apappu The version on the end of the package is how they handled having multiple versions available in the repos as well as facilitating the upgrade process from one version to another.   Using the variable scope in the python allowed ambari code to be dynamic across all the different versions, environments, etc.   If your repos are setup right, this should not be an issue.  I have seen some failure in the public repos lately, slow to respond, or blocked by certain cloud providers causing the "no package found" errors.     If you are running your own private repos and have an issue like this, you can just create the packages you need in the version you want using the rpmrebuild command on an existing rpm.  ... View more