Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 433DC18012 for ; Mon, 28 Dec 2015 20:50:50 +0000 (UTC) Received: (qmail 51050 invoked by uid 500); 28 Dec 2015 20:50:50 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 51004 invoked by uid 500); 28 Dec 2015 20:50:49 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 50983 invoked by uid 99); 28 Dec 2015 20:50:49 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Dec 2015 20:50:49 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 9DF8A2C1F54 for ; Mon, 28 Dec 2015 20:50:49 +0000 (UTC) Date: Mon, 28 Dec 2015 20:50:49 +0000 (UTC) From: "Jayush Luniya (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMBARI-14452) It should be possible to delete service components if all related host components are stopped MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-14452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-14452. ------------------------------------ Resolution: Fixed > It should be possible to delete service components if all related host components are stopped > --------------------------------------------------------------------------------------------- > > Key: AMBARI-14452 > URL: https://issues.apache.org/jira/browse/AMBARI-14452 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.2.0 > Reporter: Ajit Kumar > Assignee: Ajit Kumar > Fix For: 2.4.0 > > Attachments: AMBARI-14452.patch > > > It should be possible to delete a Service Component regardless of its state when all member host components are in DELETE friendly state (non-started). > This is what happens today with > - HDFS Secondary namenode deployed on c6402.ambari.apache.org > - Host component SECONDARY_NAMENODE in INSTALLED state > {code} > curl -u admin:admin -H "X-Requested-By: ambari" -X DELETE http://c6401.ambari.apache.org:8080/api/v1/clusters/test/services/HDFS/components/SECONDARY_NAMENODE { "status" : 500, "message" : "org.apache.ambari.server.controller.spi.SystemException: An internal system exception occurred: Could not delete service component from cluster. To remove service component, it must be in DISABLED/INIT/INSTALLED/INSTALL_FAILED/UNKNOWN/UNINSTALLED/INSTALLING state., clusterName=test, serviceName=HDFS, componentName=SECONDARY_NAMENODE, current state=STARTED." > {code} > Direct delete of the host component succeeds. > {code} > curl -u admin:admin -H "X-Requested-By: ambari" -X DELETE delete http://c6401.ambari.apache.org:8080/api/v1/clusters/test/hosts/c6402.ambari.apache.org/host_components/SECONDARY_NAMENODE > {code} > Even then the delete of the service component still fails. Ideally very first call to delete service component should have succeeded. -- This message was sent by Atlassian JIRA (v6.3.4#6332)