Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Fri, 21 Jun 2013 13:47:21 +0000 (UTC)
From: "Tom Beerbower (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12654133.1371817770071.154911.1371822441488@arcas>
In-Reply-To: <JIRA.12654133.1371817770071@arcas>
References: <JIRA.12654133.1371817770071@arcas>
Subject: [jira] [Commented] (AMBARI-2458) Ambari API should be able to
 change component state from UNKNOWN to MAINTENANCE
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tom Beerbower commented on AMBARI-2458:
---------------------------------------

+1 on the patch.
                
> Ambari API should be able to change component state from UNKNOWN to MAINTENANCE
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-2458
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2458
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.2.3
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 1.2.5
>
>         Attachments: AMBARI-2458.patch
>
>
> Use case:  When ambari node renamed, agent is not running on old name and as a result all the components are in UNKNOWN state.
> In order to remove component from the "old" named node, it status needs to be changed to MAINTENANCE, which is not possible in current implementation.  Want to issue following:
> {noformat}
> PUT /api/v1/clusters/c1/hosts/host1/host_components/GANGLIA_MONITOR {"HostRoles": {"state" : "MAINTENANCE"}}
> DELETE /api/v1/clusters/c1/hosts/host1/host_components/GANGLIA_MONITOR 
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira