# Cinder Volume Operations Failing With Vmstore “NotFound” Error on Tintri Backend

## Problem

Volume operations in PCD Storage Service fail when using the Tintri (vmstore) backend.

Users may observe:

* Volume stuck in **`creating`** state and eventually failing.
* Failures during operations such as:
  * Volume create
  * Volume clone
  * Other CRUD operations
* PCD UI throws error like:

  ```
  Could not find any available weighted backend
  ```
* On the persistent storage host, `cindervolume-base` logs reports:

  ```
  VmstoreException: Volume driver reported an error: No details 
  (typeId: VmstoreError, code: NotFound)
  ```

## Environment

* Private Cloud Director Virtualization 
* Self-Hosted Private Cloud Director Virtualization
* Component - Storage Service, Tintri 
* Tintri - v3.0.5 and below

## Resolution

* The Tintri Driver needs to be upgraded to the version `3.0.6` and above, followed by a rollout restart of the `cinder-scheduler` workload for the respective PCD region.
  * Customers need to apply the Tintri driver upgrade patch to the Persistent Storage Nodes. Reach out to the Tintri Support Team to implement this patch.
  * Once the Tintri driver is upgraded, reach out to the Platform9 Team about a rollout restart of `cinder-scheduler` workload in the affected region.

{% hint style="info" %}
**Only Self-hosted PCD customers can run the command to restart the cinder-scheduler:**

`$ kubectl rollout restart deployment/cinder-scheduler -n $REGION_NAMESPACE`
{% endhint %}

## Additional Information

* Post PCD upgrade, customers need to upgrade the Tintri driver to 3.0.6 or above versions. 


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://platform9.com/kb/pcd/storage/cinder-volume-operations-failing-with-vmstore-notfound-error-on-tintri-backend.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.