Created attachment 907689 [details] vdsm+engine logs Description of problem: Force remove storage domain(aka destroy) from a DC with 2 or more storage domain can cause disappearance of the vm from a DC without any pop-up warning or error on logs, or in the case of vm that is in status: "up", it becomes external, all the disks he had becomes floating disks and all attempts to add or attach them back is block by CanDoAction: "Cannot add Virtual Machine Disk. This VM is not managed by the engine" the result is the loss of what can be a vital data since all Virtual Machine Memory is deleted,or cannot be accessed. Version-Release number of selected component (if applicable): av9.5 vdsm-4.14.7-3.el6ev.x86_64 rhevm-3.4.0-0.21.el6ev.noarch How reproducible: 100% Steps to Reproduce: case 1:make vm disappear Setup: one host two domains 1.create vm + 2 disks (one on each domain) 2.make sure the vm is down 3.force remove one domain case 2:make vm an external vm Setup: one host two domains 1.create vm + 2 disks (one on each domain) 2.make sure the vm is up 3.deactivate one disk 4.force remove the domain with the deactivated disk Actual results: all of vm's virtual ram is lost Expected results: a warning window should notify the user in case of deleted/external vm or this operation shouldn't cause any damage to vm (more probably) Additional info: I have attached the logs
verified on oVirt-beta
RHEV-M 3.5.0 has been released, closing this bug.