You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/06/26 03:48:05 UTC

[jira] [Commented] (AMBARI-12151) RU: uses display name instead of actual hdp stack version

    [ https://issues.apache.org/jira/browse/AMBARI-12151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602254#comment-14602254 ] 

Hudson commented on AMBARI-12151:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.1 #118 (See [https://builds.apache.org/job/Ambari-branch-2.1/118/])
AMBARI-12151. RU: uses display name instead of actual hdp stack version (smohanty) (smohanty: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2544de83d8e06ebc1f4a0b6aaf31c4b7434b7700)
* ambari-server/src/main/resources/custom_actions/scripts/install_packages.py


> RU: uses display name instead of actual hdp stack version
> ---------------------------------------------------------
>
>                 Key: AMBARI-12151
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12151
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-12151.patch, Screen Shot 2015-06-25 at 4.29.23 PM.png
>
>
> When registering a stack and choosing (HDP-2.3).0.0-4, based off of the Base URL, Rolling upgrade fails as it tries to hdp-select to that display name version, instead of the actual RPM version: 
> {noformat}
> hdp-select versions
> 2.2.4.2-2
> 2.3.0.0-2231
> {noformat}
> {noformat}
> ambari=> select stack_id, version, display_name from repo_version;
>  stack_id |  version  | display_name  
> ----------+-----------+---------------
>         5 | 2.2.4.2-2 | HDP-2.2.4.2-2
>         3 | 2.3.0.0-4 | HDP-2.3.0.0-4
> (2 rows)
> {noformat}
> This is confusing as there is no good way to guess the build number from the repository base url. Ambari should handle this automatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)