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

Hadoop QA commented on AMBARI-15519:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12800028/AMBARI-15519.amend.v0.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6594//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6594//console

This message is automatically generated.

> 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)

Reply via email to