> 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/pcd/storage/vm-cloning-fails-for-self-service-users.md).

# VM Cloning Fails For Self-Service Users

### Problem

* VM clone operation gets stuck at the `VM snapshot initiated` phase and never progresses to subsequent phases.
* The instance eventually goes into ERROR with scheduler retries exceeded.\
  Relevant error line seen in logs:

```
ERROR nova.scheduler.utils ... Exceeded max scheduling attempts 3 ... Failed to call glance method data
```

### Environment

* Private Cloud Director Virtualization - v2025.10 **till v2026.1-260**
* Self-Hosted Private Cloud Director Virtualization - v2025.10 **till v2026.1-260**
* Component: Compute Service
* Self-Service Users

### Cause

* The cloning attempts are carried out by a **self-service user**, which is where the cloning workflow encounters issues. Sometimes, volume cloning deletes the snapshot before the virtual machine finishes downloading the image.
*  Based on the behaviour, the self-service user does not appear to have the required privileges to complete the full snapshot/image lifecycle used in the cloning flow (snapshot creation + image access during boot + snapshot cleanup).

### Resolution

* Bug **PCD-5572** has been reported, and the fix is available from **v2026.1-309**.

#### Workaround

1. Assign admin-level privileges for cloning. To use the cloning feature reliably, the **self-service user** will need **admin-level privileges.**
2. If admin privileges cannot be provided to the self-service user, a workable alternative is:
   1. Take a **volume snapshot** of the source VM’s boot volume
   2. Create a new VM from that **volume snapshot**


---

# 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/pcd/storage/vm-cloning-fails-for-self-service-users.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.