problem

When assigning a VM to another account (assignVirtualMachine API), if a network error happens during the process, no rollback is executed; thus, leaving the DB in an inconsistent state.

versions

4.20 (probably older as well)

The steps to reproduce the bug

1. Create a VM in ROOT domain
2. Attempt to assign VM to another account in the same domain or sub-domain
3. If an exception occurs in the network setup stage (or simulate the exception) - the VM moves to the new account

What to do about it?

It would be better if the VM remains in the original state