# Removing failed ECE deployments in Cloud UI **URL:** \ **Category:** Elastic Cloud Enterprise (ECE)\ **Created:** [July 30, 2019, 3:09pm UTC](https://discuss.elastic.co/t/removing-failed-ece-deployments-in-cloud-ui/192931 "2019-07-30T15:09:30Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Ryan\_Downey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryan_downey/32/35987_2.png) [@Ryan\_Downey](https://discuss.elastic.co/u/Ryan_Downey)\ **Post date:** [July 30, 2019, 3:09pm UTC](https://discuss.elastic.co/t/removing-failed-ece-deployments-in-cloud-ui/192931/1 "2019-07-30T15:09:30Z")
ECE 2.2 Issue: I have two deployments showing in the Cloud UI that are stuck in the "Deployment Not Found" stage and I'm trying to clarify how to clear them out correctly. From what I understand of the post linked below I should log in to one of my Coordinator nodes and run two commands since I dont have access to the API console. ```auto 1 `curl -XPOST -u 'admin:PASS' 'localhost:12400/api/v1/clusters/elasticsearch/ID/_shutdown?skip_snapshot=true'` 2 `curl -XDELETE -u 'admin:PASS' 'localhost:12400/api/v1/clusters/elasticsearch/ID` ``` The API reference table has some minor syntax changes but this seems like the general route that I need to take to remove them from the Cloud UI. > [@Failed attempts to create a deployment](https://discuss.elastic.co/t/failed-attempts-to-create-a-deployment/155039): > > ECE 2.0.0 Failed attempts to create a deployment result in a failed cluster showing in the list of deployments that cannot be removed. The deployment shows the following status: Deployment health issues: Some instances in the deployment are unhealthy The latest attempt to change the configuration failed When looking at the ECE Cloud UI, the node appears under the allocator with a Red X and the version is showing 'v'. However, when logging into the OS on the allocator the node is not showi… ---
**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\ **Post date:** [July 30, 2019, 3:22pm UTC](https://discuss.elastic.co/t/removing-failed-ece-deployments-in-cloud-ui/192931/2 "2019-07-30T15:22:21Z")
Yes - that sound right. Sorry about that! Alex ---
**Author:** ![Ryan\_Downey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryan_downey/32/35987_2.png) [@Ryan\_Downey](https://discuss.elastic.co/u/Ryan_Downey)\ **Post date:** [July 30, 2019, 4:01pm UTC](https://discuss.elastic.co/t/removing-failed-ece-deployments-in-cloud-ui/192931/3 "2019-07-30T16:01:13Z")
Alex, appreciate the quick response. With ECE are there any other steps that you need to take in order for these commands to work with a TLS enabled environment. Generally in our environment if I add -k or --insecure to the end of a command it goes through. As of right now I'm not getting that to work. ```auto sudo curl -XPOST -u admin: "https://xx.xxx.xx.xxx:12443/api/v1/clusters/elasticsearch//_shutdown?skip_snapshot=true" -k { "errors": [{ "code": "root.unauthorized.rbac", "message": "The supplied authentication is not authorized to access this resource. Reason: [Not Found]." }] ``` ---
**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\ **Post date:** [July 30, 2019, 4:21pm UTC](https://discuss.elastic.co/t/removing-failed-ece-deployments-in-cloud-ui/192931/4 "2019-07-30T16:21:47Z")
`Reason: [Not Found]` implies the cluster id is wrong If you curl `api/v1/clusters/elasticsearch` does the cluster id you have been using get returned? If not, same question for `api/v1/clusters/elasticsearch/_search?q=*` If it appears in the `_search` but not the `GET` then that is a known sync bug with an easy workaround (`DELETE v1-elasticsearch-clusters-ece-region/elasticsearch-cluster/:id` from the Adminconsole cluster, eg using that cluster's API console) ---
**Author:** ![Ryan\_Downey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryan_downey/32/35987_2.png) [@Ryan\_Downey](https://discuss.elastic.co/u/Ryan_Downey)\ **Post date:** [July 30, 2019, 6:27pm UTC](https://discuss.elastic.co/t/removing-failed-ece-deployments-in-cloud-ui/192931/5 "2019-07-30T18:27:36Z")
Ok so I was able to get this all worked out which is appreciated! My Linux skills aren't very good so theres probably an easier way to do this but I got info with ```auto curl -X POST -u admin: "https://xx.xxx.xx.xx:12443/api/v1/clusters/elasticseach/_search?q=*" -k ``` Updated that with -o to send it to a file since I couldn't read all of the output ```auto curl -X POST -u admin: "https://xx.xxx.xx.xx:12443/api/v1/clusters/elasticseach/_search?q=*" -k -o cluster_post.txt ``` Ran the same thing with the GET ```auto curl -X GET -u admin: "https://xx.xx.xx.xx.xx:12443/api/v1/clusters/elasticsearh" -k -o cluster_get.txt ``` Checked the files, as you mentioned the cluster\_id's appeared in the search but not the GET output ```auto grep cluster_post.txt grep cluster_get.txt ``` Cloud UI --\> admin-console-elasticsearch --\> Elasticsearch -\> API Console --\> DELETE v1-elasticsearch-clusters-ece-region/elasticsearch-cluster/\ Worked perfectly. Thanks again for the quick help @Alex_Piggott!!! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 13, 2019, 6:37pm UTC](https://discuss.elastic.co/t/removing-failed-ece-deployments-in-cloud-ui/192931/6 "2019-08-13T18:37:51Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.