[
https://issues.apache.org/jira/browse/AMBARI-7356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137106#comment-14137106
]
Hudson commented on AMBARI-7356:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #270 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/270/])
AMBARI-7356.When the user completes Install Wizard, mark
Clusters.provisioning_state as INSTALLED. (akovalenko) (akovalenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f63dd8a6eea79defd93837dbfc3011f42692ae91)
* ambari-web/app/controllers/installer.js
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/app/router.js
* ambari-web/app/routes/installer.js
* ambari-web/app/models/cluster_states.js
> When the user completes Install Wizard, mark Clusters.provisioning_state as
> INSTALLED
> -------------------------------------------------------------------------------------
>
> Key: AMBARI-7356
> URL: https://issues.apache.org/jira/browse/AMBARI-7356
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-7356.patch
>
>
> Make the following call when the user completes the wizard:
> PUT /api/v1/clusters/cluster_name
> data: {"Clusters":{"provisioning_state":"INSTALLED"}}
> Also, change the routing rule so that we use Clusters.provisioning_state,
> rather than /api/v1/persist to decide whether to route the user to Install
> Wizard or Dashboard upon login.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
