Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 22 Mar 2016 20:09:25 +0000 (UTC)
From: "Zhe (Joe) Wang (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12952570.1458677339000.21826.1458677365664@Atlassian.JIRA>
In-Reply-To: <JIRA.12952570.1458677339000@Atlassian.JIRA>
References: <JIRA.12952570.1458677339000@Atlassian.JIRA>
 <JIRA.12952570.1458677339300@arcas>
Subject: [jira] [Created] (AMBARI-15519) Add Service Wizard with nodes in
 the maintenance mode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Zhe (Joe) Wang created AMBARI-15519:
---------------------------------------

             Summary: 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: Bug
          Components: ambari-web
    Affects Versions: 2.4.0
            Reporter: Zhe (Joe) Wang
            Assignee: Zhe (Joe) Wang
             Fix For: 2.4.0


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)