> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/how-to/deleting-a-cinder-service-from-host.md).

# Deleting Cinder Service From Host

## Problem

How to delete the stale *cinder-volume* service if the host no longer exist?

## Environment

* Platform9 Managed OpenStack - All Versions
* Cinder

## Procedure

{% hint style="warning" %}
**Warning**

Before performing following steps, ensure that volumes are not hosted on the cinder-volume services to be decommissioned.
{% endhint %}

1. Identify the host on which the Cinder service has to be removed. Use the below command to list the cinder-volume services:

{% tabs %}
{% tab title="Bash" %}

```bash
openstack volume service list --service cinder-volume
```

{% endtab %}
{% endtabs %}

{% tabs %}
{% tab title="Example" %}

```bash
# openstack volume service list --service cinder-volume
+---------------+------------------------+------+----------+-------+----------------------------+
| Binary        | Host                   | Zone | Status   | State | Updated At                 |
+---------------+------------------------+------+----------+-------+----------------------------+
| cinder-volume | <UUID>@netapp_std1     | nova | enabled  | down  | <TimeStamp>                |
[...]
| cinder-volume | <UUID>@netapp_std2     | nova | enabled  | up    | <TimeStamp>                |
+---------------+------------------------+------+----------+-------+----------------------------+
```

{% endtab %}
{% endtabs %}

2. Ensure the selected host is in **disabled** status. If it's not, disable it with the below command:

{% tabs %}
{% tab title="Bash" %}

```bash
openstack volume service set --disable <HostUUID> <service>
```

{% endtab %}
{% endtabs %}

{% tabs %}
{% tab title="Example" %}

```bash
# openstack volume service set --disable <UUID>@netapp_std1 cinder-volume
# openstack volume service list --service cinder-volume
+---------------+------------------------+------+----------+-------+----------------------------+
| Binary        | Host                   | Zone | Status   | State | Updated At                 |
+---------------+------------------------+------+----------+-------+----------------------------+
| cinder-volume | <UUID>@netapp_std1     | nova | disabled | down  | <TimeStamp>                |
[...]
| cinder-volume | <UUID>@netapp_std2     | nova | enabled  | up    | <TimeStamp>                |
+---------------+------------------------+------+----------+-------+----------------------------+
```

{% endtab %}
{% endtabs %}

3. Now to remove the cinder-volume service from a host:

{% tabs %}
{% tab title="Bash" %}

```bash
cinder-manage service remove <service> <host>
```

{% endtab %}
{% endtabs %}

{% tabs %}
{% tab title="Example" %}

```bash
# cinder-manage service remove cinder-volume <UUID>@netapp_std1
Service cinder-volume on host <UUID>@netapp_std1 removed.
```

{% endtab %}
{% endtabs %}

4. To confirm if the cinder-volume service is removed, use the same command as mentioned in step #1:

{% tabs %}
{% tab title="Example" %}

```bash
# openstack volume service list --service cinder-volume
+---------------+------------------------+------+----------+-------+----------------------------+
| Binary        | Host                   | Zone | Status   | State | Updated At                 |
+---------------+------------------------+------+----------+-------+----------------------------+
| cinder-volume | <UUID>@netapp_std2     | nova | enabled  | up    | <TimeStamp>                |
[...]
+---------------+------------------------+------+----------+-------+----------------------------+
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmo/how-to/deleting-a-cinder-service-from-host.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.