[
https://issues.apache.org/jira/browse/AMBARI-14452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073143#comment-15073143
]
Jayush Luniya commented on AMBARI-14452:
----------------------------------------
>From CR:
mvn clean install
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Main ....................................... SUCCESS [3.892s]
[INFO] Apache Ambari Project POM ......................... SUCCESS [0.036s]
[INFO] Ambari Web ........................................ SUCCESS [44.426s]
[INFO] Ambari Views ...................................... SUCCESS [3.558s]
[INFO] Ambari Admin View ................................. SUCCESS [9.482s]
[INFO] ambari-metrics .................................... SUCCESS [0.295s]
[INFO] Ambari Metrics Common ............................. SUCCESS [2.682s]
[INFO] Ambari Metrics Hadoop Sink ........................ SUCCESS [5.443s]
[INFO] Ambari Metrics Flume Sink ......................... SUCCESS [3.240s]
[INFO] Ambari Metrics Kafka Sink ......................... SUCCESS [4.338s]
[INFO] Ambari Metrics Storm Sink ......................... SUCCESS [2.540s]
[INFO] Ambari Metrics Collector .......................... SUCCESS [56.444s]
[INFO] Ambari Metrics Monitor ............................ SUCCESS [3.158s]
[INFO] Ambari Metrics Assembly ........................... SUCCESS [1:03.306s]
[INFO] Ambari Server ..................................... SUCCESS
[1:03:33.917s]
[INFO] Ambari Functional Tests ........................... SUCCESS [1:54.784s]
[INFO] Ambari Agent ...................................... SUCCESS [13.209s]
[INFO] Ambari Client ..................................... SUCCESS [0.045s]
[INFO] Ambari Python Client .............................. SUCCESS [2.091s]
[INFO] Ambari Groovy Client .............................. SUCCESS [11.128s]
[INFO] Ambari Shell ...................................... SUCCESS [0.032s]
[INFO] Ambari Python Shell ............................... SUCCESS [0.657s]
[INFO] Ambari Groovy Shell ............................... SUCCESS [8.906s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:09:28.213s
[INFO] Finished at: Tue Dec 22 14:14:22 PST 2015
[INFO] Final Memory: 217M/1155M
> 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)
