Red Hat Bugzilla – Bug 881024
PRD32 - [RFE] Adding the ability to remove a VM without removing its disks
Last modified: 2016-02-10 15:27:22 EST
Description of problem: There is no easy way to remove a VM from engine without removing it's disks Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. In the VM tab in webadmin select a VM in down status and click on remove 2. Confirm the removal 3. Actual results: VM is removed along with it's disks Expected results: A checkbox should appear in the VM removal confirmation dialog which gives the option to remove the VM yet not remove the disks (Leaving them in engine as floating disks) Additional info:
actually, this should also be at config level, then no need to ask for these disks. for example, say a user launches a VM (instance) from a template (image). expectation is on deletion of the instance, the disks which came from the image will be deleted, but not other disks ("volumes") associated to the instance.
(In reply to comment #1) > actually, this should also be at config level, then no need to ask for these > disks. > for example, say a user launches a VM (instance) from a template (image). > expectation is on deletion of the instance, the disks which came from the > image will be deleted, but not other disks ("volumes") associated to the > instance. Let me see if I follow - you're saying that if we instantiate a template and afterwards add additional disks to the instance then the images derived from the template should be automatically deleted but the added disks should not? if so, why? how would you explain this behaviour to the user?
(In reply to comment #2) > (In reply to comment #1) > > actually, this should also be at config level, then no need to ask for these > > disks. > > for example, say a user launches a VM (instance) from a template (image). > > expectation is on deletion of the instance, the disks which came from the > > image will be deleted, but not other disks ("volumes") associated to the > > instance. > > Let me see if I follow - you're saying that if we instantiate a template and > afterwards add additional disks to the instance then the images derived from > the template should be automatically deleted but the added disks should not? > if so, why? how would you explain this behaviour to the user? afaiu, that's exactly EC2 behavior. an instance is derived from an image, and volumes can be attached to the instance. deleting the instance delete the image disks (which i'm guessing are COW), but not the volumes.
http://gerrit.ovirt.org/10376
REST API: http://gerrit.ovirt.org/#/c/10682/
*** Bug 885002 has been marked as a duplicate of this bug. ***
sf6. sanity was done on.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0888.html