[
https://issues.apache.org/jira/browse/AMBARI-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255042#comment-15255042
]
Hudson commented on AMBARI-15519:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4719 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4719/])
AMBARI-15519 Add Service Wizard with nodes in the maintenance mode. (zhewang:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9906c393aaa2be37c2ef815d90ed7eaccac59b45])
* ambari-web/app/controllers/wizard.js
* ambari-web/app/mixins/wizard/assign_master_components.js
> Add Service Wizard with nodes in the maintenance mode
> -----------------------------------------------------
>
> Key: AMBARI-15519
> URL: https://issues.apache.org/jira/browse/AMBARI-15519
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Zhe (Joe) Wang
> Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15519.amend.v0.patch, AMBARI-15519.v0.patch
>
>
> On the cluster where some nodes are in the maintenance mode Add Service
> Wizard doesn't track this.
> So, user may select host in the maintenance mode to install some master
> component. And this component won't be installed (only record in the DB will
> be created for it).
> Another situation:
> there is some cluster where all nodes are in the maintenance mode. In this
> case ASW is almost useless. Because all new components won't be installed
> while it works.
> Maybe ASW should track hosts in the maintenance mode and warn user about
> adding components on them (Steps "Assign Masters", "Assign Slaves and
> Clients")? Or just don't allow to do this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
