[
https://issues.apache.org/jira/browse/AMBARI-12151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-12151:
-----------------------------------
Attachment: AMBARI-12151.patch
Ran all stack python unit tests and tested the feature manually.
> 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)
