apache / apache/cloudstack

Failed to Move VM to Another Account

Open
#13,406 9 comments 0 reactions 0 assignees Claimed by @DaanHoogland View on GitHub
status:needs-functional-definition
Dominant language
Java
Stars
3.1k
Forks
1.4k
Avg merge
6d 19h
Merged PRs (30d)
32

Description

### problem

Up on stopping an Instance and trying to move it to another account...

Image

...it does not make clear what caused the failure.

Image

Even as a Root Admin, there is no explanation of what prevented the move from happening.

By looking at the logs, the message is clear but it is followed by an unhandled exception.

Sanitized fragments of the logs:

Image

```
2026-06-11 20:07:53,953 ERROR [o.a.c.a.c.a.v.AssignVMCmd] (qtp1404565079-58786:[ctx-e08ee8a2, ctx-7b35ebda]) (logid:46523a5c) Failed to move VM [4944]. com.cloud.exception.InvalidParameterValueException: Snapshots exist for volume [ROOT-4944]. Detach volume or remove snapshots for the volume before assigning VM to another user.
at com.cloud.vm.UserVmManagerImpl.validateIfVolumesHaveNoSnapshots(UserVmManagerImpl.java:7961)
at com.cloud.vm.UserVmManagerImpl.moveVmToUser(UserVmManagerImpl.java:7871)
```

Image

```
2026-06-11 19:58:58,841 ERROR [o.a.c.a.c.a.v.AssignVMCmd] (qtp1404565079-58786:[ctx-b7b9a764, ctx-86b9f79a]) (logid:1096b7f6) Failed to move VM [4944]. com.cloud.exception.InvalidParameterValueException: Remove any Port Forwarding rules for VM [VM instance {"id":4944,"instanceName":"i-73-4944-VM","state":"Stopped","type":"User","uuid":"*"}] before assigning it to another user.
at com.cloud.vm.UserVmManagerImpl.validateIfVmHasNoRules(UserVmManagerImpl.java:7934)
at com.cloud.vm.UserVmManagerImpl.moveVmToUser(UserVmManagerImpl.java:7868)
```

### versions

ACS 4.22.0.1

### The steps to reproduce the bug

1.
2.
3.
...

### What to do about it?

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with AssignVMCmd and UserVmManagerImpl, especially validateIfVolumesHaveNoSnapshots, validateIfVmHasNoRules, and moveVmToUser; then review linked pull request #13675. Done should include a clear user-facing explanation for move failures instead of an unhandled exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.