Hi
There are some issues in 3.2 that have been solved through 3.8 and in next
4.0:
1.- We've improved the checks and synchronization of delete operation, so
it will wait for the cancel operations.
2.- Delete is an admin operation you should be using cancel to dispose VMs
(it performs additional
Hi,
during a bulk VM deletion process 3 out of 9 VMs failed to be actually
deleted from the hypervisor host (they're still running). This is
obvious by comparing 'onevm list' with 'virsh list':
-bash-4.1$ onevm list | grep myhost
192 userx oneadmin one-192 runn 5 2G
