Machine not deleted after deleting associated image

[marc-cabocel]

=== Version ===

• v2.1.1

=== Steps to reproduce ===

• Configure Nanocloud 2.1.1
• Set a Pool to 1
• Go to desktop, save an image and name it "Image 1"
• Once the image is saved, go to Machines and check that the VM being used is now based on the new image "Image 1"
• In Applications, delete the newly created image "Image 1"
• Go to Machines and check if the VM has been deleted

=== Expected Result ===

• The VM based on "Image 1" has been deleted

=== Actual Result ===

• The VM is NOT deleted

=== Analysis ===

• It is not possible to access this VM anymore as there is no more image related to it

[corentindrouet]

If a user is using this vm, in the same time an admin delete the image associated to this vm, the user will see that he can't access it again only after delogging. When the user delog from his machine, he will not have access again to it, and the machine will be deleted after the session duration. This is not a bug, it's for didn't close sessions of users, who are using their vms in the same time where the image is deleted.

Others machines assigned to this image, and without users assigned, are correctly deleted.

[marc-cabocel]

Thanks for the explanation. I understand it from a regular user point of view but as an administrator, it might be useful to at least give him the possibility to delete the VM (with a button for instance)

[corentindrouet]

It's the same for admins. Imagine this situation: An admin go to a vdi, and create an image. An other admin connect, and saw a new image, and doesn't agree with it, so he delete it. But when checking to machines, he see one who has not been deleted (because assigned to the other admin), so he delete it manually. But the other admin is on his vm, so he is brutally disconnected. Why is it usefull to let an admins delete vms manually?

[marc-cabocel]

Ok let's keep it that way and see whether it matters to the customer or not.