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