You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jaimin D Jetly (JIRA)" <ji...@apache.org> on 2016/05/14 02:12:12 UTC
[jira] [Updated] (AMBARI-16674) Cluster deployment fails when using
base stack version
[ https://issues.apache.org/jira/browse/AMBARI-16674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaimin D Jetly updated AMBARI-16674:
------------------------------------
Attachment: AMBARI-16674.patch
Verified that the patch resolves the issue manually on a cluster
Verified that all ambari-web tests passes successfully with the patch:
27802 tests complete (29 seconds)
154 tests pending
> Cluster deployment fails when using base stack version
> ------------------------------------------------------
>
> Key: AMBARI-16674
> URL: https://issues.apache.org/jira/browse/AMBARI-16674
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16674.patch
>
>
> *STR:*
> # During install wizard, choose a base stack version For example: HDP-2.3
> # Proceed with this and on review page, click on deploy button
> This results in an API call failure and cluster deployment does not happen.
> The reason for this issue is that UI instead of using VersionDefinition ID generated by the ambari-server, creates and uses its own ID which is incorrect in case of base stack version
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)